World

$15,000 prize pool · Presenter · 6 prizes awarded

Best Use of World ID for Agents

$7,500

$2,500 × 3 winners

W Airlock$2,500
W Lifeline$2,500
W Surety$2,500

Prize details

![We are mocking proofs now, so you don't need sandbox app anymore]! Build an application using World ID for Agents. We are especially interested in agentic products, but any compelling use case is eligible. Show what becomes possible when an application can ask a person to authenticate or complete a fresh verification at the moment. Strong submissions will show a meaningful action that needs a human identity or approval layer, not simply a login screen added to an existing product.

Qualifications

- Integrate with the official World ID for Agents on dev environment provided for the event. - Demonstrate the complete journey: identity or verification request, user completion, validated result, and the protected application or agent action. - Demonstrate a denied, expired, cancelled, or otherwise unsuccessful path where the protected action does not occur. - Validate identity results in a secure backend; do not expose client secrets or treat an unvalidated client response as authorization. - Include a short integration debrief/feedback: time to first success, friction encountered, missing capability or documentation, and the one improvement with the greatest impact.

Best Use of IDKit

$5,000

$2,500 × 2 winners

W Placed$2,500
W Pupille$2,500

Prize details

Build a product that uses IDKit to solve a real trust moment: an event where a product needs to know something meaningful about a person before it grants access, completes an action, or changes a user’s experience. Use the credential that is proportionate to your use case—such as Proof of Human, Passport/NFC, or Selfie Check (Now live with Sybil score). We are not rewarding the most credentials used. We are rewarding the best decision about which credential is needed, why it is needed, and how it improves a real product experience. Strong examples could include fair access to a scarce benefit, a privacy-preserving eligibility check, recovery or protection of an important account action, or a workflow that becomes safer or simpler because it can verify the right level of human trust.

Qualifications

- Integrate IDKit in a functioning application, mini app, or onchain flow. - Use at least one supported World ID credential and verify the result on the server or onchain as appropriate. - Clearly explain the specific product event requiring trust and why the chosen credential is the minimum sufficient assurance. - Demonstrate a successful verification and one meaningful alternative path, such as cancellation, unavailable credential, rejection, or an ineligible user. - Include a short integration debrief/feedback: time to first success, friction encountered, missing capability or documentation, and the one improvement with the greatest impact.

[Cont] Best IDKit Use Case

$2,500Existing project

W Lortnoc Tahc$2,500

Prize details

Build a product that uses IDKit to solve a real trust moment: an event where a product needs to know something meaningful about a person before it grants access, completes an action, or changes a user’s experience. Use the credential that is proportionate to your use case—such as Proof of Human, Passport/NFC, or Selfie Check (Now live with Sybil score). We are not rewarding the most credentials used. We are rewarding the best decision about which credential is needed, why it is needed, and how it improves a real product experience. Strong examples could include fair access to a scarce benefit, a privacy-preserving eligibility check, recovery or protection of an important account action, or a workflow that becomes safer or simpler because it can verify the right level of human trust.

Qualifications

- Integrate IDKit in a functioning application, mini app, or onchain flow. - Use at least one supported World ID credential and verify the result on the server or onchain as appropriate. - Clearly explain the specific product event requiring trust and why the chosen credential is the minimum sufficient assurance. - Demonstrate a successful verification and one meaningful alternative path, such as cancellation, unavailable credential, rejection, or an ineligible user. - Include a short integration debrief/feedback: time to first success, friction encountered, missing capability or documentation, and the one improvement with the greatest impact.

E

ENS

$10,000 prize pool · Core · 6 prizes awarded

Best Use of ENSv2

$7,000

1st $3,000 · 2nd $2,000 · 3rd $1,000 · 4th $1,000

E Relay1st place · $3,000
E ENS Drive2nd place · $2,000
E Kura3rd place · $1,000
E Tide3rd place · $1,000

Prize details

ENSv2 beta is now live on Sepolia — be among the first to build on it. Explore the new hierarchical registry structure: resolve subnames straight off a parent's resolver with wildcard resolution, or deploy your own subname registry to tokenize and manage subnames under your own rules. Use Enhanced Access Control, the shared, role-based permission system behind both registries and resolvers, to delegate specific rights — like letting an account edit only certain text records on a name. Give subnames their own Permissioned Resolver so they fully own their data, mix in record aliasing at the resolver level or namespace aliasing via a shared registry, and combine it all to build subname setups — expiring, revocable, non-transferable vs. transferable, even forever names with no parent control. Bonus points if you bring AI agents into the mix — think agents as namespaces, each with their own identity and permissions.

Qualifications

Project must be built on ENSv2 (Sepolia). ENSv2 features should be central to the product, not a cosmetic add-on. Your demo must be functional and not just include hard-coded values. Upon submission, your project showcase must have a link to a live demo and the code needs to be open source and accessible on Github or a similar platform.

Best Integration of ENSv2 into an Existing Project

$3,000Existing project

1st $2,000 · 2nd $1,000

E Radius1st place · $2,000
E Lortnoc Tahc2nd place · $1,000

Prize details

ENSv2 is only live on Sepolia for now, so this track is about getting a head start: explore how ENSv2's feature set — the new registry hierarchy, Enhanced Access Control, Permissioned Resolvers, record and namespace aliasing — can plug into an existing protocol or project to improve the user experience or unlock entirely new use cases. Take a project you already know, yours or an open one, and integrate it against ENSv2 on its testnet deployment. This track pairs well with AI agent identity too — consider giving agents their own namespace and delegated permissions within your integration.

Qualifications

Integration must use ENSv2 on Sepolia and target an existing project's testnet deployment. It should be clear how ENSv2 improves the project, not just a cosmetic add-on. Your demo must be functional and not just include hard-coded values. Upon submission, your project showcase must have a link to a live demo and the code needs to be open source and accessible on Github or a similar platform.

UF

Uniswap Foundation

$10,000 prize pool · Core · 6 prizes awarded

Best Uniswap Stack Contribution

$6,000

1st $3,000 · 2nd $2,000 · 3rd $1,000

UF Kura1st place · $3,000
UF Bailiff2nd place · $2,000
UF OniBlock3rd place · $1,000

Prize details

Build on or integrate any part of the Uniswap stack, including the Uniswap API, the Uniswap AMM (v2, v3, or v4), CCA, or any other Uniswap protocol. This also includes new v4 hooks, extensions or improvements to official Uniswap repositories, and tooling or solutions built for the broader ecosystem.

Qualifications

A public GitHub repository with open-source code, a FEEDBACK.md file, and a completed submission to the Uniswap Developer Feedback Form (https://developers.uniswap.org/hackathon-feedback) that includes the link to your FEEDBACK.md file. Submissions without it will be reviewed and audited before winners are finalized. Make sure your README clearly points to the relevant contracts and lines of code so we can verify your integration.

Best Uniswap Stack Contribution

$4,000Existing project

1st $2,000 · 2nd $1,000 · 3rd $1,000

UF VexiHakari1st place · $2,000
UF XSwap2nd place · $1,000
UF Reckn3rd place · $1,000

Prize details

Build on or integrate any part of the Uniswap stack, including the Uniswap API, the Uniswap AMM (v2, v3, or v4), CCA, or any other Uniswap protocol. This also includes new v4 hooks, extensions or improvements to official Uniswap repositories, and tooling or solutions built for the broader ecosystem.

Qualifications

A public GitHub repository with open-source code, a FEEDBACK.md file, and a completed submission to the Uniswap Developer Feedback Form (https://developers.uniswap.org/hackathon-feedback) that includes the link to your FEEDBACK.md file. Submissions without it will be reviewed and audited before winners are finalized. Make sure your README clearly points to the relevant contracts and lines of code so we can verify your integration.

1

1inch

$7,000 prize pool · Presenter · 5 prizes awarded

Build an Aqua App

$5,000

1st $2,500 · 2nd $1,500 · 3rd $1,000

1 OddsFlow1st place · $2,500
1 Wamia2nd place · $1,500
1 watermark3rd place · $1,000

Prize details

Create a custom Aqua app that implements a sophisticated DeFi position. If you use SwapVM, you may modify SwapVM opcodes and define your own instructions. The final positions must be demonstrated through tests scripts or a UI. Projects that utilize SwapVM will be scored higher during the final judging.

Qualifications

- Official Aqua/SwapVM contracts must be used (redeployments of a modified SwapVM contract is allowed) - Onchain execution of token transfers should be presented during the final demo (local forks are ok) - Proper Git commit history (no single-commit entries on the final day)

Build an Aqua App - Continuity Track

$2,000Existing project

1st $1,500 · 2nd $500

1 VexiHakari1st place · $1,500
1 Takarabako2nd place · $500

Prize details

Create a custom Aqua app that implements a sophisticated DeFi position. If you use SwapVM, you may modify SwapVM opcodes and define your own instructions. The final positions must be demonstrated through tests scripts or a UI. Projects that utilize SwapVM will be scored higher during the final judging.

Qualifications

- Official Aqua/SwapVM contracts must be used (redeployments of a modified SwapVM contract is allowed) - Onchain execution of token transfers should be presented during the final demo (local forks are ok) - Proper Git commit history (no single-commit entries on the final day)

S

Sui

$5,000 prize pool · Core · 3 prizes awarded

DeFi, Payments, Agents

$5,000

1st $2,500 · 2nd $1,500 · 3rd $1,000

S UnSui1st place · $2,500
S AntiScalper Protocol2nd place · $1,500
S Lifeline3rd place · $1,000

Prize details

Build programmable payment systems and financial applications on Sui that move, manage, and transform money intelligently, creating more seamless, automated, and composable financial experiences beyond traditional DeFi.

Qualifications

**Systems that move, manage, and transform money programmatically.** This includes: - Payment flows - Wallets and financial interfaces - Vaults and capital allocators - Automation systems - Financial abstractions for real users

C

Curvegrid

$3,000 prize pool · Gold · 3 prizes awarded

Best AI Agent Project

$1,000

C Kagi Wallet$1,000

Prize details

What happens when AI agents can understand blockchain activity and take action on-chain? AI agents are emerging as a new interface for interacting with financial infrastructure. Combined with programmable digital assets, they could help users analyze portfolios, automate treasury operations, execute payments, monitor risks, interact with smart contracts, and coordinate increasingly complex workflows. 💡 Some Ideas to Explore: 💰 AI Treasury Agent — Monitor digital assets and recommend actions based on balances, liquidity needs, or predefined policies. 🪙 Stablecoin Payment Agent — Manage invoices, initiate stablecoin payments, select payment routes, or track settlement. 🔎 On-Chain Monitoring Agent — Analyze wallets, contracts, or transactions and surface unusual activity or events requiring attention. 📊 Portfolio Intelligence Agent — Let users ask natural-language questions about holdings, transactions, yield, or historical activity. 🛡️ Policy-Aware Transaction Agent — Propose or execute transactions while respecting rules such as spending limits, approved counterparties, or required human approvals. 🤝 Agent-to-Agent Payments — Explore autonomous commerce where AI agents request, execute, or reconcile on-chain payments with one another. Using our blockchain development platform MultiBaas is not a requirement to apply for this prize.

Qualifications

Judging is based on your idea and technical execution. ✅ A GitHub repository with your project artifacts (contracts, tests, documentation) and a solid README. Your README should include: 1️⃣ A one-sentence summary of your project 2️⃣ How you used MultiBaas in your project (optional) 3️⃣ A brief intro to your team and their social handles 4️⃣ Clear setup and testing instructions 5️⃣ Your experience with MultiBaas if you used it (feedback, challenges, wins)

Best Digital Asset Dashboard

$1,000

C UnSui$1,000

Prize details

More and more people are managing portfolios of tokens, whether you’re an individual with personal investments, a VC with token agreements, or a business getting paid in tokens. Are there upcoming DAO votes? Actions to take for vesting tokens? How do you visualise your holdings in order to understand their value and take actions to manage them. Build a dashboard that helps users understand their digital assets, identify actions that need to be taken, and make better operational decisions. 💡 Some Ideas to Explore: 📊 RWA Analytics – How are RWAs performing including ownership distribution, valuations, and liquidity flows 🏦 Treasury Management – How do you track the assets in your portfolio and liquidate or exchange them efficiently in different markets 📈 DeFi Analytics – Real-time DEX activity, yield curves, liquidity movements 🌉 Cross-Chain Views – Compare assets or contracts across chains with unified views Using our blockchain development platform MultiBaas is not a requirement to apply for this prize.

Qualifications

Judging is based on your idea and technical execution. ✅ A GitHub repository with your project artifacts (contracts, tests, documentation) and a solid README. Your README should include: 1️⃣ A one-sentence summary of your project 2️⃣ How you used MultiBaas in your project (optional) 3️⃣ A brief intro to your team and their social handles 4️⃣ Clear setup and testing instructions 5️⃣ Your experience with MultiBaas if you used it (feedback, challenges, wins)

Best RWA Tokenization Project

$1,000

C DayTrader$1,000

Prize details

Turn real-world assets into programmable, composable digital primitives. Tokenized RWAs are rapidly becoming one of the most impactful Web3 use cases: from on-chain treasuries and money markets to supply-chain assets, invoices, or even real estate shares. This prize challenges builders to bring real-world asset value on-chain. Beyond simply tokenizing an asset, think about what becomes possible once ownership, transactions, permissions, and financial workflows are programmable. 💡 Some Ideas to Explore: 🏦 On-chain Treasuries – Tokenize treasury bills, money-market instruments, or other financial assets with transparent yield and transaction reporting 📄 Invoice Financing – Build tokenized invoice marketplaces with automated settlement, cashflow tracking, or other mechanisms 🏠 Real Estate Shares – Explore fractional ownership, secondary trading, or compliance-aware transfer logic 📦 Supply Chain Assets – Track movement, custody, provenance, and settlement by representing commercial goods on-chain 🪙 Stablecoins – Create an interface for minting and managing stablecoins, including compliance aspects, yield tracking, or anything else you think useful in the stablecoin world 🔐 Programmable Asset Controls — Experiment with permissions, transaction limits, allowlists, approval workflows, or other controls around how tokenized assets can be held and transferred Using our blockchain development platform MultiBaas is not a requirement to apply for this prize.

Qualifications

Judging is based on your idea and technical execution. ✅ A GitHub repository with your project artifacts (contracts, tests, documentation) and a solid README. Your README should include: 1️⃣ A one-sentence summary of your project 2️⃣ How you used MultiBaas in your project (optional) 3️⃣ A brief intro to your team and their social handles 4️⃣ Clear setup and testing instructions 5️⃣ Your experience with MultiBaas if you used it (feedback, challenges, wins)

I

Intercepta

$2,500 prize pool · Ruby · 3 prizes awarded

Safe Agent-to-Agent Payments with x402

$2,000

1st $1,250 · 2nd $750

I Kagi Wallet1st place · $1,250
I x402 Guard2nd place · $750

Prize details

Agents are starting to pay each other: for an API call, a dataset, compute or another agent's work, often over x402. Most of those payments get signed with no one checking who is on the other side. Build the check that makes agent-to-agent payments safe. Use the Intercepta API inside an agent payment flow, so every payment is screened **before** the agent signs it or the service accepts it. Show the verdict in the flow and let it decide what happens next: pay, refuse, cap the amount or ask a human. Where we'll lean in, and help most at the booth: - **The paying agent.** Before it signs an x402 payment, screen the destination address (payTo), the token (real USDC or a lookalike) and the payment authorization itself. Enforce spending limits and stop what fails, inside the agent loop. - **The paid agent or service.** An x402 endpoint or facilitator that screens the payer's wallet for sanctions, stolen funds and scam exposure before it accepts or settles. - **Counterparty risk for agents.** A risk profile with reasons for every agent or wallet on the other side, so agents can decide who to pay, who to serve and how far to trust them. x402 is our focus, and other agent payment protocols count too. We judge the moment of decision, not the size of the project: how clearly the risk shows up, how naturally it fits the payment flow, and whether an agent's owner would trust it with real money.

Qualifications

- A working agent payment flow, x402 preferred. Payments can run on a testnet. - At least one live call to the Intercepta API (free key at [intercepta.io/ethglobal](https://intercepta.io/ethglobal)) runs before a payment is signed or accepted, and its result decides what happens next. Mocked or hard-coded responses don't qualify. - Our risk data covers mainnet, so screen real mainnet addresses even when the payment runs on a testnet. Test addresses with known risks are pinned in our Discord channel. - Your demo shows one payment that goes through and one that is blocked or held, with the reason visible. - Public GitHub repo. The README points to the files where the API is called and includes 3 to 5 lines of feedback on the API: time to first call, what confused you, what was missing.

Add Payment Screening to Your Agent or x402 Service

$500Existing project

I XSwap$500

Prize details

Already run an agent, an agent framework, an x402-enabled API or a payment service? Ship one feature this weekend: an Intercepta check at the moment money moves between agents. Add screening to the product you maintain. Check the destination address and the payment authorization before your agent pays, or check the payer before your x402 endpoint accepts funds. Show the result in the real flow and ship the new code as open source. We judge how naturally the check fits the existing product and whether its users would trust it with real money. A product with real users is a plus.

Qualifications

- The feature is added to an existing product or repo on the Continuity track, and the new code is open source. - At least one live Intercepta API call runs before a payment is signed, sent or accepted, and its result is visible in the product's real flow. - Your demo shows the flow before and after the check, including one blocked or held payment. - The README points to the files where the API is called and includes 3 to 5 lines of feedback on the API.