fluencelabs/Gitcoin-GR11-Hackathon
1
0
Fork 0
mirror of https://github.com/fluencelabs/Gitcoin-GR11-Hackathon synced 2024-12-04 17:00:18 +00:00
Code Issues Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
boneyard93501 2021-09-09 09:38:34 -05:00 committed by GitHub
parent 593a944497
commit f43c3b64b6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 21 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
README.md
View File

@ -8,21 +8,32 @@ Fluence provides the infrastructure and tools to enable decentralized compute fo
## The Prizes
Fluence provides named prizes of USD 500 each for up to three best and unique submissions for each of the following categories:
### Beginner Bounty -- USD 250 x 10:
Extend the Fluence Quickstart, https://github.com/fluencelabs/examples/tree/main/quickstart/3-browser-to-service, with a distributed character count service deployed to at least one Fluence peer. Display a message's character count at the end of the message, e.g., (char count: 123 chars). Document your solution and submit it via a Github or Gitcoin repo with MIT or Apache 2.0 license.
* 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.
### Intermediate Bounties -- USD 2,500 each:
Build a performant explorer for the Fluence network with Fluence services, Aqua-based composition, IPFS (hot/cache) storage and a Web-framework of your choice. The explorer should allow users to query the network at least by service id and blueprint id by peer. A graphical and even animated representation of the network would definitely score extra points. For info concerning the current explorer see https://github.com/fluencelabs/dashboard. Document your solution and provide a max three (3) minute video presenting and demonstration your solutions and submit via a Github or Gitcoin repo with MIT or Apache 2.0 license.
Port or implement an Ethereum signature signing and verification service as Wasm IT modules and provide Aqua workflows at least for sign and verify functionalities. For inspiration, see for example https://crates.io/crates/ethereum-tx-sign or https://crates.io/crates/ethsign. Document your solution and provide a max three (3) minute video presenting and demonstration your solutions and submit via a Github or Gitcoin repo with MIT or Apache 2.0 license.
Implement and deploy Wasm IT modules to create, manage or verify Decentralized Identity (DID) or Verifiable Credentials (VC) documents and associated linked data. An implementation using BBS+, see https://w3c-ccg.github.io/ldp-bbs2020/, would score a lot of goodwill. Document your solution and provide a max three (3) minute video presenting and demonstration your solutions and submit via a Github or Gitcoin repo with MIT or Apache 2.0 license.
Create a Ceramix, https://ceramic.network/, Wasm IT adapter with Marine that provides bindings for both the complete CLI, https://developers.ceramic.network/build/cli/api/, and HTTP, https://developers.ceramic.network/build/http/api/, APIs. Provide Aqua workflows for at least the 'create', 'update' and 'query` methods. Document your solution and provide a max three (3) minute video presenting and demonstration your solutions and submit via a Github or Gitcoin repo with MIT or Apache 2.0 license.
* Write a tutorial on a use case of your choosing that shows how to use [IPLD](https://ipld.io/) with Fluence and Aqua with one or more of Bitcoin or Ethereum. 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 and Aqua to index and search IPFS hosted blogs and websites.
### Advanced Bounty -- USD 5000:
Implement an Aqua "playground", i.e. a browser-based development and execution environment for Aqua scripts.
The minimum acceptable submission should provide the following features and run on at least one of Firefox or Chrome:
* Syntax highlighting
* All examples listed in Aqua examples (see below) need to run
* Document your solution and provide a max five (5) minute video presenting and demonstration your solutions and submit via a Github or Gitcoin repo with MIT or Apache 2.0 license.
* 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.
Have a look at the following resources:
* Aqua JS compiler: https://github.com/fluencelabs/aqua
* Aqua standard library: https://github.com/fluencelabs/aqua-lib
* JS SDK: https://github.com/fluencelabs/fluence-js
* Aqua examples: https://github.com/fluencelabs/aqua-playground
* Syntax highlighting: https://github.com/fluencelabs/aqua-vscode
* Sandbox PoC: https://codesandbox.io/s/aqua-typescript-nvrd1 or https://github.com/folex/aqua-typescript-codesandbox
and USD 2,000 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
## General Resources
* [Fluence documentation](https://doc.fluence.dev/docs/)
* [Aqua book](https://doc.fluence.dev/aqua-book/)