{"schema":"HACKATHON","d":{"id":437,"tabSet":[{"id":796,"name":"Bounties Details","slug":"bounties-details","description":"# General Pool\nProjects can apply directly to one or multiple bounties, but there will also be a general jury to evaluate all of them.\n\nAmong all eligible projects, whether they apply to a specific bounty or not, the jury will select and reward the top ones. Depending on the quality of the projects, the number of rewarded submissions may vary.\n\n# Aligned\nAligned is a decentralized zero-knowledge (ZK) proof verification and aggregation layer for Ethereum. Aligned accelerates Ethereum’s roadmap by making proof verification faster and more affordable.\n\nOur bounties will be awarded to projects that build innovative technology using Aligned for ZKP verification, or extend the capabilities of Aligned by contributing to our open-source project.\n\nBelow we provide a non-exhaustive list of potential ideas. We invite you to reach out to our team members at Lambda Hackweek to discuss project ideas if you will be using Aligned for your hackathon project!\n\n## Requirements\n- Create a project that demonstrates how Aligned can be used for cheap and fast ZKP verification, thus enabling new types of blockchain infrastructure or consumer dApps (bounties 1 & 2).\n - The project must use Aligned to verify ZK proofs.\n - The project must be deployed on the Ethereum Holesky testnet.\n- Improve the Aligned developer experience (bounty 3).\n- The project must use a clear [Open Source License](https://choosealicense.com/licenses/): MIT, GNU, Unlicensed, or any standard open source license your team wants.\n- The project must include appropriate documentation, including:\n - A README.md that describes the project and rationale, provides backgrounds/biographies of team members, and notes on challenges you faced when building the project.\n - Easy to follow deployment and execution instructions.\n - Documentation that allows for others to reproduce your project.\n \n## Resources\n- https://github.com/yetanotherco/aligned_layer\n- https://docs.alignedlayer.com/\n\n## Bounty 1: Infrastructure using Aligned for verification\n\n*Build infrastructure using Aligned to verify proofs.*\n\n**Prizes:**\n- 1st place: $4000\n- 2nd place: $2500\n- 3rd place: $1000\n\nHere is a list of potential ideas:\n- Fast bridging solutions.\n - Example: Noble has implemented [ICS23](https://github.com/cosmos/ics23) in SP1 for Tendermint light clients; we would love to see a similar implementation which uses Aligned for verification. (See https://github.com/noble-assets/sp1-ics23-example and https://x.com/SuccinctLabs/status/1805341476689527207)\n- ZK Oracles.\n - Implement a basic oracle system on Aligned that queries a price endpoint in rust and generates a proof of this using SP1.\n- ZK Coprocessors.\n - Cross-compile [evm-mlir](https://github.com/lambdaclass/evm_mlir) to RISC-V and verify it using SP1 or RISC Zero. Similar to this: https://dev.to/quartztechnology/rethv-building-reth-for-the-risc-v-platform-5f0m[…]503648ce94ea5067168557f221abdfc2bd245b88a385582ebb911a720aa891da7\n - Compile https://github.com/sigp/lighthouse to RISC-V and verify its execution using SP1 or RISC Zero\n- Verifiable Machine Learning.\n - Perform a comparison of running ezkl proving and verification against:\n - Writing an ML model in https://github.com/huggingface/candle and verifying using SP1 or RISC Zero\n- Verify a verkle proof using Aligned.\n - Example: https://github.com/crate-crypto/rust-verkle with SP1\n- Verify a ssz proof using Aligned.\n - Example: https://github.com/ralexstokes/ssz-rs with SP1\n- Build an application using a multi proof system that leverages Aligned. Use multiple rust provers and/or Gnark to have a more robust application, that needs multiple proving systems to agree before doing an action\n- Build the first ZK rollup on top of Aligned (either create only the smart contracts with a simple State Transition Function)\n- Soft finality solutions for Rollups and Appchains.\n- New settlement layers (use Aligned + EigenDA) for Rollups and Intent based systems.\n- Encrypted mempools using SNARKs to show the correctness of the encryption.\n- Alternative L1 <> Ethereum interoperability solutions.\n- Cheap verification and interoperability for identity protocols.\n- New credential protocols such as zkTLS based systems.\n- P2P protocols based on SNARKs such as payment systems and social networks.\n- Based Rollup infrastructure.\n- ZK-based onchain gaming infrastructure.\n\n## Bounty 2: Consumer dApps using Aligned for verification\n*Build fun games & puzzles using Aligned and unleash your creativity.*\n\n*This bounty will be awarded to projects which use Aligned to build something that can engage consumers and create fun onchain experiences for users. Judging will take into account user experience, virality, and ease of taking live onto mainnet.*\n\n**Prizes:**\n- 1st place: $4000\n- 2nd place: $2500\n- 3rd place: $1000\n\n**Here is a list of potential ideas:**\n- ZK Games in Aligned\n - ZK Wordle and then mint an NFT in Ethereum\n - ZK Sudoku and then mint an NFT in Ethereum\n - ZK Tetris with an onchain leaderboard\n- Run a compiler in SP1 or RISC Zero and post a proof to Aligned.\n- Migrate any Halo2 games and examples to Aligned.\n- Run Doom with RISC Zero/SP1 on Aligned.\n\n## Bounty 3: Build Aligned Tooling\n*Help accelerate Aligned’s roadmap by contributing to our project and extending its capabilities.*\n\n**Prizes:**\n- 1st place: $4000\n- 2nd place: $2500\n- 3rd place: $1000\n\nHere is a list of potential ideas:\n- Build a Go, Python, or Typescript SDK for interacting with Aligned.\n- Tooling to improve the Aligned developer experience.\n\n\n# ZKsync \nzkSync Era is a Layer-2 protocol that scales Ethereum with cutting-edge ZK tech. Our mission is not only to increase Ethereum's throughput merely but to fully preserve its foundational values – freedom, self-sovereignty, decentralization – at scale.\n\n## Bounty 1: Build an application using Native Account Abstraction on ZKsync\n\nNative Account Abstraction on ZKsync Era fundamentally changes how accounts operate by introducing the concept of Smart Accounts and Paymasters. Smart Accounts are fully programmable, allowing for various customizations such as signature schemes, native multi-sig capabilities, spending limits, and application-specific restrictions. Paymasters can sponsor transactions for users, enabling users to pay transaction fees in ERC20 tokens.\n\nThis bounty is for projects that demonstrate innovative uses of native account abstraction. \n\nPrizes:\n- 1st: 4000\n- 2nd: 2500\n- 3rd: 1000\n\n## Bounty 2: Build a ZK app on ZKsync Era\nThis bounty is for projects that demonstrate innovative uses of ZK technology on ZKSync Era. \n\nPrizes:\n- 1st: 4000\n- 2nd: 2500\n- 3rd: 1000\n\n## Requirements for bounty 1 and bounty 2\n- Project must be deployed on zkSync Sepolia Tesnet\n- Documentation should include:\n - a clear README.md with the following:\n - a clear short one-sentence description of your dapp. Aim for something simple like: “Easy social recovery via Telegram” or “Customizable long-term vaults on smart contract accounts to prevent thefts from hacking”.\n - short description of team and backgrounds.\n - a clear installation/execution process that works.\n - A clear Open Source License: MIT, GNU, Unlicensed or any standard open source license your team wants.\n - Have a Project Description section including the problem being solved and any issues you ran into.\n- Bonus: \n - Create a tutorial and document your code projects for others to replicate\n### Resources\n\nQuickstart: https://docs.zksync.io/build/quick-start/hello-world.html\n\nDocumentation: https://docs.zksync.io/build/\n\nDeveloper Tools: https://docs.zksync.io/build/tooling/zksync-cli/getting-started.html\n\nNative Account Abstraction (AA) on zkSync: \nhttps://docs.zksync.io/build/developer-reference/account-abstraction.html.\n \nNative AA vs EIP4337: https://docs.zksync.io/build/developer-reference/differences-with-ethereum.html#native-aa-vs-eip-4337\n\nExamples: daily spend limit smart account: https://docs.zksync.io/build/tutorials/smart-contract-development/account-abstraction/daily-spend-limit.html\n\nExamplel: ERC20 token paymaster: https://docs.zksync.io/build/tutorials/smart-contract-development/paymasters/custom-paymaster-tutorial.html\n\nRepository: paymaster examples: https://github.com/matter-labs/paymaster-examples\n\n# Starknet\n\nBuild any cool stuff using one or multiple elements of the Starknet stack.\n\nFew ideas:\n- Onchain game using Dojo\n- Innovative dApp on Starknet\n- Hack on Stone prover or Stwo prover\n- Contribute to the Bitcoin Circle Stark verifier\n- Performance optimisations on any component of the Starknet stack\n- Build your custom Starknet Appchain using Madara\n\n## Prizes\n- 1st: $4,000\n- 2nd: $2,500\n- 3rd: $1,000\n\n## Resources\n\n- [Cairo Book](https://book.cairo-lang.org/)\n- [Starknet documentation](https://docs.starknet.io/)\n- [Garaga - State-of-the-art Elliptic Curve operations and SNARKS verification for Cairo & Starknet](https://github.com/keep-starknet-strange/garaga)\n- [Bitcoin Circle STARK verifier](https://github.com/Bitcoin-Wildlife-Sanctuary/bitcoin-circle-stark)\n- [STWO - Next Gen Prover](https://github.com/starkware-libs/stwo)\n- [Madara](https://github.com/keep-starknet-strange/madara)\n\n# nil\n=nil; is an Ethereum L2 blockchain leveraging zkSharding to enhance scalability through horizontal scaling, modularity, and verifiable security. Our architecture supports parallel transaction processing across multiple execution shards, each validated by zero-knowledge proofs (ZKPs) and EVM opcode compatibility. Interoperability among these shards is seamlessly maintained through a native cross-shard communication protocol, enabling efficient and secure interactions within the network.\n\nWe are offering bounties for developers who choose to build dApps on top of our cluster. This is your opportunity to be among the first to explore and code on =nil;. We encourage you to start small and expand your efforts as you learn more about our technology. We will do our best to provide support both online and offline to assist you throughout the hackathon.\n\nWe are offering a total bounty of $3,500, distributed as follows:\n- 1st Prize: $1,200\n- 2nd Prize: $1,000\n- 3rd Prize: $800\n\nAddition **$500 Pool** which will be shared among participants who submit any qualifying dApp project beyond the top three prizes\n\n**Additional Resources:**\n- Official =nil; Documentation: https://docs.nil.foundation/nil/intro\n- =nil; Hardhat Example: https://github.com/NilFoundation/nil-hardhat-example\n\n**If you want to join our bounties and build on =nil;, get in touch with our team lead Aleksa Opacic for access to the network and all the details. Find Aleksa on Telegram @aleksaopacic**\n\n## Project Suggestions\n\nWe welcome any dApp as a submission for the hackathon. The only mandatory requirement is that it's deployed on the =nil; cluster and users can interact with it. If you are unsure of what to build, here are a few suggestions that we would be excited to see:\n1. **Custom Wallets:** Understand how wallets work in =nil; and create a novel wallet implementation that could be adopted by various projects within our ecosystem. For example, consider developing vesting wallets that could leave a lasting mark on the =nil; ecosystem.\n2. **Async Messages Coordinator:** Explore how you can coordinate asynchronous messages at the application level to enhance cross-shard communication. This could be a crucial tool for developers looking to optimize interactions across shards.\n3. **NFT Standard Development:** Develop a straightforward NFT standard for =nil;\n4. **Applications Utilizing Cross-Shard Communication:** Asynchronous communication allows us to unlock horizontal scalability. Think of applications that can make use of this additional scale for better and more valuable user experiences.\n\n# Polygon Miden\nPolygon Miden is a zkRollup with client-side proving. Anyone can create zk proofs of their own state changes, and the rollup only verifies. That leads to high throughput and privacy at the same time. \n\nWe are currently on the alpha testnet. The Miden client is available in Rust and WASM for you to build applications. However, smart contract development must be done in Miden Assembly - it’s easier than it sounds.\n\nMore info: https://hackmd.io/@Domi2000/rJZ7Ms6BC\n\n**** **All bounty applications will be open source, with the full source code available on GitHub.**\n\n## Bounty #1 $5000 in MATIC - ECDSA signatures in Miden (secp256k1)\n\nFor any cross-chain application on Miden, we will need to verify signatures. Most signatures in the Ethereum and Bitcoin ecosystem are secp256k1.\n\nCurrently, it is inefficient to use elliptic curve cryptography in the Miden VM and, therefore, in the rollup. However, most cross-chain applications or encryption techniques are based on elliptic curve cryptography, mainly secp256k1. \n\nFind a way to make ECDSA signature verification cheap (<1m cycles) and efficient on Miden - that can be via a [chiplet](https://0xpolygonmiden.github.io/miden-vm/design/chiplets/main.html) (~ Co-Processor) or any other technique. \n\n## Bounty #2 $5000 in MATIC - FRI in a chiplet\n\nOne of the primary goals of the Miden VM is to achieve very efficient recursive STARK proof verification (see Bobbin’s [zkSummit talk](https://www.youtube.com/watch?v=uL2J31dQfLI) for a high-level overview). One of the main components of verifying STARKs is verifying FRI proofs. For example, verifying a FRI proof for a computation that requires 1M cycles in the Miden VM takes up 20K+ cycles (which is roughly ⅓ of the entire STARK proof verification cost).\n\nCurrently, FRI proof verification procedure in Miden VM is written in MASM. One of the main components of this procedure is verifying correctness of a single FRI query (see [here](https://github.com/0xPolygonMiden/miden-vm/blob/next/stdlib/asm/crypto/fri/frie2f4.masm#L179)). This procedure can be sped up dramatically if most (or all) of the logic is offloaded to a dedicated [chiplet](https://0xpolygonmiden.github.io/miden-vm/design/chiplets/main.html).\n\nThe goal of this challenge is to design a Miden VM chiplet to reduce the [verify_query](https://github.com/0xPolygonMiden/miden-vm/blob/next/stdlib/asm/crypto/fri/frie2f4.masm#L179) procedure to as few instructions as possible (ideally, a single new instruction in the VM). This would primarily consist of defining the AIR (intermediate algebraic representation) for the chiplet.\n\nA successful design would use the existing chiplet architecture, though, some modifications of the architecture are possible (e.g., some minor increase in the number of columns is OK). We can also assume that the chiplet can “make calls” to other chiplets for things like hashing, reading/writing memory etc.\n\n## Bounty #3 $4000 in MATIC - Prototype of a novel application on Miden\n\nMiden’s properties allow builders to build applications that are infeasible on EVM-chains. Privacy, native account abstraction, and parallel transaction execution open the design space for novel applications and experiments. \n\nThe applications could be in DeFi, RWAs, or on-chain voting. One example is the [on-chain order book](https://github.com/0xPolygonMiden/examples/discussions/138) on Miden.\n\nThe most useful novel application that works as a Proof of Concept wins this bounty.\n\n## Bounty #4 $4000 in MATIC - Prototype a game on Miden\n\nPrototype a game which is multiplayer(preferred) and involves hiding/revealing information as gameplay mechanism and client side proving as a means to improve the gameplay experience.\n\nExamples: Fog of War and Dark Forest.\n\n## Bounty #5 $3000 in MATIC - Send funds privately from browser to browser\n\nUse the [Miden client npm package](https://www.npmjs.com/package/@demox-labs/miden-sdk?activeTab=readme) to build an in-browser payment application using private notes. Clients could communicate via encrypted emails or WebRTC. However, this should be abstracted away from the user. For this bounty, most technology is already there, and the bounty is about the UX. \n\nThe most private and best-designed application wins this bounty.\n\n# Celestia\nThe first modular blockchain network, Celestia is a modular data availability network that makes it easy for anyone to securely launch their own blockchain. You can build whatever by rapidly launching a blockchain with leading Ethereum rollup frameworks or transform nearly any VM into your own sovereign chain. With Celestia underneath, a customizable blockchain becomes as easy to deploy as a smart contract, while accessing abundant throughput enabled by data availability sampling (DAS), the first architecture that scales while maintaining verifiability for any user.\n\n**Build Whatever Bounty $2000** - Build whatever while still leveraging Celestia DA. The prize goes to the best hack with Celestia DA overall. To qualify, you can build something with a predefined rollup stack like OP Stack, Arbitrum Orbit (can leverage Stylus), Madara, or build something using Rollkit, Sovereign SDK, a game with Katana or something completely new! \n\n\n**Modular Builder Bounty $2000** - Awarded to the best hack that combines Celestia and any other piece of the modular stack, specially from other sponsors (think Celestia DA for Taiko, or combining Aligned layer with Celestia DA, etc)\n\n[https://docs.celestia.org/\n](https://docs.celestia.org/)\n\n[Hack Ideas\n](https://celestiaorg.notion.site/Lambda-Hack-Week-Ideas-Celestia-66d85f8b6a514f44afc95eaae4d6e482)\n\n# node101\n\nnode101 is thrilled to support innovation in the modular ecosystem by offering bounties to developers who bring the modularity of Cosmos and the privacy & scalability of zero knowledge together. For instance, you may develop a Cosmos SDK project with ZK, integrate Cosmos SDK in your hackathon project, integrate IBC technology into your ZK application, or implement some ZK functionality to an existing Cosmos chain. Nevertheless, be bold to explore new ideas and feel free to reach in case you have any questions.\n\n[Cosmos SDK](https://docs.cosmos.network/) is a powerful framework that simplifies the creation of custom blockchains, enabling developers to focus on building applications rather than infrastructure. By leveraging Cosmos SDK, projects can benefit from the robust CometBFT consensus engine, interoperability with other blockchains through IBC (Inter-Blockchain Communication), and a modular architecture that promotes rapid development and scalability. Some of the big projects that are using Cosmos’s technology that you may have heard of are [Cosmos Hub](https://hub.cosmos.network/main), [Celestia](https://celestia.org/), [Osmosis](https://osmosis.zone/), [Agoric](https://agoric.com/), [Akash](https://akash.network/), [Injective](https://injective.com/), [Namada](https://namada.net/), [Penumbra](https://penumbra.zone/), [Fetch.ai](http://Fetch.ai), [dYdX](https://dydx.exchange/), and [Bera Chain](https://www.berachain.com/).\n\nIn this hackathon, we aim for more ZK developers to join the modular ecosystem of Cosmos. We believe in modularity more than anything, and we want more people to be a part of the modular change. Just reach out to our team to explore!\n\nE-Mail: yunus@node101.io or necip@node101.io \n\nTelegram: @ygurlek or @necipsagiro\n\n## Docs and Resources\n\n- Explore all the Cosmos SDK projects: https://cosmos.network/ecosystem/apps/\n- All the developer docs you need: https://docs.cosmos.network/\n- Learn Cosmos with Interchain Foundation’s academy: https://ida.interchain.io/ \n- Cosmos SDK GitHub: https://github.com/cosmos/cosmos-sdk \n\n## Bounty Details\n\nWe are excited to offer a total of $4,000 worth of ATOM tokens for this year’s Lambda Week.\n\n1. 1st Place: $2,000 worth of ATOM\n2. 2nd Place: $1,250 worth of ATOM\n3. 3rd Place: $750 worth of ATOM\n\n## Eligibility Criteria\nTo qualify for the bounty, projects must:\n- Be integrating to an existing Cosmos SDK project or using Cosmos SDK or Cosmos related technology (like IBC),\n- Using ZK for a meaningful functionality inside the project,\n- Make a meaningful contribution to the ecosystem or show inspirational use case,\n- Have a working proof of concept demonstration,\n- Implement modular structure and write clean code,\n- Provide clear documentation and a explanation of the project,\n- Have all the code public in GitHub.\n\nNevertheless, be bold to explore new ideas and propose your own project. Just discuss with our team before!\n\n## Submission Guidelines\n- Submit a link to your project’s public repository (GitHub, GitLab, etc.).\n- Include a detailed README file with the project motivation, an overview of the project, and an explanation of how ZK is integrated to the Cosmos SDK or Cosmos related chain.\n- Also, it is preferable to submit a PR to the Cosmos SDK or related chain if applicable\n\n## Judging Criteria\n\nProjects will be judged based on the following factors:\n- Innovation: How unique and creative is the solution?\n- Technical Implementation: How well is ZK and Cosmos integrated and utilized?\n- Impact: What potential impact could this project have in the real world?\n- Documentation and Presentation: How clear and comprehensive is the documentation and presentation of the project?\n\nWe look forward to seeing the innovative projects you create using Cosmos SDK and wish all participants the best of luck in the hackathon!\n\n# Cartridge\nCartridge leads the development of the Dojo Engine and other tools and infrastructure for building and deploying Fully Onchain Games (FoCG) and Autonomous Worlds (AW).\n\nDojo is an open source framework for building provable Games, Autonomous Worlds and other Applications that are composable, extensible, permissionless and persistent. Dojo is an extension of Cairo, an efficiently provable language, that supports generation of zero-knowledge proofs attesting to a computations validity and enables exponential scaling of onchain computation while maintaining the security properties of Ethereum.\n\nPrizes will be awarded to teams for \n1. Best Dojo Games,\n2. Best Dojo Games Deployed with Slot, \n3. Best Dojo Games Integrated with Controller!\n\n3x $1,000 Prizes for the Best Games Built with [Dojo](https://book.dojoengine.org/)\n\n2x $500 Prizes for Best Games Deployed with [Slot](https://book.dojoengine.org/toolchain/slot)\n\n2x $500 Prizes for Best Games Integrated with [Controller](https://docs.cartridge.gg/controller/getting-started)\n\nJudging is subjective, but it will be based on the criteria listed below:\n1. Novel use of the unique properties of the Dojo Engine\n2. Originality of concept, game mechanics, visual design, etc.\n3. Compelling visual and game design\n4. Level of fun\n\n### Resources\n[Dojo Book\n](https://book.dojoengine.org/)\n\n[Slot Documentation\n](https://book.dojoengine.org/toolchain/slot)\n\n[Controller Documentation\n](https://docs.cartridge.gg/controller/getting-started)\n\n[Dojo Basecamp Workshop\n](https://www.youtube.com/live/BzhN3T5U3PA)\n\n# EigenLayer\n\nEigenLayer enables developers to build arbitrary distributed systems on top of the Ethereum trust network. It extends the security of Ethereum outside the EVM, making it an order of magnitude easier to build decentralized networks.\n\n### Prizes\nBest use of existing EigenLayer AVS - $2,000.00\n\nBest new EigenLayer AVS - $3,000.00\n\n### Resources\nAVS Book: https://eigenlabs.gitbook.io/avs-book\n\nAwesome AVS: https://github.com/Layr-Labs/awesome-avs\n\n# Mina\nMina Protocol is the world’s first zero knowledge proof verification L1 that enables zero knowledge proof based decentralized applications development on top of it. The entire Mina blockchain can be verified as a zero knowledge proof, thus enabling a constant sized block history: the entire Mina state history can be expressed in 22 KBs! o1js is the name of the typescript framework that is used to generate zero knowledge proofs that can be verified both inside and outside the Mina blockchain. o1js proofs are constant both in proof size and verification time. It also enables one of the world’s best performant proof aggregation technologies through proof recursion.\n\nThis year, Mina Protocol will be sponsoring the Lambda Hackathon with a total budget of **15,000 MINA**. You may find more information about the bounty details and the technology below. If you have any questions about the bounties or Mina’s technology in general, please feel free to reach!\n- E-Mail: yunus.gurlek@minaprotocol.com\n- Telegram: @ygurlek\n- Twitter: @yunusguerlek\n### Some Resources \n- [Mina Docs - zkApps](https://docs.minaprotocol.com/zkapps/o1js): Mina Docs include a low of valuable information for you to build amazing zkApps (zero knowledge applications)\n- [Mina Docs - Tutorials](https://docs.minaprotocol.com/zkapps/tutorials): Tutorials are the perfect way to start learning o1js from scratch.\n- [Mina Docs - o1js Reference](https://docs.minaprotocol.com/zkapps/o1js-reference): You may find more information on o1js modules and methods in the official reference.\n- [Minascan](https://minascan.io/directory) and [ZKOK](https://zkok.io/): List of current projects in Mina.\n- [Detailed o1js Article](https://docs.google.com/document/d/1SA3VOi3KVVdl09q4010HgtUzTWWnYTG-95lvtmQlJFI/edit?usp=sharing): This work in progress article may be helpful to understand o1js in more detail.\n- [Hackathon Project Ideas](https://docs.google.com/document/d/1Ufin1p7zgalFcsss5V_DscEGOFIDXRhmiwjhmCER26g/edit?usp=sharing): Finally, you may find some project ideas here to help you start building on Mina.\n\n## General Qualification Requirements\nAll the projects that want to be considered for Mina’s trach must qualify the following criterias:\n- All projects must be using o1js for some zero knowledge proof related functionality (both inside and outside Mina Protocol is accepted).\n- Zero knowledge proofs (ZKPs) must be a valid part of the project and must show some unique functionality that is not possible without ZKPs.\n- All of the code must be written during the hackathon, with the only exception of ZK gaming projects. Please find more information below.\n- All of the code must be in GitHub (or some other Git management tool) and public. Please keep your code public for reference and inspiration to other developers after the hackathon as well.\n- All of the code must be original. You may of course use some other o1js library or project to not reimplement some functionality, but this must be properly documented in your code. Also note that your project will not receive any credits for the libraries you have used without implementing any new functionality.\n\nPlease always communicate with us to make sure your project meets all the requirements. We are 7/24 here to help you.\n\n### Main Prize Pool\nAll projects that qualify for the general qualification requirements will be considered for these prizes. In addition to the MINA award that your project will receive, your project will directly qualify for [Mina’s Navigators Starter Grant](https://minafoundation.notion.site/Mina-Navigators-Season-2-72ccd35e45304bc98dbeec88c1ca2056) (that is equivalent to an additional grant of 5000 MINA).\n\nPlease note that Mina neither requires, nor wants the projects on top of it to be solely using Mina’s technology. Mina is one of the world’s strongest ZKP verification and settlement layers, and it has amazing capabilities, but for some other use cases integrating different technologies may make sense for the project. Thus, please be aware that we support cross chain projects and encourage you to discover new possibilities by including as many technologies as possible in your projects.\n\n- 1st Place: 3500 MINA + Navigators Starter Grant\n- 2nd Place: 2500 MINA + Navigators Starter Grant\n- 3rd Place: 1750 MINA + Navigators Starter Grant\n- 4th Place: 1500 MINA + Navigators Starter Grant\n- 5th Place: 1250 MINA + Navigators Starter Grant\n \n### General Prize Pool\nAll projects that qualify for the general qualification requirements will be awarded from the general prize pool that worths a total of **4500 MINA**. This amount will be split between all qualifying projects equally. So basically, it is impossible to not be awarded if you are able to finish your project using Mina’s technology 🙂\n\nAll projects that qualify for Mina’s bounty will also be considered for a [Navigators Starter Grant](https://minafoundation.notion.site/Mina-Navigators-Season-2-72ccd35e45304bc98dbeec88c1ca2056). Please note that there is no guarantee that you will receive this grant, but there is a really high chance that you will be accepted if you made a meaningful contribution to the Mina ecosystem.\n\nAlso, please note that Mina Foundation is more than open to have additional rewards for the projects that show extraordinary success during the hackathon. So do not limit yourself to this document and be bold to explore as much as you can!\n\n\n# RISC Zero\nIt's now possible to pair a program's output with a self-certifying receipt, allowing a skeptical third party to verify correct execution — and the verifier doesn't need to repeat the original computation or even see the inputs to the program!\n\nRISC Zero empowers everyone to create these Verifiable Programs using Zero Knowledge Proofs (ZKPs). Unlike other ZKP domain specific languages and pure arithmetic circuit constructions, RISC Zero provides a Virtual Machine (zkVM) that proves correct execution of a RISC-V compiled program written in any language* !\n\n*Rust is by far the most supported for now, but examples in python, C/C++, Wasmtime, and more exist!\n\n## 🤩 Best zkVM Application ⸺ $1,500\n*Up to 3 teams will receive $500*\n\nBest RISC Zero zkVM projects - anything that uses our tooling! There are no specific use cases we are looking for, so be as creative as you’d like. ✨\n\nQualifications\n\nOpen-ended prize! The only strict requirement is that your submission uses the RISC Zero zkVM.\n## 🤝 ZK Coprocessor ⸺ $1,000\n*Up to 2 teams will receive $500*\n\nThe [RISC Zero Foundry Template](https://github.com/risc0/risc0-foundry-template) makes it easy to get started with both the on-chain and off-chain parts of a [blockchain coprocessor](https://www.risczero.com/blog/a-guide-to-zk-coprocessors-for-scalability) application. This provides a starting point for building powerful new applications on Ethereum that offload computationally intensive (i.e. gas expensive), or would be difficult or impossible to implement Solidity & the EVM.\n\nQualifications\n\nSubmissions should offload computation from on-chain to off-chain. Special consideration will be given to projects that utilize our [STEEL View Call Proofs Library](https://www.risczero.com/blog/introducing-steel).\n\n## 👪 Integrations Bounty ⸺ $1,000\n\n*Up to 2 teams will receive $500*\n\nThere are so many ways to integrate zk proof systems into various on and off-chain applications to add value and unlock new possibilities - many yet to be discovered! We want to incentivize you to build a novel integration for any other sponsor bounty’s platform.\n\nQualifications\n\nSubmissions must be new or non-trivial improvements or extensions of RISC Zero integrations with another LambdaHackWeek @ Brussels 2024 sponsor’s platform/tooling/app. Bonus points for those applying for their bounties as well! \n\n## 🗃️ Resources\n- [Getting Started - Dev Docs](https://dev.risczero.com/api/getting-started)\n- [Getting Started - Video Tutorials](https://www.youtube.com/playlist?list=PLcPzhUaCxlCj7wKkzekYYq7QDvtGTOPm7)\n- [Awesome RISC Zero\n](https://github.com/inversebrah/awesome-risc0)\n- [Demos and Examples](https://dev.risczero.com/api/zkvm/examples)\n- [STEEL View Call Proof Library](https://github.com/risc0/risc0-ethereum/tree/main/steel)\n\n\n# OnlyDust\n\nOnlyDust is a platform that onboards developers to blockchain ecosystems, through open-source contributions. Contribute to the most exciting projects in the space and get rewarded.\n\n## Bounties\n\nWe will provide $15.000 for eligible contributors that are able to tackle issues for the following repos: \n\n### Stellar (1 Repo)\n\n[Soroban Example DApp](https://github.com/stellar/soroban-example-dapp/issues): How to build a dapp frontend backed by smart contracts on Stellar.\n\n\n### Proof of Passport (1 Repo)\n\n[Proof of passport](https://github.com/zk-passport/proof-of-passport) is developing tools allowing users to generate proofs of humanity, nationality and age using their government-issued passport. We want to make it easy to extract the signed data from passport chips and verify it. It unlocks uses cases in proof of unique identity, sybil resistance and selective disclosure of private data.\n\n\n### Worldcoin (1 Repo)\n\n[Worldcoin scroll bridge:](https://github.com/dragan2234/worldcoin-scroll-bridge) Build bridge integrations with Scroll. The point of the state bridge contracts in world-id-state-bridge is to have two contracts, one deployed on Ethereum mainnet and the other one on a target L2.\n\n\n# Taiko\n\nTaiko is Ethereum’s first Based Layer 2 scaling solution. Based means that Taiko uses (the base layer) Ethereum’s nodes as the sequencers for its blocks. As a result, Taiko inherits all the same economic security guarantees as Ethereum. It also means there is no need for an escape hatch mechanism common with external sequencers. Taiko is also Ethereum equivalent, which means that developers can use all the same tools they’re used to and any contract that runs on Ethereum will also run on Taiko. \n\n## Bounty: Build Discord/Telegram Bots and Minigames Utilizing the Taiko Blockchain\n\n**Description**: We are excited to announce a hackathon bounty for innovative developers to build Discord and Telegram bots or minigames that integrate with the Taiko blockchain. This is a fantastic opportunity to showcase your skills in blockchain development, engage with a vibrant community, and win some prizes!\n\n**Prize Pool**: $1750\n\nThe prize money may be divided between up to 3 top prizes. However, if there is one clear standout winner, they may receive the entire prize pool.\n\n## Judging Criteria:\n- Functionality (30%)\n - How well does the bot or minigame perform its intended functions?\n - Is the integration with the Taiko blockchain seamless and effective?\n- Innovation (25%)\n - How unique and creative is the bot or minigame?\n - Does it introduce new or interesting use cases for the Taiko blockchain?\n- User Experience (20%)\n - Is the bot or minigame easy to use and navigate?\n - Does it provide a smooth and enjoyable user experience?\n- Technical Implementation (15%)\n - Quality of the code and technical implementation.\n - Efficient use of the Taiko blockchain's features.\n- Documentation (10%)\n - Clarity and completeness of the project documentation.\n - Ease of understanding for other developers or users.\n\n## Helpful Resources\n1. Taiko Blockchain Documentation: https://docs.taiko.xyz\n2. Discord.js Documentation: https://discordjs.guide/\n3. Telegraf.js Documentation: https://telegraf.js.org/\n4. Discord Bot Example: https://github.com/discordjs/discord.js\n5. Telegram Bot Example: https://github.com/telegraf/telegraf\n\nGet creative, dive into the world of Taiko blockchain, and build something amazing! Happy hacking!\n\n## Some ideas to get you started:\n### Tipping bot\nA bot that allows users to manage a basic Taiko wallet in Discord/TG. They can check their balances and send tokens to other users based on their username. \n\n### OTC Trading Bot\nA bot that facilitates token swaps between users within Discord/Telegram channels using smart contracts on the Taiko blockchain. Users can initiate and confirm token swaps securely.\n\n### Decentralized Lottery Minigame\nA lottery game where participants buy tickets using Taiko tokens. The smart contract on the Taiko blockchain manages ticket purchases, randomly selects a winner, and distributes the prize automatically.\n\n### Crypto Trading Simulation\nA simulation game that mirrors real-time crypto trading on the Taiko blockchain. Players can buy and sell virtual assets, with transactions recorded on-chain to track profits and losses.\n\n### NFT Marketplace Bot\nA bot that acts as a decentralized NFT marketplace on Discord/Telegram. Users can list, buy, and sell NFTs stored on the Taiko blockchain, with transactions executed through smart contracts.\n\n### Blockchain-based RPG\nA role-playing game where players collect items or characters represented as NFTs on the Taiko blockchain. Transactions include acquiring, trading, or battling NFTs, all recorded on-chain.\n\n### Proof-of-Attendance Bot\nA bot that issues proof-of-attendance tokens on the Taiko blockchain for users participating in events or meetings within Discord/Telegram channels. Tokens are minted and distributed as proof of participation.\n\n### Token Rewards Bot\nA bot that rewards users with Taiko tokens for completing specific tasks or achievements within Discord/Telegram communities. Transactions are recorded on-chain, ensuring transparency and immutability.\n\n### Prediction Market Minigame\nA prediction market where users can buy and sell prediction shares on future events or outcomes using Taiko tokens. Smart contracts manage the market and settle transactions based on the correct prediction.\n\n### Blockchain Voting Bot\nA bot that facilitates voting mechanisms on Discord/Telegram using the Taiko blockchain. Each vote is recorded securely on-chain, ensuring transparency and integrity of the voting process.\n\n### Collectible Card Game (CCG)\nA card game where players collect, trade, and battle with digital cards represented as NFTs on the Taiko blockchain. Players can buy, sell, and upgrade their cards using blockchain transactions.\n\n### Decentralized Exchange Bot\nA bot that acts as a decentralized exchange (DEX) within Discord/Telegram channels, allowing users to swap tokens directly using Taiko blockchain smart contracts. It provides a secure and transparent trading environment.\n\n### Blockchain-based Quest Adventure\nAn adventure game where players embark on quests, solve puzzles, and earn rewards stored as NFTs on the Taiko blockchain. Transactions include acquiring quest items, completing challenges, and trading rewards.\n\n\n# Dora Factory\n\nA-MACI (Anonymous Minimal Anti-Collusion Infrastructure) is one of Dora Factory's solutions to address the scalability issues in decentralized governance, such as quadratic governance and beyond. It is based on Zk-SNARK / PLONK and provides privacy protection for on-chain voting. MACI ensures that the blockchain does not need to provide public voting details and can only offer a credible voting result, preventing voters from verifying each other and thus avoiding collusion. A-MACI further ensures that voting details are not visible to administrators, providing a trustless anonymous voting mechanism and allowing everyone to become an A-MACI operator.\n\nWhile Dora Factory develops A-MACI infrastructures, there are many interesting technical and community growth challenges. We offer the following bounties at this year’s Lambda Hack:\n\n## 1 A-MACI Circuit Bug Bounty\n\nThe circuit is the most crucial part of a Zk-SNARK system. If there are issues with the circuit, such as missing necessary constraints, it could provide attackers with means to forge proofs, compromising the system's security.\n\nThe A-MACI system includes four circuits: processDeactivate, processMsg, processTally, and addNewKey. The specific implementations of these circuits can be found at: https://github.com/dorahacksglobal/a-maci-evm/tree/main/circuits\n\nIf you can find bugs in the circuit and even provide solutions, you can receive a bounty reward.\n\n- Minor Bug: $300 each\n- Major Bug: $1500 each\n\n---\n\n## 2 Design a Tool/Product for User Key Management\n\nIn an A-MACI system, users use EdDSA-based public and private keys as their unique identifier. During the lifecycle of A-MACI, users may need to discard old keypair, regenerate new keypair, and use them. Unlike blockchain products that often use various wallet plugins to manage users accounts, there is currently no good A-MACI keypair management tool for browsers.\n\nDesign a tool that allows users to securely manage A-MACI keypair, clearly knowing the status of their corresponding public and private keys. The tool should also be able to sign necessary MACI messages.\n\nAn MVP is required to claim bounty.\n\nPrize: $2500\n\nA non-functional MVP with a good idea will be rewarded $1000 in bounty prize\n\n---\n\n## 3 Design an A-MACI Solution Allowing Variable Voter Voice Credits\n\nSince variable Voice Credits can enable administrators to distinguish voters' identity characteristics, the current A-MACI system from Dora Factory forces all voters to have equal Voice Credits, limiting A-MACI's use cases to some extent.\n\nDesign a solution that supports voters who are assigned different Voice Credits while maintaining the anonymity and anti-collusion features of A-MACI. Depending on the completeness of the solution, different levels of rewards will be offered:\n\n- [A ] Complete circuit/contract code and a write-up about your approach and how a new protocol would work.\n- [B ] Propose a solution with key code snippets to understand the principles. A detailed protocol write-up is required.\n- [C ] Propose a solution without actual code engineering.\n\nPrizes:\n- A - $10000\n- B - $5000\n- C - $2500\n\nNote: submission to this bounty will need to be verified and reviewed by the Dora Factory team, bounty prize release will be delayed until proposed protocol / code is evaluated and verified.\n\n*—---------The following three bounties are community growth bounties —------------*\n\n## 4 Masterplan and deployment of a MACI voting round in any use case\n\n**Details: **\n\nReady to put the power of Minimal Anti-Collusion Infrastructure (MACI) into action? We're challenging you to design, implement, and deploy a MACI voting round for a real-world use case you define. \n\nBecome a MACI voting designer and operator yourself by helping organizations in need to build a functional round. \n\n**Prizes: **\n- Best use case: $400\n- Best voting mechanism: $400\n\n**Submission Requirements:**\n\nYour submission should include the following components: \n- Define and Describe the Use Case:\n - Explain the specific circumstances under which this organization requires MACI voting.\n - Detail the problem or challenge that MACI voting aims to address.\n- Explain the Voting Mechanism:\n - Describe how votes will be counted.\n - Explain the process for determining the final result.\n - Highlight any unique features or improvements in your voting mechanism.\n- Deploy the MACI Voting Round:\n - Use the [Vota Operator Manual](https://docs.dorafactory.org/docs/vota) to guide your deployment. \n - Act as the “operator” to execute this MACI voting round. \n - Provide the deployment link to your MACI voting round. \n\n## 5: Design a MACI voting use case and its voting mechanism for a real community/DAO\n\nReady to put the power of Minimal Anti-Collusion Infrastructure (MACI) into action? We're challenging you to design a MACI voting round for a real-world use case. Try designing a MACI voting system for an existing community/DAO to decentralize their governance! \n\n**Prize**: $150/winner up to 10 winners\n\n**Your submission must include the following:**\n- **Introduction of the Community/DAO:** Briefly introduce the team and community/DAO this MACI voting round serves, and how would MACI empower the community/DAO in operation, governance, fund management, etc..\n- **Links to relevant sites of this community/DAO**.\n- **Define and Describe the Use Case:**\n - Explain the specific circumstances under which this organization requires MACI voting.\n - Detail the problem or challenge that MACI voting aims to address.\n- **Explain the Voting Mechanism:**\n - Describe how votes will be counted.\n - Explain the process for determining the final result.\n - Highlight any unique features or improvements in your voting mechanism.\n\n**Other requirements:**\n- **Non-AI Writing** in the submission.\n- **Prohibited Topics:** Statements on any topics or elements that entail gambling and other crimes are NOT allowed as part of the submission.\n\n## 6: Deploy a MACI round at Dora Vota \n\n**Prize**: $50/winner up to 40 winners\n\n**Intro**\n\n[Dora Vota](https://research.dorahacks.io/2023/07/31/vota) is a specialized blockchain for voting and decentralized community governance.It is designed to support voting rounds for various communities and organizations. The first voting scheme we support is MACI (Minimal Anti-collusion Infrastructure).\n\nIn order to allow everyone to setup and apply MACI easily, Dora Factory has developed a user-friendly [GUI](https://vota.dorafactory.org/) and [CLI](https://github.com/DoraFactory/vota-operator-scripts) for MACI voting round deployment and operation.\n\n**Submission requirements: **\n\nYou should submit the **link to the MACI round** deployed by you and your **Operator’s public key **(required when creating the round). \n\n**How to Deploy a MACI voting round on Vota**\n- Video guide: https://drive.google.com/file/d/1iz63Hivd2v_0xzmMVz5uZmVtnvOhTCda/view?usp=sharing\n- Step-by-step guide\n - Prerequisites https://docs.dorafactory.org/docs/vota/prerequisites\n - Deploy Round https://docs.dorafactory.org/docs/vota/deploy\n - Tally and Proof https://docs.dorafactory.org/docs/vota/tally\n - Troubleshooting https://docs.dorafactory.org/docs/vota/troubleshoot\n\n**Read more:** If you're interested in the mechanisms and details of MACI, you can explore further by reading the following articles:\n- [Minimal anti-collusion infrastructure](https://ethresear.ch/t/minimal-anti-collusion-infrastructure/5413)\n- [MACI anonymization - using rerandomizable encryption](https://ethresear.ch/t/maci-anonymization-using-rerandomizable-encryption/7054)\n- [基于 2-of-2 多方安全计算的 MACI 匿名化方案 ](https://research.dorahacks.io/2023/03/30/mpc-maci-anonymization)(MACI anonymization based on 2-of-2 MPC)\n\nNote: Only Lambda Hack 2024 participants are allowed to claim MACI deployment bounty.\n\n\n# Brevis\nBrevis is a smart ZK coprocessor that empowers smart contracts to trustlessly read historical on-chain states/txs/events and run customizable computations on top at low cost, enabling data-driven dApp UX.\n\n**No ZK knowledge is required!**\n\nBuild with Brevis and win amazing prizes. \n\n## Build Data-driven dApps with Brevis ZK Coprocessor\n**What is required to complete this prize?**\n- Developers are required to integrate [Brevis SDK](https://docs.brevis.network/) into their dApps successfully. \n- The dApps should access historical blockchain states, transactions, and/or events, and run customized business logic/computation on those data through Brevis ZK Coprocessor. \n- The integration should be meaningful: accessing historical states that are also available in the current blockchain states does not count as successful integration. \n- To qualify for the first prize, the dApp must write customized and meaningful computation logic on the data accessed. Simply utilizing historical on-chain data without any computation does not qualify for the first prize.\n- We do consider partial or incomplete integration on a case-by-case basis. For submissions aiming to solve real-world use cases with a clear path towards full integration, we will most likely issue the full amount of the bounty. \n\n**Bounty #1 $2000**\n\n**Bounty #2 $1000**\n\n### [What's Brevis in 2mins](https://twitter.com/brevis_zk/status/1738024191482589685)\n\nExamples:\n- A good example of a successful integration is a t[rading-volume-based fee discount feature in Uniswap V4](https://blog.brevis.network/2023/11/01/uniswap-v4-hook-brevis-zk-coprocessor-data-driven-dex-experiences/). You can find example code for this in the Brevis SDK repo. \n- To understand the core concept of Brevis and what you can build with it, we recommend reading this [Uniswap V4 hook example](https://blog.brevis.network/2023/11/01/uniswap-v4-hook-brevis-zk-coprocessor-data-driven-dex-experiences/) and [this introductory blog](https://blog.brevis.network/2024/01/16/zk-coprocessor-zero-to-hero-1-wtf-can-it-do/). \n- Some specific ideas are\n- Uniswap v4 hooks based on traders' historical trading behaviors \n- Loyalty and user retention features in DeFi, gaming and others\n- User-gating features based on historical user behaviors \n- Trust-free active liquidity management solutions using Brevis to prove on-chain triggers \n- Smart wallet recovery features based on user behaviors and on-chain financial connections\n- Brainstorm with us at our booth!\n- Other examples and inspirations can be found in Brevis's blog, Twitter and the previous programs at the other hackathons:\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/1456547e-c635-408b-ac89-615b6c6b9a80/\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/df4b6a25-6b97-4312-933b-b7771a6d125a/\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/74320761-4ed9-4a01-9248-29c17e7aca77/\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/4c0f3abd-e74e-4ff1-bd07-0d37521c9147/\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/7d2c649c-b521-40b3-9120-c188f64c2cbc/\n\n\n# Marlin\nMarlin provides TEE-based coprocessors to run programs off-chain verifiably via the Oyster marketplace. TEEs or Trusted Execution Environments rely on hardware-based security to provide computational integrity and data confidentiality. Instances can be rented individually or shared using the serverless mode on Oyster. This makes them suitable to run automation or keeper bots, ML models, heavy computations or matching engines as is the case with Kalypso.\n\nKalypso is a decentralized marketplace for efficient zero-knowledge (ZK) proof generation. Its orderbook-based matching engine connects applications with dedicated hardware providers which improves user experience and boosts hardware utilization. Kalypso's modular and composable architecture makes it easy to integrate into any tech stack, zkVM and proving system. A unique feature of Kalypso is its ability to work with private inputs through the use of Trusted Execution Environments (TEEs). \n\nProjects which use Kalypso to delegate ZK proof generation, or Oyster in any way to run off-chain programs or bots will be awarded two prizes:\n\n**Prize #1 $2000**\n\n**Prize #2 $1500**\n\n\nAdditionally, any project that uses either Kalypso or Oyster which doesn’t win the prizes above (and works!) will receive $300 each.\n\nFor support, please reach out directly on Marlin’s Discord server:\n- Website: https://www.marlin.org\n- Twitter: https://twitter.com/MarlinProtocol\n- Telegram: https://t.me/MarlinProtocol\n- Discord: https://discord.gg/xqJfSGY6gR\n\n# Kakarot\n\nKakarot is a ZK-EVM on top of the Starknet and Cairo stack. Kakarot effectively turns StarknetOS chains into dual VM clients (EVM + CairoVM). EVM applications can deploy natively on Starknet, without any modification. Additionally, Kakarot leverages Starkware's STARK prover and proof aggregator (Stone + SHARP), the most battle tested and evolutive prover stack in the industry.\n\nPrizes and bounties are provided for people who are EVM developers or Cairo developers and utilize Kakarot ZK-EVM for dApp or protocol development. Innovative applications on Kakarot would be:\n - **DualVM applications** that leverage Kakarot’s Cairo interoperability module to run Cairo code from the EVM. For example, dApps where 90% of code can be written in Solidity, and 10% of performance-heavy code written as Cairo programs; or EVM adapters wrapping popular Starknet apps that enables EVM interaction with a Cairo application. Interesting verticals to explore for these hybrid dApps can be found below:\n - **DeFi** (AMMs, money markets, etc.)\n - **Gaming**\n - **Social applications** (NFTs, memes etc.)\n - **Token bridges** using Kakarot’s messaging system for NFTs or ERC20 tokens.\n - **ERC4337-compatible dApps** on Kakarot using Pimlico infrastructure\n\nAll bounty winners will get exposure and tweets from Kakarot. \nThe top 3 projects will get:\n - #1: 750$\n - #2: 600$\n - #3: 400$\n\nhttps://docs.kakarot.org\n\n\n# Herodotus\n\nStorage Proofs provide smart contracts with synchronous access to on-chain data and verifiable data feeds across Ethereum layers. Our solutions allow smart contracts to read and process historical and current on-chain data, enabling developers to seamlessly retrieve data from L1 State on L2s, L2 State on L1s, and L2 State on L2s, eliminating the necessity for asynchronous messaging.\n\n## Bounty 1. 🛰️ Best Use of Storage Proof API or Turbo ⸺ $1,500\nUtilize the [Storage Proof API](https://docs.herodotus.dev/herodotus-docs/developers/storage-proof-api) or [Turbo](https://docs.herodotus.dev/herodotus-docs/developers/turbo) to access cross-chain and historical Ethereum data on a supported Layer 2. Develop applications such as a bridge, DeFi app, or other dApps. \n\n**Requirements**\n\nSubmissions must demonstrate actual use of the Storage Proof API or Turbo without mock requests.\n\n## Bounty 2. 🛰️ Best Use of Herodotus Data Processor ⸺ $1,500\nLeverage the [Herodotus Data Processor](https://docs.herodotus.dev/herodotus-docs/developers/data-processor) to develop innovative solutions that demonstrate use of the Herodotus Data Processor to compute over on-chain data. Can either request via [API](https://docs.herodotus.dev/herodotus-docs/developers/api-docs), or [generate trace locally](https://github.com/HerodotusDev/hdp) via cli to connect your project.\n\n**Requirements**\n\nSubmissions must showcase practical implementations with genuine data processing and verifications, without mock requests.\n\n## Use Cases\n\n### Governance\n\nStorage Proofs eliminate the need for bridging by allowing users to prove ownership of assets on another network without actually bridging them. This functionality enables the implementation of L1 token/NFT gated contracts on L2s, offering a seamless integration.\nA perfect example of this use of Storage Proofs and Herodotus is SnapshotX, which leverages Storage Proofs to enable voting based on assets stored on L1. \n\n### Bridging\n\nWith Storage Proofs, you can access historical data, which is highly valuable for powering intent-based systems such as bridges. For instance, one can prove that after a user initiates a transfer from Chain B to Chain A, they have provided liquidity on Chain A. This historical data allows the actor to reclaim funds from escrow, enabling new kinds of bridging designs.\n\n**Additional Materials:**\n\nhttps://github.com/HerodotusDev/yab-herodotus\n\n### Rewarding user activity\n\nHistorical data allows smart contracts to have visibility comparable to what a human can see on Etherscan. This capability enables developers to build smart contracts that retrieve user activity using Historical Data Proofs (HDP). For example, one can prove that a user interacted with a certain protocol more than ten times over the last month. Combined with the advanced features of Starknet and zkSync, such as account abstraction, this functionality can be leveraged to build a paymaster that subsidizes transactions for highly active users.\n\n### Accessing historical randomness\nGenerating random numbers on Ethereum is inherently complicated due to the nature of blockchain technology, more specifically because of deterministic execution and transparency that makes all data visible to anyone, including the validators who can have some control over the block they produce.\n\nIf a random number generation method relies on block-related information, validators could influence the outcome in their favor, or abstain from including transactions that are not favorable to them or other parties subsidizing them.\n\nHere comes RANDAO, a decentralized solution using a commit-reveal scheme directly integrated into the Ethereum protocol and accessible thanks to the block.prevrandao opcode, and injected inside the MIX_HASH property of new block headers.\n\nThe problem is, that this is only accessible on Ethereum L1, making it hard for derived L2s to benefit from it.\n\nThis example DApp allows users to commit to a dice roll (1-6) on Ethereum Sepolia (L1). It then creates a storage proof of the commitment's storage slot and verifies it on zkSync Sepolia (L2).\n\nOn L2, Turbo extracts the MIX_HASH property from the corresponding L1 target block (i.e., a pre-defined future block after the original commitment). It uses it as a source of randomness to determine the dice roll result.\nUltimately, Ethereum Layer 2s with Turbo support can utilize Ethereum RANDAO in a nearly identical manner as if they were accessing RANDAO directly on Ethereum.\n\n**Additional Materials:** \n\nhttps://github.com/HerodotusDev/turbo-zksync-demo\n\n### Reputation based light client for ORUs\n\nLeveraging HDP, it is possible to develop a light client based on a sequencer's reputation. Optimistic rollups, a layer 2 scaling solution, rely on a security model that uses fraud proofs to ensure the integrity of transactions. However, this model results in long finality times as it requires a challenge period to dispute any fraudulent claims. The recent upgrade to permissionless fraud proofs exacerbates this issue, as anyone can post new state roots in the OP Stack, making it difficult to determine trustworthy state roots until they remain undisputed for a week.\n\nA sequencer, identified by an Ethereum address, gains trust by consistently avoiding successful challenges and making accurate claims. This reputation-based system reduces finality time by treating the state root claims of trusted sequencers as valid. The sequencer's reputation is periodically updated using historical data, with any successful challenge resetting their reputation to zero. This ensures that only reliable sequencers are depended upon, enhancing the security and functionality of blockchain ecosystems.\n\nBy implementing this design, we can significantly improve the efficiency and reliability of optimistic rollups. The use of historical data to evaluate sequencer performance and reputation allows for quicker validation of state roots, thus reducing the finality time and increasing the overall throughput of the network. \n\n**Additional Materials:** \n\nhttps://ethresear.ch/t/reputation-centric-light-client-framework-for-optimistic-rollups/19988"},{"id":813,"name":"Submission Guide","slug":"submission-guide","description":"# Getting Started [3-5 MIN]\n\n**1.** **You should submit your BUIDL via [DoraHacks.io](https://dorahacks.io/). Before that, make sure that you already have an account.**\n\nUse the **Log in button** at the upper right corner of the page to access the sign-up options.\n\n

\n\n**Github, crypto wallet** and **email** are supported for creating an account. For BUIDLers, we recommend you to connect the account to your **github** to make more people know what you are building at any time.\n\n*You may be asked to receive a verification code via email. The email may take some time to arrive. No worries! The code will not expire in 10 minutes when you click “send code”.\n\n**2. Before the submission of deadline, please make sure you have added your Github link to the project. You can submit the project first, edit it later before the deadline.**\n\nClick “Submit BUIDL”.\n\n

\n\n> **→ If you already have a BUIDL on DoraHacks**\n\nChoose your BUIDL project from **\"Apply with Existing BUIDL\"** and identify the track you want to join.\n\n> **→ If you want to submit a new BUIDL project**\n\nClick **“Create a new BUIDL”** and fill in the form as required. You'll be directed to \"Apply for Lambda Hack Week\" page after the new BUIDL setup.\n\nFill in the form to offer the information about your project. Note that for demo, demo link and social media, please offer **URLs (with http/https://)**.\n\n

\n\nDon't forget to check \"I agree to the User Agreement\".\n\n

\n\nBack to Application window. Choose your BUIDL project from **\"Apply with Existing BUIDL\"** and identify the track you want to join.\n\n\nYou will then need to select which bounties you are applying into\n\n![image (11).png](https://cdn.dorahacks.io/static/files/1909263ba72cef4ce6661c6456190b52.png)\n\nWhen submission succeeds, you'll see this notification.\n\n

\n\n# Project Verification\n\nAfter verification by the hackathon organizer through the manager portal, your project will be displayed in the [BUIDLs gallery](https://dorahacks.io/hackathon/437/buidl).\n\n# Want to make some changes to your BUIDL?\n\nClick [Avatar] -> [Profile] to enter the Account Center, and click the \"Edit\" button on the top right of the BUIDL to update the BUIDL information.\n\n

\n\n
\n\n

"},{"id":824,"name":"Workshops","slug":"workshops","description":"There will be a lot of exciting workshops throughout the event. Please check the schedule on the [Luma](https://lu.ma/lambdaweek2024-workshops) page and register there to secure your spot.\n\n\n![6th High quality.jpg](https://cdn.dorahacks.io/static/files/190821971a32b96b0720f9442218f29e.jpg)\n![7th High quality.jpg](https://cdn.dorahacks.io/static/files/1908219cd6e92ef897040dd4d34957ae.jpg)\n![8th High quality.jpg](https://cdn.dorahacks.io/static/files/1908219d9671823afce98964d2386954.jpg)"},{"id":828,"name":"Submission Day","slug":"submission-day","description":"# Hackathon Participants, Information for LambdaHackWeek’s Last Day\n\nWe are excited to see the amazing projects you have been working on and are looking forward to your presentations on the DORA platform. Please take note of the following important details for the upcoming judging and closing events:\n\n**Project Submission:**\n\n- **Date:** Tuesday 9th\n- **Time Limit:** 1:00 PM\n- **Submission guide:** https://dorahacks.io/hackathon/lambdahackweek2/submission-guide\n\n**Project Presentations:**\n\n- **Time:** 1:00 PM - 4:00 PM\n- **Location:** Different rooms (specified below), is you apply for more than one bounty, you have to pitch more than one time.\n\n| | Room 1 | Room 2 | Room 3 | Room 4 | Room 5 | Room 6 |\n| --- | --- | --- | --- | --- | --- | --- |\n| 1:00 PM - 1:30PM | OnlyDust | Cartridge | Kakarot | Starkware | Herodotus | Marlin |\n| 2:00 PM - 2:30 PM | Brevis | Aligned | Mina | EigenLayer | RiscZero | Polygon |\n| 3:00 PM - 3:30 PM | Celestia | Taiko | Node 101 | Dora | ZKsync | nil |\n\nTo be elegible for the bounties It is essential that the team attend the venue to be judged in their specified rooms and time. The rooms and their proportions are assigned as follows:\n\n**Closing Ceremony:**\n\n- **Time:** 4:30 PM\n- **Location:** Auditorium\n\nDuring the closing ceremony, we will announce the winners of each bounty. Following the ceremony, we invite you to join us for an afterwork gathering at the catering area, where you can relax and network with fellow participants and judges.\n\nWe look forward to your innovative presentations and wish you the best of luck!"}],"skills":null,"applied":false,"isCurrentHackerRegistered":false,"buidlsCount":43,"applicationsCount":46,"organization":{"id":2415,"name":"LambdaClass","logo":"https://cdn.dorahacks.io/static/files/1901ca6f1c9e5e258a27cda430a8f9e1.png"},"description":"# Lambda Hack Week\n\nA 200 people four-day hacking week from July 6th to 9th in Brussels, during EthCC 2024, aimed at pushing the boundaries of technology.\n\nLambda Week 2024 is the round two of our LambdaZK Week that we hosted in Paris during EthCC 2023.\n\nBesides hacking, our 4 day 200 people hackathon will feature workshops, technical presentations and panels that will address the latest developments in the industry.\n\nMajor topics are:\n- ZK L1 & L2 Apps\n- Interoperabilty\n- Cryptography\n- On-chain game development\n\n# Key dates\n- 6th July 9am Doors Open\n- 6th July 11am Opening Ceremony\n- 9th July 1pm Hackathon stops\n- 9th July 1pm-4pm Judging\n- 9th July 5pm Closing Ceremomy\n\n# Elegible Criteria and Judging\n\nBy participating, you'll have the opportunity to win your share of a substantial prize pool.\n\nThese bounties are judged by the projects issuing the bounty, but also by a jury set by the organization.\n\nIn-person bounty winners will be announced by sponsors during the Closing Ceremony on 9th July, 2024.\n\nAll prizes will be subject to a technical review to ensure genuine work and collaboration\n\n- Teams must have no more than 4 hackers and at least 1 hacker, who are all physically in attendance on 06-09 July 2024 for IRL events.\n- Pre-existing projects are not allowed to be considered for prizes. You may, however, build a new feature for an existing project that is unique and standalone.\n- All codes/repositories required to run your project must be submitted. You cannot steal another team's source code.\n- Judges will make the final decision on whether a project will qualify for prize consideration.\n\n# Bounties\nBounty criteria for each sponsor can be found in [here](https://dorahacks.io/hackathon/lambdahackweek2/bounties)\n\nSponsors will issue rewards based on how closely a project meets the bounty criteria.\n\n# Workshops\nAll the workshops are being uploaded [here](https://lu.ma/lambdaweek2024-workshops)\n\nPlease, register in each one of your interest in order to help with the organization\n\n# Submission Guidelines\nAt a minimum submissions for prizes must have the following to be considered for judging:\n\n- Project Description\n - The name and summary of the project\n - Names of each participants and their contact info (GitHub handle, Twitter handle, Telegram handle, email)\n- Link to publicly visible source code repository\n - Comprehensive README, with a clear description of the project\n - A link to a working demo or test guide\n- Showcase (optional)\n - 2-3 minute video describing the project that presents the idea and showing how it works.\n\n# Venue Rules\n\nTo ensure a great experience for everyone, please follow these rules:\n\n - **Operating Hours:** The venue opens at 9:00 AM and closes at 11:00 PM.\n - **No Smoking:** Smoking is strictly prohibited inside the venue and even in the balcony area.\n - **No Outside Food or Drinks:** Please do not bring food or beverages from outside.\n - **Keep It Clean:** Help us maintain a clean environment by disposing of trash properly.\n - **Report Issues:** If you encounter any issues or see something that needs attention, please contact the organizers as soon as possible.\n - **Be Respectful:** With so many people here for four days, please behave and be nice to each other.\n\nThank you for your cooperation and enjoy the hackathon!","onboardingCompleted":false,"registerFormUrl":null,"preRegisterTime":0,"publicContactHackerHandle":null,"hackersCount":111,"winnerAnnounced":false,"teamCount":0,"tracks":[],"sponsors":[{"id":461,"bounties":[{"id":527,"name":"Aligned","token":"USD","bonus":7500,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":7500,"name":"Aligned","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":462,"bounties":[{"id":530,"name":"ZKsync","token":"USD","bonus":7500,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":7500,"name":"ZKsync","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":463,"bounties":[{"id":532,"name":"nil","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"nil","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":464,"bounties":[{"id":533,"name":"Polygon Miden","token":"USD","bonus":5000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":5000,"name":"Polygon Miden","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":465,"bounties":[{"id":538,"name":"Celestia","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Celestia","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":466,"bounties":[{"id":540,"name":"node101","token":"USD","bonus":4000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":4000,"name":"node101","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":467,"bounties":[{"id":541,"name":"Cartridge","token":"USD","bonus":5000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":5000,"name":"Cartridge","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":468,"bounties":[{"id":542,"name":"EigenLayer","token":"USD","bonus":5000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":5000,"name":"EigenLayer","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":469,"bounties":[{"id":543,"name":"Mina","token":"USD","bonus":5000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":5000,"name":"Mina","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":470,"bounties":[],"bountyCount":0,"totalBonus":0,"name":"Ingonyama","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":473,"bounties":[{"id":548,"name":"Taiko","token":"USD","bonus":1750,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":1750,"name":"Taiko","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":475,"bounties":[{"id":545,"name":"RISC Zero","token":"USD","bonus":1500,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":1500,"name":"RISC Zero","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":476,"bounties":[{"id":555,"name":"Brevis","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Brevis","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":477,"bounties":[{"id":549,"name":"Dora Factory","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Dora Factory","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":478,"bounties":[{"id":556,"name":"Marlin","token":"USD","bonus":3500,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":3500,"name":"Marlin","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":479,"bounties":[{"id":557,"name":"Kakarot","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Kakarot","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":480,"bounties":[{"id":558,"name":"Herodotus","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Herodotus","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":485,"bounties":[{"id":560,"name":"Starknet","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Starknet","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":486,"bounties":[{"id":561,"name":"OnlyDust","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties#onlydust","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties#onlydust"}],"bountyCount":1,"totalBonus":2000,"name":"OnlyDust","logo":null,"weight":1820,"description":"","isCurrentOrg":false}],"bountiesCount":18,"amaciJudgingCount":0,"isPublicBountyJudging":false,"title":"Lambda Hack Week","uname":"lambdahackweek2","imageUrl":"https://cdn.dorahacks.io/static/files/1901caaa28d9e31dd8bff90457cb713c.png","originUrl":null,"startTime":1720267200000,"endTime":1720522800000,"timezone":"180","city":null,"visible":true,"approvalStatus":6,"state":0,"voteUrl":null,"voteMechanism":null,"bonusPrice":150000,"bonusMechanism":null,"followersCount":0,"ecosystem":["Ethereum","ZK","Cryptography","Blockchain","Onchain gaming","Interoperability"],"applyGuide":null,"weight":0,"participationForm":"IRL","field":["Cryptography","zk","blockchain","onchain gaming","interoperability"],"email":null,"contacts":["Telegram","lferrigno"],"externalContacts":null,"telegram":"lferrigno","discord":null,"whatsapp":null,"wechat":null,"prizeFundingEscrowed":0,"token":"USD","prizeSafeForm":0,"prizeSafeNetwork":null,"prizeSafeOwner":null,"prizeSafeWallet":null,"prizeSafePublishDate":null,"hasOnboarding":false,"isPublicTrackJudging":false,"isEndedTrackJudging":false,"question":null,"countryId":19,"cityId":1056469830,"venueName":"The Sparks","venueAddress":"Rue Ravenstein 60, 1000 Bruxelles, Belgium","category":1,"isEnableBounty":true,"isBountyRequired":false,"isEndedBountyJudging":false,"bountiesLimitForBuidl":10,"isMultiTracksAllowed":false,"tracksLimitForBuidl":0,"showIdeaTab":true,"showQuestionTab":true,"showTeamTab":false,"bonusDescription":[],"askHackers":[],"isEnabledQuestions":false,"isEnabledAskHackers":false,"isBuidlsPrivate":false,"trackJudgingMaxScore":100,"bountyJudgingMaxScore":100,"isExtended":false,"oldEndTime":0,"status":2,"isOrganizer":false,"password":null,"isAdmin":false,"isTrackJudge":false,"isBountyJudge":false,"tracksCount":0,"path":"/hackathon/lambdahackweek2","originURL":null,"image":"https://cdn.dorahacks.io/static/files/1901caaa28d9e31dd8bff90457cb713c.png","voteURL":null,"tabs":["{\"schema\":\"HACKATHON_TAB\",\"d\":{\"id\":796,\"name\":\"Bounties Details\",\"slug\":\"bounties-details\",\"description\":\"# General Pool\\nProjects can apply directly to one or multiple bounties, but there will also be a general jury to evaluate all of them.\\n\\nAmong all eligible projects, whether they apply to a specific bounty or not, the jury will select and reward the top ones. Depending on the quality of the projects, the number of rewarded submissions may vary.\\n\\n# Aligned\\nAligned is a decentralized zero-knowledge (ZK) proof verification and aggregation layer for Ethereum. Aligned accelerates Ethereum’s roadmap by making proof verification faster and more affordable.\\n\\nOur bounties will be awarded to projects that build innovative technology using Aligned for ZKP verification, or extend the capabilities of Aligned by contributing to our open-source project.\\n\\nBelow we provide a non-exhaustive list of potential ideas. We invite you to reach out to our team members at Lambda Hackweek to discuss project ideas if you will be using Aligned for your hackathon project!\\n\\n## Requirements\\n- Create a project that demonstrates how Aligned can be used for cheap and fast ZKP verification, thus enabling new types of blockchain infrastructure or consumer dApps (bounties 1 & 2).\\n - The project must use Aligned to verify ZK proofs.\\n - The project must be deployed on the Ethereum Holesky testnet.\\n- Improve the Aligned developer experience (bounty 3).\\n- The project must use a clear [Open Source License](https://choosealicense.com/licenses/): MIT, GNU, Unlicensed, or any standard open source license your team wants.\\n- The project must include appropriate documentation, including:\\n - A README.md that describes the project and rationale, provides backgrounds/biographies of team members, and notes on challenges you faced when building the project.\\n - Easy to follow deployment and execution instructions.\\n - Documentation that allows for others to reproduce your project.\\n \\n## Resources\\n- https://github.com/yetanotherco/aligned_layer\\n- https://docs.alignedlayer.com/\\n\\n## Bounty 1: Infrastructure using Aligned for verification\\n\\n*Build infrastructure using Aligned to verify proofs.*\\n\\n**Prizes:**\\n- 1st place: $4000\\n- 2nd place: $2500\\n- 3rd place: $1000\\n\\nHere is a list of potential ideas:\\n- Fast bridging solutions.\\n - Example: Noble has implemented [ICS23](https://github.com/cosmos/ics23) in SP1 for Tendermint light clients; we would love to see a similar implementation which uses Aligned for verification. (See https://github.com/noble-assets/sp1-ics23-example and https://x.com/SuccinctLabs/status/1805341476689527207)\\n- ZK Oracles.\\n - Implement a basic oracle system on Aligned that queries a price endpoint in rust and generates a proof of this using SP1.\\n- ZK Coprocessors.\\n - Cross-compile [evm-mlir](https://github.com/lambdaclass/evm_mlir) to RISC-V and verify it using SP1 or RISC Zero. Similar to this: https://dev.to/quartztechnology/rethv-building-reth-for-the-risc-v-platform-5f0m[…]503648ce94ea5067168557f221abdfc2bd245b88a385582ebb911a720aa891da7\\n - Compile https://github.com/sigp/lighthouse to RISC-V and verify its execution using SP1 or RISC Zero\\n- Verifiable Machine Learning.\\n - Perform a comparison of running ezkl proving and verification against:\\n - Writing an ML model in https://github.com/huggingface/candle and verifying using SP1 or RISC Zero\\n- Verify a verkle proof using Aligned.\\n - Example: https://github.com/crate-crypto/rust-verkle with SP1\\n- Verify a ssz proof using Aligned.\\n - Example: https://github.com/ralexstokes/ssz-rs with SP1\\n- Build an application using a multi proof system that leverages Aligned. Use multiple rust provers and/or Gnark to have a more robust application, that needs multiple proving systems to agree before doing an action\\n- Build the first ZK rollup on top of Aligned (either create only the smart contracts with a simple State Transition Function)\\n- Soft finality solutions for Rollups and Appchains.\\n- New settlement layers (use Aligned + EigenDA) for Rollups and Intent based systems.\\n- Encrypted mempools using SNARKs to show the correctness of the encryption.\\n- Alternative L1 <> Ethereum interoperability solutions.\\n- Cheap verification and interoperability for identity protocols.\\n- New credential protocols such as zkTLS based systems.\\n- P2P protocols based on SNARKs such as payment systems and social networks.\\n- Based Rollup infrastructure.\\n- ZK-based onchain gaming infrastructure.\\n\\n## Bounty 2: Consumer dApps using Aligned for verification\\n*Build fun games & puzzles using Aligned and unleash your creativity.*\\n\\n*This bounty will be awarded to projects which use Aligned to build something that can engage consumers and create fun onchain experiences for users. Judging will take into account user experience, virality, and ease of taking live onto mainnet.*\\n\\n**Prizes:**\\n- 1st place: $4000\\n- 2nd place: $2500\\n- 3rd place: $1000\\n\\n**Here is a list of potential ideas:**\\n- ZK Games in Aligned\\n - ZK Wordle and then mint an NFT in Ethereum\\n - ZK Sudoku and then mint an NFT in Ethereum\\n - ZK Tetris with an onchain leaderboard\\n- Run a compiler in SP1 or RISC Zero and post a proof to Aligned.\\n- Migrate any Halo2 games and examples to Aligned.\\n- Run Doom with RISC Zero/SP1 on Aligned.\\n\\n## Bounty 3: Build Aligned Tooling\\n*Help accelerate Aligned’s roadmap by contributing to our project and extending its capabilities.*\\n\\n**Prizes:**\\n- 1st place: $4000\\n- 2nd place: $2500\\n- 3rd place: $1000\\n\\nHere is a list of potential ideas:\\n- Build a Go, Python, or Typescript SDK for interacting with Aligned.\\n- Tooling to improve the Aligned developer experience.\\n\\n\\n# ZKsync \\nzkSync Era is a Layer-2 protocol that scales Ethereum with cutting-edge ZK tech. Our mission is not only to increase Ethereum's throughput merely but to fully preserve its foundational values – freedom, self-sovereignty, decentralization – at scale.\\n\\n## Bounty 1: Build an application using Native Account Abstraction on ZKsync\\n\\nNative Account Abstraction on ZKsync Era fundamentally changes how accounts operate by introducing the concept of Smart Accounts and Paymasters. Smart Accounts are fully programmable, allowing for various customizations such as signature schemes, native multi-sig capabilities, spending limits, and application-specific restrictions. Paymasters can sponsor transactions for users, enabling users to pay transaction fees in ERC20 tokens.\\n\\nThis bounty is for projects that demonstrate innovative uses of native account abstraction. \\n\\nPrizes:\\n- 1st: 4000\\n- 2nd: 2500\\n- 3rd: 1000\\n\\n## Bounty 2: Build a ZK app on ZKsync Era\\nThis bounty is for projects that demonstrate innovative uses of ZK technology on ZKSync Era. \\n\\nPrizes:\\n- 1st: 4000\\n- 2nd: 2500\\n- 3rd: 1000\\n\\n## Requirements for bounty 1 and bounty 2\\n- Project must be deployed on zkSync Sepolia Tesnet\\n- Documentation should include:\\n - a clear README.md with the following:\\n - a clear short one-sentence description of your dapp. Aim for something simple like: “Easy social recovery via Telegram” or “Customizable long-term vaults on smart contract accounts to prevent thefts from hacking”.\\n - short description of team and backgrounds.\\n - a clear installation/execution process that works.\\n - A clear Open Source License: MIT, GNU, Unlicensed or any standard open source license your team wants.\\n - Have a Project Description section including the problem being solved and any issues you ran into.\\n- Bonus: \\n - Create a tutorial and document your code projects for others to replicate\\n### Resources\\n\\nQuickstart: https://docs.zksync.io/build/quick-start/hello-world.html\\n\\nDocumentation: https://docs.zksync.io/build/\\n\\nDeveloper Tools: https://docs.zksync.io/build/tooling/zksync-cli/getting-started.html\\n\\nNative Account Abstraction (AA) on zkSync: \\nhttps://docs.zksync.io/build/developer-reference/account-abstraction.html.\\n \\nNative AA vs EIP4337: https://docs.zksync.io/build/developer-reference/differences-with-ethereum.html#native-aa-vs-eip-4337\\n\\nExamples: daily spend limit smart account: https://docs.zksync.io/build/tutorials/smart-contract-development/account-abstraction/daily-spend-limit.html\\n\\nExamplel: ERC20 token paymaster: https://docs.zksync.io/build/tutorials/smart-contract-development/paymasters/custom-paymaster-tutorial.html\\n\\nRepository: paymaster examples: https://github.com/matter-labs/paymaster-examples\\n\\n# Starknet\\n\\nBuild any cool stuff using one or multiple elements of the Starknet stack.\\n\\nFew ideas:\\n- Onchain game using Dojo\\n- Innovative dApp on Starknet\\n- Hack on Stone prover or Stwo prover\\n- Contribute to the Bitcoin Circle Stark verifier\\n- Performance optimisations on any component of the Starknet stack\\n- Build your custom Starknet Appchain using Madara\\n\\n## Prizes\\n- 1st: $4,000\\n- 2nd: $2,500\\n- 3rd: $1,000\\n\\n## Resources\\n\\n- [Cairo Book](https://book.cairo-lang.org/)\\n- [Starknet documentation](https://docs.starknet.io/)\\n- [Garaga - State-of-the-art Elliptic Curve operations and SNARKS verification for Cairo & Starknet](https://github.com/keep-starknet-strange/garaga)\\n- [Bitcoin Circle STARK verifier](https://github.com/Bitcoin-Wildlife-Sanctuary/bitcoin-circle-stark)\\n- [STWO - Next Gen Prover](https://github.com/starkware-libs/stwo)\\n- [Madara](https://github.com/keep-starknet-strange/madara)\\n\\n# nil\\n=nil; is an Ethereum L2 blockchain leveraging zkSharding to enhance scalability through horizontal scaling, modularity, and verifiable security. Our architecture supports parallel transaction processing across multiple execution shards, each validated by zero-knowledge proofs (ZKPs) and EVM opcode compatibility. Interoperability among these shards is seamlessly maintained through a native cross-shard communication protocol, enabling efficient and secure interactions within the network.\\n\\nWe are offering bounties for developers who choose to build dApps on top of our cluster. This is your opportunity to be among the first to explore and code on =nil;. We encourage you to start small and expand your efforts as you learn more about our technology. We will do our best to provide support both online and offline to assist you throughout the hackathon.\\n\\nWe are offering a total bounty of $3,500, distributed as follows:\\n- 1st Prize: $1,200\\n- 2nd Prize: $1,000\\n- 3rd Prize: $800\\n\\nAddition **$500 Pool** which will be shared among participants who submit any qualifying dApp project beyond the top three prizes\\n\\n**Additional Resources:**\\n- Official =nil; Documentation: https://docs.nil.foundation/nil/intro\\n- =nil; Hardhat Example: https://github.com/NilFoundation/nil-hardhat-example\\n\\n**If you want to join our bounties and build on =nil;, get in touch with our team lead Aleksa Opacic for access to the network and all the details. Find Aleksa on Telegram @aleksaopacic**\\n\\n## Project Suggestions\\n\\nWe welcome any dApp as a submission for the hackathon. The only mandatory requirement is that it's deployed on the =nil; cluster and users can interact with it. If you are unsure of what to build, here are a few suggestions that we would be excited to see:\\n1. **Custom Wallets:** Understand how wallets work in =nil; and create a novel wallet implementation that could be adopted by various projects within our ecosystem. For example, consider developing vesting wallets that could leave a lasting mark on the =nil; ecosystem.\\n2. **Async Messages Coordinator:** Explore how you can coordinate asynchronous messages at the application level to enhance cross-shard communication. This could be a crucial tool for developers looking to optimize interactions across shards.\\n3. **NFT Standard Development:** Develop a straightforward NFT standard for =nil;\\n4. **Applications Utilizing Cross-Shard Communication:** Asynchronous communication allows us to unlock horizontal scalability. Think of applications that can make use of this additional scale for better and more valuable user experiences.\\n\\n# Polygon Miden\\nPolygon Miden is a zkRollup with client-side proving. Anyone can create zk proofs of their own state changes, and the rollup only verifies. That leads to high throughput and privacy at the same time. \\n\\nWe are currently on the alpha testnet. The Miden client is available in Rust and WASM for you to build applications. However, smart contract development must be done in Miden Assembly - it’s easier than it sounds.\\n\\nMore info: https://hackmd.io/@Domi2000/rJZ7Ms6BC\\n\\n**** **All bounty applications will be open source, with the full source code available on GitHub.**\\n\\n## Bounty #1 $5000 in MATIC - ECDSA signatures in Miden (secp256k1)\\n\\nFor any cross-chain application on Miden, we will need to verify signatures. Most signatures in the Ethereum and Bitcoin ecosystem are secp256k1.\\n\\nCurrently, it is inefficient to use elliptic curve cryptography in the Miden VM and, therefore, in the rollup. However, most cross-chain applications or encryption techniques are based on elliptic curve cryptography, mainly secp256k1. \\n\\nFind a way to make ECDSA signature verification cheap (<1m cycles) and efficient on Miden - that can be via a [chiplet](https://0xpolygonmiden.github.io/miden-vm/design/chiplets/main.html) (~ Co-Processor) or any other technique. \\n\\n## Bounty #2 $5000 in MATIC - FRI in a chiplet\\n\\nOne of the primary goals of the Miden VM is to achieve very efficient recursive STARK proof verification (see Bobbin’s [zkSummit talk](https://www.youtube.com/watch?v=uL2J31dQfLI) for a high-level overview). One of the main components of verifying STARKs is verifying FRI proofs. For example, verifying a FRI proof for a computation that requires 1M cycles in the Miden VM takes up 20K+ cycles (which is roughly ⅓ of the entire STARK proof verification cost).\\n\\nCurrently, FRI proof verification procedure in Miden VM is written in MASM. One of the main components of this procedure is verifying correctness of a single FRI query (see [here](https://github.com/0xPolygonMiden/miden-vm/blob/next/stdlib/asm/crypto/fri/frie2f4.masm#L179)). This procedure can be sped up dramatically if most (or all) of the logic is offloaded to a dedicated [chiplet](https://0xpolygonmiden.github.io/miden-vm/design/chiplets/main.html).\\n\\nThe goal of this challenge is to design a Miden VM chiplet to reduce the [verify_query](https://github.com/0xPolygonMiden/miden-vm/blob/next/stdlib/asm/crypto/fri/frie2f4.masm#L179) procedure to as few instructions as possible (ideally, a single new instruction in the VM). This would primarily consist of defining the AIR (intermediate algebraic representation) for the chiplet.\\n\\nA successful design would use the existing chiplet architecture, though, some modifications of the architecture are possible (e.g., some minor increase in the number of columns is OK). We can also assume that the chiplet can “make calls” to other chiplets for things like hashing, reading/writing memory etc.\\n\\n## Bounty #3 $4000 in MATIC - Prototype of a novel application on Miden\\n\\nMiden’s properties allow builders to build applications that are infeasible on EVM-chains. Privacy, native account abstraction, and parallel transaction execution open the design space for novel applications and experiments. \\n\\nThe applications could be in DeFi, RWAs, or on-chain voting. One example is the [on-chain order book](https://github.com/0xPolygonMiden/examples/discussions/138) on Miden.\\n\\nThe most useful novel application that works as a Proof of Concept wins this bounty.\\n\\n## Bounty #4 $4000 in MATIC - Prototype a game on Miden\\n\\nPrototype a game which is multiplayer(preferred) and involves hiding/revealing information as gameplay mechanism and client side proving as a means to improve the gameplay experience.\\n\\nExamples: Fog of War and Dark Forest.\\n\\n## Bounty #5 $3000 in MATIC - Send funds privately from browser to browser\\n\\nUse the [Miden client npm package](https://www.npmjs.com/package/@demox-labs/miden-sdk?activeTab=readme) to build an in-browser payment application using private notes. Clients could communicate via encrypted emails or WebRTC. However, this should be abstracted away from the user. For this bounty, most technology is already there, and the bounty is about the UX. \\n\\nThe most private and best-designed application wins this bounty.\\n\\n# Celestia\\nThe first modular blockchain network, Celestia is a modular data availability network that makes it easy for anyone to securely launch their own blockchain. You can build whatever by rapidly launching a blockchain with leading Ethereum rollup frameworks or transform nearly any VM into your own sovereign chain. With Celestia underneath, a customizable blockchain becomes as easy to deploy as a smart contract, while accessing abundant throughput enabled by data availability sampling (DAS), the first architecture that scales while maintaining verifiability for any user.\\n\\n**Build Whatever Bounty $2000** - Build whatever while still leveraging Celestia DA. The prize goes to the best hack with Celestia DA overall. To qualify, you can build something with a predefined rollup stack like OP Stack, Arbitrum Orbit (can leverage Stylus), Madara, or build something using Rollkit, Sovereign SDK, a game with Katana or something completely new! \\n\\n\\n**Modular Builder Bounty $2000** - Awarded to the best hack that combines Celestia and any other piece of the modular stack, specially from other sponsors (think Celestia DA for Taiko, or combining Aligned layer with Celestia DA, etc)\\n\\n[https://docs.celestia.org/\\n](https://docs.celestia.org/)\\n\\n[Hack Ideas\\n](https://celestiaorg.notion.site/Lambda-Hack-Week-Ideas-Celestia-66d85f8b6a514f44afc95eaae4d6e482)\\n\\n# node101\\n\\nnode101 is thrilled to support innovation in the modular ecosystem by offering bounties to developers who bring the modularity of Cosmos and the privacy & scalability of zero knowledge together. For instance, you may develop a Cosmos SDK project with ZK, integrate Cosmos SDK in your hackathon project, integrate IBC technology into your ZK application, or implement some ZK functionality to an existing Cosmos chain. Nevertheless, be bold to explore new ideas and feel free to reach in case you have any questions.\\n\\n[Cosmos SDK](https://docs.cosmos.network/) is a powerful framework that simplifies the creation of custom blockchains, enabling developers to focus on building applications rather than infrastructure. By leveraging Cosmos SDK, projects can benefit from the robust CometBFT consensus engine, interoperability with other blockchains through IBC (Inter-Blockchain Communication), and a modular architecture that promotes rapid development and scalability. Some of the big projects that are using Cosmos’s technology that you may have heard of are [Cosmos Hub](https://hub.cosmos.network/main), [Celestia](https://celestia.org/), [Osmosis](https://osmosis.zone/), [Agoric](https://agoric.com/), [Akash](https://akash.network/), [Injective](https://injective.com/), [Namada](https://namada.net/), [Penumbra](https://penumbra.zone/), [Fetch.ai](http://Fetch.ai), [dYdX](https://dydx.exchange/), and [Bera Chain](https://www.berachain.com/).\\n\\nIn this hackathon, we aim for more ZK developers to join the modular ecosystem of Cosmos. We believe in modularity more than anything, and we want more people to be a part of the modular change. Just reach out to our team to explore!\\n\\nE-Mail: yunus@node101.io or necip@node101.io \\n\\nTelegram: @ygurlek or @necipsagiro\\n\\n## Docs and Resources\\n\\n- Explore all the Cosmos SDK projects: https://cosmos.network/ecosystem/apps/\\n- All the developer docs you need: https://docs.cosmos.network/\\n- Learn Cosmos with Interchain Foundation’s academy: https://ida.interchain.io/ \\n- Cosmos SDK GitHub: https://github.com/cosmos/cosmos-sdk \\n\\n## Bounty Details\\n\\nWe are excited to offer a total of $4,000 worth of ATOM tokens for this year’s Lambda Week.\\n\\n1. 1st Place: $2,000 worth of ATOM\\n2. 2nd Place: $1,250 worth of ATOM\\n3. 3rd Place: $750 worth of ATOM\\n\\n## Eligibility Criteria\\nTo qualify for the bounty, projects must:\\n- Be integrating to an existing Cosmos SDK project or using Cosmos SDK or Cosmos related technology (like IBC),\\n- Using ZK for a meaningful functionality inside the project,\\n- Make a meaningful contribution to the ecosystem or show inspirational use case,\\n- Have a working proof of concept demonstration,\\n- Implement modular structure and write clean code,\\n- Provide clear documentation and a explanation of the project,\\n- Have all the code public in GitHub.\\n\\nNevertheless, be bold to explore new ideas and propose your own project. Just discuss with our team before!\\n\\n## Submission Guidelines\\n- Submit a link to your project’s public repository (GitHub, GitLab, etc.).\\n- Include a detailed README file with the project motivation, an overview of the project, and an explanation of how ZK is integrated to the Cosmos SDK or Cosmos related chain.\\n- Also, it is preferable to submit a PR to the Cosmos SDK or related chain if applicable\\n\\n## Judging Criteria\\n\\nProjects will be judged based on the following factors:\\n- Innovation: How unique and creative is the solution?\\n- Technical Implementation: How well is ZK and Cosmos integrated and utilized?\\n- Impact: What potential impact could this project have in the real world?\\n- Documentation and Presentation: How clear and comprehensive is the documentation and presentation of the project?\\n\\nWe look forward to seeing the innovative projects you create using Cosmos SDK and wish all participants the best of luck in the hackathon!\\n\\n# Cartridge\\nCartridge leads the development of the Dojo Engine and other tools and infrastructure for building and deploying Fully Onchain Games (FoCG) and Autonomous Worlds (AW).\\n\\nDojo is an open source framework for building provable Games, Autonomous Worlds and other Applications that are composable, extensible, permissionless and persistent. Dojo is an extension of Cairo, an efficiently provable language, that supports generation of zero-knowledge proofs attesting to a computations validity and enables exponential scaling of onchain computation while maintaining the security properties of Ethereum.\\n\\nPrizes will be awarded to teams for \\n1. Best Dojo Games,\\n2. Best Dojo Games Deployed with Slot, \\n3. Best Dojo Games Integrated with Controller!\\n\\n3x $1,000 Prizes for the Best Games Built with [Dojo](https://book.dojoengine.org/)\\n\\n2x $500 Prizes for Best Games Deployed with [Slot](https://book.dojoengine.org/toolchain/slot)\\n\\n2x $500 Prizes for Best Games Integrated with [Controller](https://docs.cartridge.gg/controller/getting-started)\\n\\nJudging is subjective, but it will be based on the criteria listed below:\\n1. Novel use of the unique properties of the Dojo Engine\\n2. Originality of concept, game mechanics, visual design, etc.\\n3. Compelling visual and game design\\n4. Level of fun\\n\\n### Resources\\n[Dojo Book\\n](https://book.dojoengine.org/)\\n\\n[Slot Documentation\\n](https://book.dojoengine.org/toolchain/slot)\\n\\n[Controller Documentation\\n](https://docs.cartridge.gg/controller/getting-started)\\n\\n[Dojo Basecamp Workshop\\n](https://www.youtube.com/live/BzhN3T5U3PA)\\n\\n# EigenLayer\\n\\nEigenLayer enables developers to build arbitrary distributed systems on top of the Ethereum trust network. It extends the security of Ethereum outside the EVM, making it an order of magnitude easier to build decentralized networks.\\n\\n### Prizes\\nBest use of existing EigenLayer AVS - $2,000.00\\n\\nBest new EigenLayer AVS - $3,000.00\\n\\n### Resources\\nAVS Book: https://eigenlabs.gitbook.io/avs-book\\n\\nAwesome AVS: https://github.com/Layr-Labs/awesome-avs\\n\\n# Mina\\nMina Protocol is the world’s first zero knowledge proof verification L1 that enables zero knowledge proof based decentralized applications development on top of it. The entire Mina blockchain can be verified as a zero knowledge proof, thus enabling a constant sized block history: the entire Mina state history can be expressed in 22 KBs! o1js is the name of the typescript framework that is used to generate zero knowledge proofs that can be verified both inside and outside the Mina blockchain. o1js proofs are constant both in proof size and verification time. It also enables one of the world’s best performant proof aggregation technologies through proof recursion.\\n\\nThis year, Mina Protocol will be sponsoring the Lambda Hackathon with a total budget of **15,000 MINA**. You may find more information about the bounty details and the technology below. If you have any questions about the bounties or Mina’s technology in general, please feel free to reach!\\n- E-Mail: yunus.gurlek@minaprotocol.com\\n- Telegram: @ygurlek\\n- Twitter: @yunusguerlek\\n### Some Resources \\n- [Mina Docs - zkApps](https://docs.minaprotocol.com/zkapps/o1js): Mina Docs include a low of valuable information for you to build amazing zkApps (zero knowledge applications)\\n- [Mina Docs - Tutorials](https://docs.minaprotocol.com/zkapps/tutorials): Tutorials are the perfect way to start learning o1js from scratch.\\n- [Mina Docs - o1js Reference](https://docs.minaprotocol.com/zkapps/o1js-reference): You may find more information on o1js modules and methods in the official reference.\\n- [Minascan](https://minascan.io/directory) and [ZKOK](https://zkok.io/): List of current projects in Mina.\\n- [Detailed o1js Article](https://docs.google.com/document/d/1SA3VOi3KVVdl09q4010HgtUzTWWnYTG-95lvtmQlJFI/edit?usp=sharing): This work in progress article may be helpful to understand o1js in more detail.\\n- [Hackathon Project Ideas](https://docs.google.com/document/d/1Ufin1p7zgalFcsss5V_DscEGOFIDXRhmiwjhmCER26g/edit?usp=sharing): Finally, you may find some project ideas here to help you start building on Mina.\\n\\n## General Qualification Requirements\\nAll the projects that want to be considered for Mina’s trach must qualify the following criterias:\\n- All projects must be using o1js for some zero knowledge proof related functionality (both inside and outside Mina Protocol is accepted).\\n- Zero knowledge proofs (ZKPs) must be a valid part of the project and must show some unique functionality that is not possible without ZKPs.\\n- All of the code must be written during the hackathon, with the only exception of ZK gaming projects. Please find more information below.\\n- All of the code must be in GitHub (or some other Git management tool) and public. Please keep your code public for reference and inspiration to other developers after the hackathon as well.\\n- All of the code must be original. You may of course use some other o1js library or project to not reimplement some functionality, but this must be properly documented in your code. Also note that your project will not receive any credits for the libraries you have used without implementing any new functionality.\\n\\nPlease always communicate with us to make sure your project meets all the requirements. We are 7/24 here to help you.\\n\\n### Main Prize Pool\\nAll projects that qualify for the general qualification requirements will be considered for these prizes. In addition to the MINA award that your project will receive, your project will directly qualify for [Mina’s Navigators Starter Grant](https://minafoundation.notion.site/Mina-Navigators-Season-2-72ccd35e45304bc98dbeec88c1ca2056) (that is equivalent to an additional grant of 5000 MINA).\\n\\nPlease note that Mina neither requires, nor wants the projects on top of it to be solely using Mina’s technology. Mina is one of the world’s strongest ZKP verification and settlement layers, and it has amazing capabilities, but for some other use cases integrating different technologies may make sense for the project. Thus, please be aware that we support cross chain projects and encourage you to discover new possibilities by including as many technologies as possible in your projects.\\n\\n- 1st Place: 3500 MINA + Navigators Starter Grant\\n- 2nd Place: 2500 MINA + Navigators Starter Grant\\n- 3rd Place: 1750 MINA + Navigators Starter Grant\\n- 4th Place: 1500 MINA + Navigators Starter Grant\\n- 5th Place: 1250 MINA + Navigators Starter Grant\\n \\n### General Prize Pool\\nAll projects that qualify for the general qualification requirements will be awarded from the general prize pool that worths a total of **4500 MINA**. This amount will be split between all qualifying projects equally. So basically, it is impossible to not be awarded if you are able to finish your project using Mina’s technology 🙂\\n\\nAll projects that qualify for Mina’s bounty will also be considered for a [Navigators Starter Grant](https://minafoundation.notion.site/Mina-Navigators-Season-2-72ccd35e45304bc98dbeec88c1ca2056). Please note that there is no guarantee that you will receive this grant, but there is a really high chance that you will be accepted if you made a meaningful contribution to the Mina ecosystem.\\n\\nAlso, please note that Mina Foundation is more than open to have additional rewards for the projects that show extraordinary success during the hackathon. So do not limit yourself to this document and be bold to explore as much as you can!\\n\\n\\n# RISC Zero\\nIt's now possible to pair a program's output with a self-certifying receipt, allowing a skeptical third party to verify correct execution — and the verifier doesn't need to repeat the original computation or even see the inputs to the program!\\n\\nRISC Zero empowers everyone to create these Verifiable Programs using Zero Knowledge Proofs (ZKPs). Unlike other ZKP domain specific languages and pure arithmetic circuit constructions, RISC Zero provides a Virtual Machine (zkVM) that proves correct execution of a RISC-V compiled program written in any language* !\\n\\n*Rust is by far the most supported for now, but examples in python, C/C++, Wasmtime, and more exist!\\n\\n## 🤩 Best zkVM Application ⸺ $1,500\\n*Up to 3 teams will receive $500*\\n\\nBest RISC Zero zkVM projects - anything that uses our tooling! There are no specific use cases we are looking for, so be as creative as you’d like. ✨\\n\\nQualifications\\n\\nOpen-ended prize! The only strict requirement is that your submission uses the RISC Zero zkVM.\\n## 🤝 ZK Coprocessor ⸺ $1,000\\n*Up to 2 teams will receive $500*\\n\\nThe [RISC Zero Foundry Template](https://github.com/risc0/risc0-foundry-template) makes it easy to get started with both the on-chain and off-chain parts of a [blockchain coprocessor](https://www.risczero.com/blog/a-guide-to-zk-coprocessors-for-scalability) application. This provides a starting point for building powerful new applications on Ethereum that offload computationally intensive (i.e. gas expensive), or would be difficult or impossible to implement Solidity & the EVM.\\n\\nQualifications\\n\\nSubmissions should offload computation from on-chain to off-chain. Special consideration will be given to projects that utilize our [STEEL View Call Proofs Library](https://www.risczero.com/blog/introducing-steel).\\n\\n## 👪 Integrations Bounty ⸺ $1,000\\n\\n*Up to 2 teams will receive $500*\\n\\nThere are so many ways to integrate zk proof systems into various on and off-chain applications to add value and unlock new possibilities - many yet to be discovered! We want to incentivize you to build a novel integration for any other sponsor bounty’s platform.\\n\\nQualifications\\n\\nSubmissions must be new or non-trivial improvements or extensions of RISC Zero integrations with another LambdaHackWeek @ Brussels 2024 sponsor’s platform/tooling/app. Bonus points for those applying for their bounties as well! \\n\\n## 🗃️ Resources\\n- [Getting Started - Dev Docs](https://dev.risczero.com/api/getting-started)\\n- [Getting Started - Video Tutorials](https://www.youtube.com/playlist?list=PLcPzhUaCxlCj7wKkzekYYq7QDvtGTOPm7)\\n- [Awesome RISC Zero\\n](https://github.com/inversebrah/awesome-risc0)\\n- [Demos and Examples](https://dev.risczero.com/api/zkvm/examples)\\n- [STEEL View Call Proof Library](https://github.com/risc0/risc0-ethereum/tree/main/steel)\\n\\n\\n# OnlyDust\\n\\nOnlyDust is a platform that onboards developers to blockchain ecosystems, through open-source contributions. Contribute to the most exciting projects in the space and get rewarded.\\n\\n## Bounties\\n\\nWe will provide $15.000 for eligible contributors that are able to tackle issues for the following repos: \\n\\n### Stellar (1 Repo)\\n\\n[Soroban Example DApp](https://github.com/stellar/soroban-example-dapp/issues): How to build a dapp frontend backed by smart contracts on Stellar.\\n\\n\\n### Proof of Passport (1 Repo)\\n\\n[Proof of passport](https://github.com/zk-passport/proof-of-passport) is developing tools allowing users to generate proofs of humanity, nationality and age using their government-issued passport. We want to make it easy to extract the signed data from passport chips and verify it. It unlocks uses cases in proof of unique identity, sybil resistance and selective disclosure of private data.\\n\\n\\n### Worldcoin (1 Repo)\\n\\n[Worldcoin scroll bridge:](https://github.com/dragan2234/worldcoin-scroll-bridge) Build bridge integrations with Scroll. The point of the state bridge contracts in world-id-state-bridge is to have two contracts, one deployed on Ethereum mainnet and the other one on a target L2.\\n\\n\\n# Taiko\\n\\nTaiko is Ethereum’s first Based Layer 2 scaling solution. Based means that Taiko uses (the base layer) Ethereum’s nodes as the sequencers for its blocks. As a result, Taiko inherits all the same economic security guarantees as Ethereum. It also means there is no need for an escape hatch mechanism common with external sequencers. Taiko is also Ethereum equivalent, which means that developers can use all the same tools they’re used to and any contract that runs on Ethereum will also run on Taiko. \\n\\n## Bounty: Build Discord/Telegram Bots and Minigames Utilizing the Taiko Blockchain\\n\\n**Description**: We are excited to announce a hackathon bounty for innovative developers to build Discord and Telegram bots or minigames that integrate with the Taiko blockchain. This is a fantastic opportunity to showcase your skills in blockchain development, engage with a vibrant community, and win some prizes!\\n\\n**Prize Pool**: $1750\\n\\nThe prize money may be divided between up to 3 top prizes. However, if there is one clear standout winner, they may receive the entire prize pool.\\n\\n## Judging Criteria:\\n- Functionality (30%)\\n - How well does the bot or minigame perform its intended functions?\\n - Is the integration with the Taiko blockchain seamless and effective?\\n- Innovation (25%)\\n - How unique and creative is the bot or minigame?\\n - Does it introduce new or interesting use cases for the Taiko blockchain?\\n- User Experience (20%)\\n - Is the bot or minigame easy to use and navigate?\\n - Does it provide a smooth and enjoyable user experience?\\n- Technical Implementation (15%)\\n - Quality of the code and technical implementation.\\n - Efficient use of the Taiko blockchain's features.\\n- Documentation (10%)\\n - Clarity and completeness of the project documentation.\\n - Ease of understanding for other developers or users.\\n\\n## Helpful Resources\\n1. Taiko Blockchain Documentation: https://docs.taiko.xyz\\n2. Discord.js Documentation: https://discordjs.guide/\\n3. Telegraf.js Documentation: https://telegraf.js.org/\\n4. Discord Bot Example: https://github.com/discordjs/discord.js\\n5. Telegram Bot Example: https://github.com/telegraf/telegraf\\n\\nGet creative, dive into the world of Taiko blockchain, and build something amazing! Happy hacking!\\n\\n## Some ideas to get you started:\\n### Tipping bot\\nA bot that allows users to manage a basic Taiko wallet in Discord/TG. They can check their balances and send tokens to other users based on their username. \\n\\n### OTC Trading Bot\\nA bot that facilitates token swaps between users within Discord/Telegram channels using smart contracts on the Taiko blockchain. Users can initiate and confirm token swaps securely.\\n\\n### Decentralized Lottery Minigame\\nA lottery game where participants buy tickets using Taiko tokens. The smart contract on the Taiko blockchain manages ticket purchases, randomly selects a winner, and distributes the prize automatically.\\n\\n### Crypto Trading Simulation\\nA simulation game that mirrors real-time crypto trading on the Taiko blockchain. Players can buy and sell virtual assets, with transactions recorded on-chain to track profits and losses.\\n\\n### NFT Marketplace Bot\\nA bot that acts as a decentralized NFT marketplace on Discord/Telegram. Users can list, buy, and sell NFTs stored on the Taiko blockchain, with transactions executed through smart contracts.\\n\\n### Blockchain-based RPG\\nA role-playing game where players collect items or characters represented as NFTs on the Taiko blockchain. Transactions include acquiring, trading, or battling NFTs, all recorded on-chain.\\n\\n### Proof-of-Attendance Bot\\nA bot that issues proof-of-attendance tokens on the Taiko blockchain for users participating in events or meetings within Discord/Telegram channels. Tokens are minted and distributed as proof of participation.\\n\\n### Token Rewards Bot\\nA bot that rewards users with Taiko tokens for completing specific tasks or achievements within Discord/Telegram communities. Transactions are recorded on-chain, ensuring transparency and immutability.\\n\\n### Prediction Market Minigame\\nA prediction market where users can buy and sell prediction shares on future events or outcomes using Taiko tokens. Smart contracts manage the market and settle transactions based on the correct prediction.\\n\\n### Blockchain Voting Bot\\nA bot that facilitates voting mechanisms on Discord/Telegram using the Taiko blockchain. Each vote is recorded securely on-chain, ensuring transparency and integrity of the voting process.\\n\\n### Collectible Card Game (CCG)\\nA card game where players collect, trade, and battle with digital cards represented as NFTs on the Taiko blockchain. Players can buy, sell, and upgrade their cards using blockchain transactions.\\n\\n### Decentralized Exchange Bot\\nA bot that acts as a decentralized exchange (DEX) within Discord/Telegram channels, allowing users to swap tokens directly using Taiko blockchain smart contracts. It provides a secure and transparent trading environment.\\n\\n### Blockchain-based Quest Adventure\\nAn adventure game where players embark on quests, solve puzzles, and earn rewards stored as NFTs on the Taiko blockchain. Transactions include acquiring quest items, completing challenges, and trading rewards.\\n\\n\\n# Dora Factory\\n\\nA-MACI (Anonymous Minimal Anti-Collusion Infrastructure) is one of Dora Factory's solutions to address the scalability issues in decentralized governance, such as quadratic governance and beyond. It is based on Zk-SNARK / PLONK and provides privacy protection for on-chain voting. MACI ensures that the blockchain does not need to provide public voting details and can only offer a credible voting result, preventing voters from verifying each other and thus avoiding collusion. A-MACI further ensures that voting details are not visible to administrators, providing a trustless anonymous voting mechanism and allowing everyone to become an A-MACI operator.\\n\\nWhile Dora Factory develops A-MACI infrastructures, there are many interesting technical and community growth challenges. We offer the following bounties at this year’s Lambda Hack:\\n\\n## 1 A-MACI Circuit Bug Bounty\\n\\nThe circuit is the most crucial part of a Zk-SNARK system. If there are issues with the circuit, such as missing necessary constraints, it could provide attackers with means to forge proofs, compromising the system's security.\\n\\nThe A-MACI system includes four circuits: processDeactivate, processMsg, processTally, and addNewKey. The specific implementations of these circuits can be found at: https://github.com/dorahacksglobal/a-maci-evm/tree/main/circuits\\n\\nIf you can find bugs in the circuit and even provide solutions, you can receive a bounty reward.\\n\\n- Minor Bug: $300 each\\n- Major Bug: $1500 each\\n\\n---\\n\\n## 2 Design a Tool/Product for User Key Management\\n\\nIn an A-MACI system, users use EdDSA-based public and private keys as their unique identifier. During the lifecycle of A-MACI, users may need to discard old keypair, regenerate new keypair, and use them. Unlike blockchain products that often use various wallet plugins to manage users accounts, there is currently no good A-MACI keypair management tool for browsers.\\n\\nDesign a tool that allows users to securely manage A-MACI keypair, clearly knowing the status of their corresponding public and private keys. The tool should also be able to sign necessary MACI messages.\\n\\nAn MVP is required to claim bounty.\\n\\nPrize: $2500\\n\\nA non-functional MVP with a good idea will be rewarded $1000 in bounty prize\\n\\n---\\n\\n## 3 Design an A-MACI Solution Allowing Variable Voter Voice Credits\\n\\nSince variable Voice Credits can enable administrators to distinguish voters' identity characteristics, the current A-MACI system from Dora Factory forces all voters to have equal Voice Credits, limiting A-MACI's use cases to some extent.\\n\\nDesign a solution that supports voters who are assigned different Voice Credits while maintaining the anonymity and anti-collusion features of A-MACI. Depending on the completeness of the solution, different levels of rewards will be offered:\\n\\n- [A ] Complete circuit/contract code and a write-up about your approach and how a new protocol would work.\\n- [B ] Propose a solution with key code snippets to understand the principles. A detailed protocol write-up is required.\\n- [C ] Propose a solution without actual code engineering.\\n\\nPrizes:\\n- A - $10000\\n- B - $5000\\n- C - $2500\\n\\nNote: submission to this bounty will need to be verified and reviewed by the Dora Factory team, bounty prize release will be delayed until proposed protocol / code is evaluated and verified.\\n\\n*—---------The following three bounties are community growth bounties —------------*\\n\\n## 4 Masterplan and deployment of a MACI voting round in any use case\\n\\n**Details: **\\n\\nReady to put the power of Minimal Anti-Collusion Infrastructure (MACI) into action? We're challenging you to design, implement, and deploy a MACI voting round for a real-world use case you define. \\n\\nBecome a MACI voting designer and operator yourself by helping organizations in need to build a functional round. \\n\\n**Prizes: **\\n- Best use case: $400\\n- Best voting mechanism: $400\\n\\n**Submission Requirements:**\\n\\nYour submission should include the following components: \\n- Define and Describe the Use Case:\\n - Explain the specific circumstances under which this organization requires MACI voting.\\n - Detail the problem or challenge that MACI voting aims to address.\\n- Explain the Voting Mechanism:\\n - Describe how votes will be counted.\\n - Explain the process for determining the final result.\\n - Highlight any unique features or improvements in your voting mechanism.\\n- Deploy the MACI Voting Round:\\n - Use the [Vota Operator Manual](https://docs.dorafactory.org/docs/vota) to guide your deployment. \\n - Act as the “operator” to execute this MACI voting round. \\n - Provide the deployment link to your MACI voting round. \\n\\n## 5: Design a MACI voting use case and its voting mechanism for a real community/DAO\\n\\nReady to put the power of Minimal Anti-Collusion Infrastructure (MACI) into action? We're challenging you to design a MACI voting round for a real-world use case. Try designing a MACI voting system for an existing community/DAO to decentralize their governance! \\n\\n**Prize**: $150/winner up to 10 winners\\n\\n**Your submission must include the following:**\\n- **Introduction of the Community/DAO:** Briefly introduce the team and community/DAO this MACI voting round serves, and how would MACI empower the community/DAO in operation, governance, fund management, etc..\\n- **Links to relevant sites of this community/DAO**.\\n- **Define and Describe the Use Case:**\\n - Explain the specific circumstances under which this organization requires MACI voting.\\n - Detail the problem or challenge that MACI voting aims to address.\\n- **Explain the Voting Mechanism:**\\n - Describe how votes will be counted.\\n - Explain the process for determining the final result.\\n - Highlight any unique features or improvements in your voting mechanism.\\n\\n**Other requirements:**\\n- **Non-AI Writing** in the submission.\\n- **Prohibited Topics:** Statements on any topics or elements that entail gambling and other crimes are NOT allowed as part of the submission.\\n\\n## 6: Deploy a MACI round at Dora Vota \\n\\n**Prize**: $50/winner up to 40 winners\\n\\n**Intro**\\n\\n[Dora Vota](https://research.dorahacks.io/2023/07/31/vota) is a specialized blockchain for voting and decentralized community governance.It is designed to support voting rounds for various communities and organizations. The first voting scheme we support is MACI (Minimal Anti-collusion Infrastructure).\\n\\nIn order to allow everyone to setup and apply MACI easily, Dora Factory has developed a user-friendly [GUI](https://vota.dorafactory.org/) and [CLI](https://github.com/DoraFactory/vota-operator-scripts) for MACI voting round deployment and operation.\\n\\n**Submission requirements: **\\n\\nYou should submit the **link to the MACI round** deployed by you and your **Operator’s public key **(required when creating the round). \\n\\n**How to Deploy a MACI voting round on Vota**\\n- Video guide: https://drive.google.com/file/d/1iz63Hivd2v_0xzmMVz5uZmVtnvOhTCda/view?usp=sharing\\n- Step-by-step guide\\n - Prerequisites https://docs.dorafactory.org/docs/vota/prerequisites\\n - Deploy Round https://docs.dorafactory.org/docs/vota/deploy\\n - Tally and Proof https://docs.dorafactory.org/docs/vota/tally\\n - Troubleshooting https://docs.dorafactory.org/docs/vota/troubleshoot\\n\\n**Read more:** If you're interested in the mechanisms and details of MACI, you can explore further by reading the following articles:\\n- [Minimal anti-collusion infrastructure](https://ethresear.ch/t/minimal-anti-collusion-infrastructure/5413)\\n- [MACI anonymization - using rerandomizable encryption](https://ethresear.ch/t/maci-anonymization-using-rerandomizable-encryption/7054)\\n- [基于 2-of-2 多方安全计算的 MACI 匿名化方案 ](https://research.dorahacks.io/2023/03/30/mpc-maci-anonymization)(MACI anonymization based on 2-of-2 MPC)\\n\\nNote: Only Lambda Hack 2024 participants are allowed to claim MACI deployment bounty.\\n\\n\\n# Brevis\\nBrevis is a smart ZK coprocessor that empowers smart contracts to trustlessly read historical on-chain states/txs/events and run customizable computations on top at low cost, enabling data-driven dApp UX.\\n\\n**No ZK knowledge is required!**\\n\\nBuild with Brevis and win amazing prizes. \\n\\n## Build Data-driven dApps with Brevis ZK Coprocessor\\n**What is required to complete this prize?**\\n- Developers are required to integrate [Brevis SDK](https://docs.brevis.network/) into their dApps successfully. \\n- The dApps should access historical blockchain states, transactions, and/or events, and run customized business logic/computation on those data through Brevis ZK Coprocessor. \\n- The integration should be meaningful: accessing historical states that are also available in the current blockchain states does not count as successful integration. \\n- To qualify for the first prize, the dApp must write customized and meaningful computation logic on the data accessed. Simply utilizing historical on-chain data without any computation does not qualify for the first prize.\\n- We do consider partial or incomplete integration on a case-by-case basis. For submissions aiming to solve real-world use cases with a clear path towards full integration, we will most likely issue the full amount of the bounty. \\n\\n**Bounty #1 $2000**\\n\\n**Bounty #2 $1000**\\n\\n### [What's Brevis in 2mins](https://twitter.com/brevis_zk/status/1738024191482589685)\\n\\nExamples:\\n- A good example of a successful integration is a t[rading-volume-based fee discount feature in Uniswap V4](https://blog.brevis.network/2023/11/01/uniswap-v4-hook-brevis-zk-coprocessor-data-driven-dex-experiences/). You can find example code for this in the Brevis SDK repo. \\n- To understand the core concept of Brevis and what you can build with it, we recommend reading this [Uniswap V4 hook example](https://blog.brevis.network/2023/11/01/uniswap-v4-hook-brevis-zk-coprocessor-data-driven-dex-experiences/) and [this introductory blog](https://blog.brevis.network/2024/01/16/zk-coprocessor-zero-to-hero-1-wtf-can-it-do/). \\n- Some specific ideas are\\n- Uniswap v4 hooks based on traders' historical trading behaviors \\n- Loyalty and user retention features in DeFi, gaming and others\\n- User-gating features based on historical user behaviors \\n- Trust-free active liquidity management solutions using Brevis to prove on-chain triggers \\n- Smart wallet recovery features based on user behaviors and on-chain financial connections\\n- Brainstorm with us at our booth!\\n- Other examples and inspirations can be found in Brevis's blog, Twitter and the previous programs at the other hackathons:\\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/1456547e-c635-408b-ac89-615b6c6b9a80/\\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/df4b6a25-6b97-4312-933b-b7771a6d125a/\\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/74320761-4ed9-4a01-9248-29c17e7aca77/\\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/4c0f3abd-e74e-4ff1-bd07-0d37521c9147/\\n - https://uniswap.atrium.academy/hackathons/hookathon-c1/projects/7d2c649c-b521-40b3-9120-c188f64c2cbc/\\n\\n\\n# Marlin\\nMarlin provides TEE-based coprocessors to run programs off-chain verifiably via the Oyster marketplace. TEEs or Trusted Execution Environments rely on hardware-based security to provide computational integrity and data confidentiality. Instances can be rented individually or shared using the serverless mode on Oyster. This makes them suitable to run automation or keeper bots, ML models, heavy computations or matching engines as is the case with Kalypso.\\n\\nKalypso is a decentralized marketplace for efficient zero-knowledge (ZK) proof generation. Its orderbook-based matching engine connects applications with dedicated hardware providers which improves user experience and boosts hardware utilization. Kalypso's modular and composable architecture makes it easy to integrate into any tech stack, zkVM and proving system. A unique feature of Kalypso is its ability to work with private inputs through the use of Trusted Execution Environments (TEEs). \\n\\nProjects which use Kalypso to delegate ZK proof generation, or Oyster in any way to run off-chain programs or bots will be awarded two prizes:\\n\\n**Prize #1 $2000**\\n\\n**Prize #2 $1500**\\n\\n\\nAdditionally, any project that uses either Kalypso or Oyster which doesn’t win the prizes above (and works!) will receive $300 each.\\n\\nFor support, please reach out directly on Marlin’s Discord server:\\n- Website: https://www.marlin.org\\n- Twitter: https://twitter.com/MarlinProtocol\\n- Telegram: https://t.me/MarlinProtocol\\n- Discord: https://discord.gg/xqJfSGY6gR\\n\\n# Kakarot\\n\\nKakarot is a ZK-EVM on top of the Starknet and Cairo stack. Kakarot effectively turns StarknetOS chains into dual VM clients (EVM + CairoVM). EVM applications can deploy natively on Starknet, without any modification. Additionally, Kakarot leverages Starkware's STARK prover and proof aggregator (Stone + SHARP), the most battle tested and evolutive prover stack in the industry.\\n\\nPrizes and bounties are provided for people who are EVM developers or Cairo developers and utilize Kakarot ZK-EVM for dApp or protocol development. Innovative applications on Kakarot would be:\\n - **DualVM applications** that leverage Kakarot’s Cairo interoperability module to run Cairo code from the EVM. For example, dApps where 90% of code can be written in Solidity, and 10% of performance-heavy code written as Cairo programs; or EVM adapters wrapping popular Starknet apps that enables EVM interaction with a Cairo application. Interesting verticals to explore for these hybrid dApps can be found below:\\n - **DeFi** (AMMs, money markets, etc.)\\n - **Gaming**\\n - **Social applications** (NFTs, memes etc.)\\n - **Token bridges** using Kakarot’s messaging system for NFTs or ERC20 tokens.\\n - **ERC4337-compatible dApps** on Kakarot using Pimlico infrastructure\\n\\nAll bounty winners will get exposure and tweets from Kakarot. \\nThe top 3 projects will get:\\n - #1: 750$\\n - #2: 600$\\n - #3: 400$\\n\\nhttps://docs.kakarot.org\\n\\n\\n# Herodotus\\n\\nStorage Proofs provide smart contracts with synchronous access to on-chain data and verifiable data feeds across Ethereum layers. Our solutions allow smart contracts to read and process historical and current on-chain data, enabling developers to seamlessly retrieve data from L1 State on L2s, L2 State on L1s, and L2 State on L2s, eliminating the necessity for asynchronous messaging.\\n\\n## Bounty 1. 🛰️ Best Use of Storage Proof API or Turbo ⸺ $1,500\\nUtilize the [Storage Proof API](https://docs.herodotus.dev/herodotus-docs/developers/storage-proof-api) or [Turbo](https://docs.herodotus.dev/herodotus-docs/developers/turbo) to access cross-chain and historical Ethereum data on a supported Layer 2. Develop applications such as a bridge, DeFi app, or other dApps. \\n\\n**Requirements**\\n\\nSubmissions must demonstrate actual use of the Storage Proof API or Turbo without mock requests.\\n\\n## Bounty 2. 🛰️ Best Use of Herodotus Data Processor ⸺ $1,500\\nLeverage the [Herodotus Data Processor](https://docs.herodotus.dev/herodotus-docs/developers/data-processor) to develop innovative solutions that demonstrate use of the Herodotus Data Processor to compute over on-chain data. Can either request via [API](https://docs.herodotus.dev/herodotus-docs/developers/api-docs), or [generate trace locally](https://github.com/HerodotusDev/hdp) via cli to connect your project.\\n\\n**Requirements**\\n\\nSubmissions must showcase practical implementations with genuine data processing and verifications, without mock requests.\\n\\n## Use Cases\\n\\n### Governance\\n\\nStorage Proofs eliminate the need for bridging by allowing users to prove ownership of assets on another network without actually bridging them. This functionality enables the implementation of L1 token/NFT gated contracts on L2s, offering a seamless integration.\\nA perfect example of this use of Storage Proofs and Herodotus is SnapshotX, which leverages Storage Proofs to enable voting based on assets stored on L1. \\n\\n### Bridging\\n\\nWith Storage Proofs, you can access historical data, which is highly valuable for powering intent-based systems such as bridges. For instance, one can prove that after a user initiates a transfer from Chain B to Chain A, they have provided liquidity on Chain A. This historical data allows the actor to reclaim funds from escrow, enabling new kinds of bridging designs.\\n\\n**Additional Materials:**\\n\\nhttps://github.com/HerodotusDev/yab-herodotus\\n\\n### Rewarding user activity\\n\\nHistorical data allows smart contracts to have visibility comparable to what a human can see on Etherscan. This capability enables developers to build smart contracts that retrieve user activity using Historical Data Proofs (HDP). For example, one can prove that a user interacted with a certain protocol more than ten times over the last month. Combined with the advanced features of Starknet and zkSync, such as account abstraction, this functionality can be leveraged to build a paymaster that subsidizes transactions for highly active users.\\n\\n### Accessing historical randomness\\nGenerating random numbers on Ethereum is inherently complicated due to the nature of blockchain technology, more specifically because of deterministic execution and transparency that makes all data visible to anyone, including the validators who can have some control over the block they produce.\\n\\nIf a random number generation method relies on block-related information, validators could influence the outcome in their favor, or abstain from including transactions that are not favorable to them or other parties subsidizing them.\\n\\nHere comes RANDAO, a decentralized solution using a commit-reveal scheme directly integrated into the Ethereum protocol and accessible thanks to the block.prevrandao opcode, and injected inside the MIX_HASH property of new block headers.\\n\\nThe problem is, that this is only accessible on Ethereum L1, making it hard for derived L2s to benefit from it.\\n\\nThis example DApp allows users to commit to a dice roll (1-6) on Ethereum Sepolia (L1). It then creates a storage proof of the commitment's storage slot and verifies it on zkSync Sepolia (L2).\\n\\nOn L2, Turbo extracts the MIX_HASH property from the corresponding L1 target block (i.e., a pre-defined future block after the original commitment). It uses it as a source of randomness to determine the dice roll result.\\nUltimately, Ethereum Layer 2s with Turbo support can utilize Ethereum RANDAO in a nearly identical manner as if they were accessing RANDAO directly on Ethereum.\\n\\n**Additional Materials:** \\n\\nhttps://github.com/HerodotusDev/turbo-zksync-demo\\n\\n### Reputation based light client for ORUs\\n\\nLeveraging HDP, it is possible to develop a light client based on a sequencer's reputation. Optimistic rollups, a layer 2 scaling solution, rely on a security model that uses fraud proofs to ensure the integrity of transactions. However, this model results in long finality times as it requires a challenge period to dispute any fraudulent claims. The recent upgrade to permissionless fraud proofs exacerbates this issue, as anyone can post new state roots in the OP Stack, making it difficult to determine trustworthy state roots until they remain undisputed for a week.\\n\\nA sequencer, identified by an Ethereum address, gains trust by consistently avoiding successful challenges and making accurate claims. This reputation-based system reduces finality time by treating the state root claims of trusted sequencers as valid. The sequencer's reputation is periodically updated using historical data, with any successful challenge resetting their reputation to zero. This ensures that only reliable sequencers are depended upon, enhancing the security and functionality of blockchain ecosystems.\\n\\nBy implementing this design, we can significantly improve the efficiency and reliability of optimistic rollups. The use of historical data to evaluate sequencer performance and reputation allows for quicker validation of state roots, thus reducing the finality time and increasing the overall throughput of the network. \\n\\n**Additional Materials:** \\n\\nhttps://ethresear.ch/t/reputation-centric-light-client-framework-for-optimistic-rollups/19988\"}}","{\"schema\":\"HACKATHON_TAB\",\"d\":{\"id\":813,\"name\":\"Submission Guide\",\"slug\":\"submission-guide\",\"description\":\"# Getting Started [3-5 MIN]\\n\\n**1.** **You should submit your BUIDL via [DoraHacks.io](https://dorahacks.io/). Before that, make sure that you already have an account.**\\n\\nUse the **Log in button** at the upper right corner of the page to access the sign-up options.\\n\\n

\\n\\n**Github, crypto wallet** and **email** are supported for creating an account. For BUIDLers, we recommend you to connect the account to your **github** to make more people know what you are building at any time.\\n\\n*You may be asked to receive a verification code via email. The email may take some time to arrive. No worries! The code will not expire in 10 minutes when you click “send code”.\\n\\n**2. Before the submission of deadline, please make sure you have added your Github link to the project. You can submit the project first, edit it later before the deadline.**\\n\\nClick “Submit BUIDL”.\\n\\n

\\n\\n> **→ If you already have a BUIDL on DoraHacks**\\n\\nChoose your BUIDL project from **\\\"Apply with Existing BUIDL\\\"** and identify the track you want to join.\\n\\n> **→ If you want to submit a new BUIDL project**\\n\\nClick **“Create a new BUIDL”** and fill in the form as required. You'll be directed to \\\"Apply for Lambda Hack Week\\\" page after the new BUIDL setup.\\n\\nFill in the form to offer the information about your project. Note that for demo, demo link and social media, please offer **URLs (with http/https://)**.\\n\\n

\\n

\\n\\nDon't forget to check \\\"I agree to the User Agreement\\\".\\n\\n

\\n\\nBack to Application window. Choose your BUIDL project from **\\\"Apply with Existing BUIDL\\\"** and identify the track you want to join.\\n\\n\\nYou will then need to select which bounties you are applying into\\n\\n![image (11).png](https://cdn.dorahacks.io/static/files/1909263ba72cef4ce6661c6456190b52.png)\\n\\nWhen submission succeeds, you'll see this notification.\\n\\n

\\n\\n# Project Verification\\n\\nAfter verification by the hackathon organizer through the manager portal, your project will be displayed in the [BUIDLs gallery](https://dorahacks.io/hackathon/437/buidl).\\n\\n# Want to make some changes to your BUIDL?\\n\\nClick [Avatar] -> [Profile] to enter the Account Center, and click the \\\"Edit\\\" button on the top right of the BUIDL to update the BUIDL information.\\n\\n

\\n\\n
\\n\\n

\"}}","{\"schema\":\"HACKATHON_TAB\",\"d\":{\"id\":824,\"name\":\"Workshops\",\"slug\":\"workshops\",\"description\":\"There will be a lot of exciting workshops throughout the event. Please check the schedule on the [Luma](https://lu.ma/lambdaweek2024-workshops) page and register there to secure your spot.\\n\\n\\n![6th High quality.jpg](https://cdn.dorahacks.io/static/files/190821971a32b96b0720f9442218f29e.jpg)\\n![7th High quality.jpg](https://cdn.dorahacks.io/static/files/1908219cd6e92ef897040dd4d34957ae.jpg)\\n![8th High quality.jpg](https://cdn.dorahacks.io/static/files/1908219d9671823afce98964d2386954.jpg)\"}}","{\"schema\":\"HACKATHON_TAB\",\"d\":{\"id\":828,\"name\":\"Submission Day\",\"slug\":\"submission-day\",\"description\":\"# Hackathon Participants, Information for LambdaHackWeek’s Last Day\\n\\nWe are excited to see the amazing projects you have been working on and are looking forward to your presentations on the DORA platform. Please take note of the following important details for the upcoming judging and closing events:\\n\\n**Project Submission:**\\n\\n- **Date:** Tuesday 9th\\n- **Time Limit:** 1:00 PM\\n- **Submission guide:** https://dorahacks.io/hackathon/lambdahackweek2/submission-guide\\n\\n**Project Presentations:**\\n\\n- **Time:** 1:00 PM - 4:00 PM\\n- **Location:** Different rooms (specified below), is you apply for more than one bounty, you have to pitch more than one time.\\n\\n| | Room 1 | Room 2 | Room 3 | Room 4 | Room 5 | Room 6 |\\n| --- | --- | --- | --- | --- | --- | --- |\\n| 1:00 PM - 1:30PM | OnlyDust | Cartridge | Kakarot | Starkware | Herodotus | Marlin |\\n| 2:00 PM - 2:30 PM | Brevis | Aligned | Mina | EigenLayer | RiscZero | Polygon |\\n| 3:00 PM - 3:30 PM | Celestia | Taiko | Node 101 | Dora | ZKsync | nil |\\n\\nTo be elegible for the bounties It is essential that the team attend the venue to be judged in their specified rooms and time. The rooms and their proportions are assigned as follows:\\n\\n**Closing Ceremony:**\\n\\n- **Time:** 4:30 PM\\n- **Location:** Auditorium\\n\\nDuring the closing ceremony, we will announce the winners of each bounty. Following the ceremony, we invite you to join us for an afterwork gathering at the catering area, where you can relax and network with fellow participants and judges.\\n\\nWe look forward to your innovative presentations and wish you the best of luck!\"}}"],"participation":"IRL","escrowed":false,"bounties":[{"id":486,"bounties":[{"id":561,"name":"OnlyDust","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties#onlydust","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties#onlydust"}],"bountyCount":1,"totalBonus":2000,"name":"OnlyDust","logo":null,"weight":1820,"description":"","isCurrentOrg":false},{"id":485,"bounties":[{"id":560,"name":"Starknet","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Starknet","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":480,"bounties":[{"id":558,"name":"Herodotus","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Herodotus","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":479,"bounties":[{"id":557,"name":"Kakarot","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Kakarot","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":478,"bounties":[{"id":556,"name":"Marlin","token":"USD","bonus":3500,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":3500,"name":"Marlin","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":477,"bounties":[{"id":549,"name":"Dora Factory","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Dora Factory","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":476,"bounties":[{"id":555,"name":"Brevis","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Brevis","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":475,"bounties":[{"id":545,"name":"RISC Zero","token":"USD","bonus":1500,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":1500,"name":"RISC Zero","logo":null,"weight":1819,"description":"","isCurrentOrg":false},{"id":473,"bounties":[{"id":548,"name":"Taiko","token":"USD","bonus":1750,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":1750,"name":"Taiko","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":470,"bounties":[],"bountyCount":0,"totalBonus":0,"name":"Ingonyama","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":469,"bounties":[{"id":543,"name":"Mina","token":"USD","bonus":5000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":5000,"name":"Mina","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":468,"bounties":[{"id":542,"name":"EigenLayer","token":"USD","bonus":5000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":5000,"name":"EigenLayer","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":467,"bounties":[{"id":541,"name":"Cartridge","token":"USD","bonus":5000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":5000,"name":"Cartridge","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":466,"bounties":[{"id":540,"name":"node101","token":"USD","bonus":4000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":4000,"name":"node101","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":465,"bounties":[{"id":538,"name":"Celestia","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"Celestia","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":464,"bounties":[{"id":533,"name":"Polygon Miden","token":"USD","bonus":5000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":5000,"name":"Polygon Miden","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":463,"bounties":[{"id":532,"name":"nil","token":"USD","bonus":2000,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":2000,"name":"nil","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":462,"bounties":[{"id":530,"name":"ZKsync","token":"USD","bonus":7500,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":7500,"name":"ZKsync","logo":null,"weight":1818,"description":"","isCurrentOrg":false},{"id":461,"bounties":[{"id":527,"name":"Aligned","token":"USD","bonus":7500,"link":"https://dorahacks.io/hackathon/lambdahackweek2/bounties","description":"https://dorahacks.io/hackathon/lambdahackweek2/bounties"}],"bountyCount":1,"totalBonus":7500,"name":"Aligned","logo":null,"weight":1818,"description":"","isCurrentOrg":false}]}}