Update README.md

This commit is contained in:
boneyard93501 2021-09-02 14:51:14 -05:00 committed by GitHub
parent a46a88b28e
commit 89e3e83142
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -8,7 +8,7 @@ Fluence provides the infrastructure and tools to enable decentralized compute fo
## The Prizes ## The Prizes
Fluence provides named prizes of $500 each for up to three best and unique submissions for each of the following categories: Fluence provides named prizes of USD 500 each for up to three best and unique submissions for each of the following categories:
* Write a tutorial on a use case of your choosing on how to integrate Fluence and Aqua with one or more of IPFS, Ceramic or Textile. The tutorial should be ready for Medium publication and the associated code should be provided in a Github or Gitlab repo with MIT/Apache 2.0 license. For example, you could use Fluence to create NFTs on one or more protocols and Aqua to compose the workflow over Fluence compute and (mutable) decentrazlied storage. * Write a tutorial on a use case of your choosing on how to integrate Fluence and Aqua with one or more of IPFS, Ceramic or Textile. The tutorial should be ready for Medium publication and the associated code should be provided in a Github or Gitlab repo with MIT/Apache 2.0 license. For example, you could use Fluence to create NFTs on one or more protocols and Aqua to compose the workflow over Fluence compute and (mutable) decentrazlied storage.
@ -16,6 +16,12 @@ Fluence provides named prizes of $500 each for up to three best and unique submi
* Write a tutorial on a use case of your choosing on how to use Decentralized Identities (DID) or Verifiable Credentials (VC)w ith Fluence and Aqua from the issuer, holder and/or verifier perspectives. The tutorial should be ready for Medium publication and the associated code should be provided in a Github or Gitlab repo with MIT/Apache 2.0 license. For example, you could use Fluence to create a distributed and decentralized verifier for Verifiable Credentials. * Write a tutorial on a use case of your choosing on how to use Decentralized Identities (DID) or Verifiable Credentials (VC)w ith Fluence and Aqua from the issuer, holder and/or verifier perspectives. The tutorial should be ready for Medium publication and the associated code should be provided in a Github or Gitlab repo with MIT/Apache 2.0 license. For example, you could use Fluence to create a distributed and decentralized verifier for Verifiable Credentials.
and USD 2,0000 USD for the best use of Fluence compute for your dApp. Examples in this category include
* Use Fluence to power a decentralized NFT creation and storage solution using, for examples, NFT.storage. We are especially excited about using Fluence compute to dynamically update the metadata of mutable NFTs.
* Use Fluence to create a multi source DEX price oracle. We see Fluence compute at the "decenter" of querying and processing of streams to facilitate the optimal computation of buy/sell orders and routing to DExs.
* Use Fluence to capture, process and index events across multiple EVMs, e.g., Ethereum L1 and L2, for a (common) contract and store the results on Ceramic or Textile. Not unlike optimal order processing and routing, we see a need for a decentralized compute solution to make real-time transaction routing decisions for a contract available, or to be made available, across multiple EVM implementations.
## Resources ## Resources
* [Fluence documentation](https://doc.fluence.dev/docs/) * [Fluence documentation](https://doc.fluence.dev/docs/)