<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/947044f3-241f-4bce-8f7d-09b6529ef95c/Dataverse_logo.jpeg" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/947044f3-241f-4bce-8f7d-09b6529ef95c/Dataverse_logo.jpeg" width="40px" /> Dataverse $3k
</aside>
Dataverse SDK Tutorial：
Home - DataverseOS Documentation
<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/2f34c60b-0be8-4622-848f-12f0f556e1d0/QoGbRSMz_400x400.jpg" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/2f34c60b-0be8-4622-848f-12f0f556e1d0/QoGbRSMz_400x400.jpg" width="40px" /> Ceramic $2k
</aside>
Giving more power to the users over their data is extremely important and can unlock new and better ways how developers interact with each other and collaborate on projects. DAO space is an extremely interesting area where data sovereignty as well as interoperability are important aspects for this space to grow and evolve. We would like to challenge developers to build tools and applications that would improve the collaboration between DAO contributors - better ways to facilitate discussions, proposal reviews or tools to make it easier to track member contributions and enable DAO members to build their interoperable contribution profiles.
We want you to create a comprehensive technical guide that covers the integration between ComposeDB on Ceramic and Lit protocol. More specifically - we want you create a guide that would explain how developers building their dApps using ComposeDB on Ceramic can encrypt data using Lit.
The guide should be based on an a concrete simple example, include code snippets and detailed explanations for each step.
Useful materials:
<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/67f6eaef-11e3-4a1e-8671-0c3f64bf3145/Group_3.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/67f6eaef-11e3-4a1e-8671-0c3f64bf3145/Group_3.png" width="40px" /> Lit Protocol $2k
</aside>
Top 3 projects using Lit Actions and PKPs - $1700 USDC
Most creative use of Lit Protocol (this one is open to access control) - $300 USDC
Criteria: Bounty requirements: Must utilize Programmable Key Pairs and Lit Actions.
Output expected: dApp
Judging criteria:
Resources:
Overview | Lit Protocol Developer Docs
<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/ba63b29d-a141-4d26-9265-9acd5ca29801/byusM8Mt_400x400.jpg" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/ba63b29d-a141-4d26-9265-9acd5ca29801/byusM8Mt_400x400.jpg" width="40px" /> BlockPI Network $1k
</aside>
Build a product with RPC response cache embedded, providing instant response to users, e.g. eth_chainId, net_version, web3_clientVersion - 1000 USDC for the best 3 projects.
Resources：
<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/dbe33eb8-1d59-46b6-a1fb-a1e3b8617dc1/o2JfMaqi_400x400.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/dbe33eb8-1d59-46b6-a1fb-a1e3b8617dc1/o2JfMaqi_400x400.png" width="40px" /> Particle Network $2K
</aside>
Design and implement a dApp using Particle Network SDKs that provides a seamless and user-friendly experience for both Web3 natives and Web2 newcomers. Your dApp should simplify the onboarding process and create an engaging and intuitive user experience. The goal is to enable a user who is completely new to Web3 to use your dApp with as much ease as any traditional Web2 application. More details
Reward: The rewards will be distributed as follows: 1st Prize: $1,000 2nd Prize: $600 3rd Prize: $400
Resources：
<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/4638bf9c-b543-4e04-b5bb-4cebf6821016/1RnEmeJE_400x400.jpg" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/4638bf9c-b543-4e04-b5bb-4cebf6821016/1RnEmeJE_400x400.jpg" width="40px" /> Polybase $2K
</aside>
Polybase is chain-agnostic and developers can use Polybase as their database layer for dapps built on any chain through an oracle like Chainlink. Ideally, we would expect you to build an integration with Chainlink functions that the Polybase community could leverage for building apps from any chain on Polybase. The project should clearly explain how developers building apps on-chain can leverage Polybase as their database layer.
One of the primary use cases for Polybase is to enable developers to build high-performant low-cost decentralized exchanges. DEXs primarily leverage centralized databases because it's expensive to update each transaction on-chain. Since we store data off-chain and generate zk proofs on-chain you would be able to perform high-frequency trading and ensure transparency on your order books.
With dynamic NFT metadata stored on Polybase, you can build new kinds of utility or gaming NFTs that need faster and cheaper NFT metadata updates. For example, you can build a marketplace for software licenses, a marketplace to purchase token-gated educational courses, or even a marketplace to trade and purchase in-game digital assets that can in turn be used in games that are deployed on the blockchain.
Judging Criteria:
Resources：
