$20,000 🦄 The next up, STARTUP prize
What do Orb, Superfluid, and Push Protocol have in common? All 3 of these major web3 projects started at hackathons. Polygon Labs is looking for killer apps and use cases (any type of project: infra / defi / social / privacy/app layer) built with Polygon technology. To qualify for this prize, build something useful with smart contracts on Polygon zkEVM, Polygon PoS or using Polygon ID VCs. Sell us on the use cases or problems your project solves and explain your business plan and the feature roadmap that you’ll continue to build after the hackathon on your path to becoming a startup.
$10,000 ↔️ Best cross chain dApp utilizing the Polygon zkEVM LxLy bridge
gm anon, or should we say ZM. At the heart of Polygon’s new 2.0 architecture lies the LxLy bridge. The Polygon zkEVM LxLy Bridge facilitates cross-chain communication across Polygon chains. We’re challenging you to create and extend the LxLy sample implementations and add support for different types of cross-chain messaging and assets transfer of custom ERC-20s and any other EIP/ERC you see fit such as ERC1155 etc. Check out the existing code samples and open a PR with your own contribution that facilities cross-chain communication.
Cross-Chain ideas from the Polygon zkEVM team
- Claim UI: Build a Dapp to allow users to connect and see all valid messages they have that are claimable on a given LxLy chain (Polygon zkEVM etc.) and claim them!
- Implement an OpenZeppelin Governor that allows token holders to vote on Polygon zkEVM with proposals that are still on Ethereum or Polygon PoS Create a snapshot strategy that accounts for token balance on Ethereum, Polygon PoS, & Polygon zkEVM
- Build a zkEVM NFT project with mint logic that depends on owning an asset on Ethereum or Polygon PoS.
- Permissionless Prover: A smart contract that allows Polygon Labs to put up a reward for anyone who fills in as permissionless prover for when our infra goes down essentially a contract that has a function that checks whether a given verifyBatches() call was successfully called by anyone other than our trusted address, and if so, pays out some fixed reward it holds (MATIC tokens)
- Or even extend these repos to cover LxLy Bridging https://github.com/ZeframLou/universal-bridge or https://github.com/aave/governance-crosschain-bridges/tree/master/contracts/bridges
$10,000 👤 Best Use of Polygon ID for a privacy preserving dApp
Self-Sovereign Identity is the future. Use Polygon ID to represent identity-based information as verifiable credentials in your dapp so your users can prove access rights to dapp features without giving up their private data. Polygon ID is also excited to announce a brand new partnership with Dock.io that will allow you to securely extend the privacy of your Lens profile using Verifiable Credentials. Using Dock's REST API credentials can be issued a few API calls. Along with issuing credentials application developers can use the API to manage issuer profiles and create and import data schemas. Dock's tooling also supports non-developers through it's no-code solution Dock Certs which provides the same functionality via a web interface.
Polygon ID resources:
- Polygon ID Dev Docs and tutorials
- How to run an Issuer to issue VCs: Video by Tony
- Fullstack VC-gated dapp template with everything you need for your KYCAgeCredential gated dapp by Steph
- This demo shows you how to set up your Dock.io account and begin to issue VCs. Your task is to now leverage VCs to provide additional layers of privacy and security to your Lens Dapp.
Ideas from the Polygon ID team:
- Anonymous voting On-chain voting exposes the choices made by different public addresses. Create a hack that proves DAO membership with a VC while making sure members don’t double vote.
- Social proof of influence or activity Create a proof of influence issuer that issues VCs based on numbers of followers or number of posts across social platforms
- Bot protection - Create a decentralized verification system providing individual VCs of liveliness & uniqueness that could be combined to prevent sybil attacks.
- VC gated Discord or telegram channels - Create a way to gate a Discord channel or telegram chat based on a Polygon VC
$10,000 ⛽️ UX award for best dApp with Account Abstraction
Build a dApp (public good, decentralized social media, dao tool, or any other type of project) on Polygon PoS or Polygon zkEVM with an app-like UX by sponsoring your users’ gas fees with a paymaster and / or bundling multiple transactions, for example approve and transfer, into a single transaction.
In your project’s README, explain the UX optimization strategies you chose and why. Link to relevant sections of code with your account abstraction implementation (paymaster or bundler).
Learn more about AA by reading up on ERC-4337: Account Abstraction and gasless transactions.
Account Abstraction SDKs:
- Alchemy’s Account Abstraction SDK supports Polygon PoS Mainnet, Polygon PoS Mumbai Testnet, Polygon zkEVM Mainnet, and Polygon zkEVM Testnet
- Biconomy’s Gasless Transactions SDKs support Polygon PoS Mumbai Testnet and Polygon zkEVM Testnet
Trust Wallet [$10,000]
- now as you are more familiar with wizard-sdk and the EIP-712 visualization concept, propose the best way to solve this widespread issue (it can be one of the 2 already existing ones, the SDK or on-chain visualization EIP, just make sure to defend your idea)
- add more debug node providers factories, at least Alchemy and Tenderly
- extract slippage AMM calls (uniswap, 1inch,..etc), calculate the min amount and add it to amounts array, note that you can’t rely on the calldata only as someone can use a bundler to bundle multiple transaction (use the simulation internal calls to identify the AMM call, decode it and extract the slippage/minOut)
- Currently, slippage is a significant issue in decentralized finance (DeFi) because each protocol uses a different data format. It is challenging and not scalable to add custom implementations for each protocol, decode the data, and extract the slippage value.
To address this problem, a scalable solution is needed that would allow wallets to protect users from miner-extractable value (MEV) attacks targeting transactions with unset slippage (or set to 100%). One potential solution is to create an Ethereum Improvement Proposal (EIP) that standardizes the way slippage is encoded and decoded across all DeFi protocols. This would enable wallets to easily extract the slippage value from any transaction data and alert users if the slippage is unset or set to 100%, providing an additional layer of protection against MEV attacks. Alternative implementations that achieve the same goal are also worth considering.
Total bounty size : 10K
Build the Best Use Case for Circle’s Programmable Wallets
About Programmable Wallets
Programmable Wallets enable developers to create and embed secure Web3 wallets at scale in minutes. With these APIs, you can specify parameters to generate purpose-built wallets tailored to the use case you're building for. To learn about the product and flexible infrastructure models, please visit our documentation here.
What we are looking for:
We are interested in applications that use the Programmable Wallets API to build any of the following:
- Solutions that leverage programmable wallets to address existing gaps in the payments, asset management, identity & ownership, and financial ecosystem.
- Applications with seamless UX that abstracts away the complexities associated with Web3 interactions, ensuring user-friendly interfaces and experience.
- Solutions that prioritize user’s security and privacy, and have the potential to scale efficiently, addressing the diverse needs of a growing user base.
- Solutions that showcase sustainable business and potentially demonstrate how they would function in real-world scenarios.
Please make sure to include the below within your submission
1. Functional MVP - The submission is a fully functional Minimum Viable Product (MVP) that covers any of the criteria listed above.
- Video demo
- Testable code
- Deployed URL or Mobile application
Refrain from submitting only pitch decks, marketing demos, product documents without functional and testable code and demo.
2. Development Process - The submission includes a clear and comprehensive documentation of the development process, including gists, sketches, discussions, and any issues encountered. Ensure that the commit history demonstrates a steady and iterative development approach, not just one large pull request.
3. Integration Challenges/Feedback: The submission meticulously details any integration challenges with the provided API and documentation, and the adept use of GitHub Issues to extensively document problems and their resolutions. We look forward to seeing documented feedback around how the solution and the corresponding resources can be improved and what you’d like to see to better improve the building of your use case.
4. Presentation and Documentation: The submission’s presentation and video clearly details its features and the integration of the programmable wallets API, while its well-structured documentation, including code comments, simplifies understanding and further development.
Helpful resources as you start to build
- Interactive Quickstart Guide (for developer controlled wallets) - https://learn.circle.com/quickstarts/dev-controlled-wallets
- Documentation - https://developers.circle.com/w3s/docs
- Discord Channel - https://discord.gg/XY4nxa72
Rally Protocol [$10,000] (4 winners, $2,500 each)
About Rally Protocol:
Rally Protocol is the go-to mobile web3 development solution for serious builders and crypto-curious app developers alike. As permissionless, free-to-use, open-source software, Rally Protocol has built React Native tooling that allows developers to seamlessly integrate Web 3 into mobile applications. Developers are able to maintain full control of the user experience, and develop in programming languages they already know.
What We're Looking For:
We're interested in innovative applications that utilize our SDK. Here are some ideas:
- Create a mobile application that uses the EOA on the device as a signer in a SAFE, SoulWallet, or other smart contracts.
- Develop an app that uniquely leverages mobile devices and system functionality traditionally under-explored in crypto (e.g., camera, gyroscope, biometrics, location).
- Write a GSN client that calls our API in NodeJS, Python, or Ruby.
Links and documentation:
Phala Network is a decentralized off-chain compute infrastructure. On Phala Network, developers can deploy secure off-chain programs that can interface with the Internet via HTTP request, and build cross-chain applications. Now developers have a solution that makes their Smart Contracts even Smarter 🤓. Website | X (formerly Twitter) | GitHub
🏆 Most Creative & Inspiring - 2
Showcase your creativity and leverage Phala's off-chain capabilities to supercharge your Polygon smart contracts.
🤝 Web3 Social Integrations - 3
Enhance the Web3 Social experience by building integrations with Lens Protocol, Farcaster, Telegram, etc.
🎱 Qualifying Submissions - 5
Take your idea to Phala mainnet by deploying your custom off-chain program on Phala Network and easily connect to your Polygon smart contract to create your dream cross-chain application.
Check out our latest workshop on how easy it is to build a cross-chain dApp with Phala Network and Polygon https://bit.ly/3tbhGQy
🧠 Need an Idea, Check These Out
- Web3 Social (Lens, Farcaster, etc.)
- Guild.xyz Integration
- Dynamic NFTs
- AI integrations
- Bonus Integration: SubQuery + Phat Contract Indexer integration
- Adventurous Integration: Intent Based Architecture
Requirements for Project Submissions
- Deploy an off-chain program on Phala mainnet (For any issues reach out to Joshua or log an issue here)
- Create a cross-chain dApp by connecting your Polygon Smart Contract to your Phala off-chain program.
1. Open source repo of project submission (MIT License, Unlicense, etc.)
2. Contract ID on Network of Consumer Contract
3. Oracle Attestor Address
4. Readme file with documentation of Project details, including screenshots/videos demoing the project
📖 Requirements for Blog Submissions
1. Must be published to a public blog (i.e. your site, mirror, Hashnode)
2. Should be technically focused, either a write of how you built your project or a technical guide on how to use Phala
3. Submit link to published article