π§πͺ Chronicle @ETHGlobal Brussels
π οΈπ»π οΈ Hello builders and welcome to ETHGlobal Brussels Chronicle bounties page!
This document serves as a guide for integrating Chronicle Oracles into your hackathon projects.
You can only compete for one track. For Tracks 1 (DeFi) and 2 (Innovation), if the judges determine that your project is a better fit for the other track, they will move it automatically. You only need to submit your project once.
π° Bounties: 10Kβ
Track 1: DeFi Track (Integrate Chronicle Oracles into one of the following DeFi applications: Borrowing & Lending dApps, Decentralized Exchanges (DEX), Liquidity Mining, Prediction Markets, or Stablecoins)
Track 1: DeFi Track (Integrate Chronicle Oracles into one of the following DeFi applications: Borrowing & Lending dApps, Decentralized Exchanges (DEX), Liquidity Mining, Prediction Markets, or Stablecoins)β
- π₯ 1st: $2500
- π₯ 2nd: $1500
- π₯ 3rd: $700
π Qualification rules:β
-
Each project must use Chronicle Oracles in some form to make a state change on a blockchain, otherwise it will not be eligible. This means that a front end simply reading from Chronicle Oracles doesn't count.
-
You can deploy your contracts on any of the following chains:
- Ethereum Sepolia
- Arbitrum Sepolia
- Base Sepolia
- Polygon zkEVM Sepolia
- Gnosis Chain Mainnet
- Scroll Sepolia
- zkSync Sepolia
- Optimism Sepolia
- Mantle Sepolia
π― Judging Criteriaβ
- Code quality - well organized and readable code will score higher.
- Documentation - the better the documentation the higher the score.
- Extensibility - how easy can a developer use this to build out their own idea?
- DX - does the project provide a high quality developer experience?
- UI/UX - Projects with an intuitive UI will score higher.
π Assets to submit:β
Make sure to include the following in your project submission:
- A public demo URL to your deployed project that judges can test.
- A short video that demonstrates your submission (approximately 2-3 minutes).
- A public GitHub repository with the code.
- Complete the Builder Feedback Form.
Track 2: Most Innovative Chronicle Oracle Integration
Track 2: Most Innovative Chronicle Oracle Integrationβ
- π₯ 1st: $2500
- π₯ 2nd: $1500
- π₯ 3rd: $700
π Qualification rules:β
-
Each project must use Chronicle Oracles in some form to make a state change on a blockchain, otherwise it will not be eligible. This means that a front end simply reading from Chronicle Oracles doesn't count.
-
The prize will go to the top three teams with the most innovative integration of Scribe, Chronicle's new Schnorr Oracle. You can deploy your contracts on any of the following chains:
- Ethereum Sepolia
- Arbitrum Sepolia
- Base Sepolia
- Polygon zkEVM Sepolia
- Gnosis Chain Mainnet
- Scroll Sepolia
- zkSync Sepolia
- Optimism Sepolia
- Mantle Sepolia
Solutions must integrate the Chronicle Oracle smart contracts. The innovation should stem from the use case of the Oracle, i.e., the idea or utility of the project.
π― Judging Criteriaβ
- Code quality - well organized and readable code will score higher.
- Documentation - the better the documentation the higher the score.
- Extensibility - how easy can a developer use this to build out their own idea?
- DX - does the project provide a high quality developer experience?
- UI/UX - Projects with an intuitive UI will score higher.
π Assets to submit:β
Make sure to include the following in your project submission:
- A public demo URL to your deployed project that judges can test.
- A short video that demonstrates your submission (approximately 2-3 minutes).
- A public GitHub repository with the code.
- Complete the Builder Feedback Form.
Track 3: Best Educational Resource for Builders
Track 3: Best Educational Resource for Buildersβ
Create a tutorial for developers on integrating Chronicle Scribe Oracles.
- π₯ 1st: $350
- π₯ 2nd: $250
π Qualification rules:β
- The submitted material should be your own. Material originating from other sources or generated with AI does not qualify.
π― Judging Criteriaβ
- Accuracy: Information provided should be factually correct and well-researched.
- Clarity: Concepts should be explained clearly and concisely, avoiding unnecessary jargon.
- Extensibility - how easy can a developer use this material to build out their own idea?
- Relevance: The content should be relevant to the target audience and meet their learning needs.
- Practicality: The content should offer practical insights, tips, or steps that the audience can apply.