Open Agents
Online · Apr 24 – May 6, 2026
468 projects32 winning projects$35,000 in prizes6 sponsors
0G
$15,000 prize pool · Core · 10 prizes awardedBest Agent Framework, Tooling & Core Extensions
$7,5001st $2,500 · 2nd $2,000 · 3rd $1,500 · 4th $1,000 · 5th $500
- 0ACL1st place · $2,500
- 0Mendel2nd place · $2,000
- 0Immunity3rd place · $1,500
- 0cortex4th place · $1,000
- 0FFE5th place · $500
Prize details
This track is strictly for framework-level work. Build the best core extensions, improvements, forks, or entirely new open agent frameworks inspired by OpenClaw (or alternatives like ZeroClaw, NullClaw, etc.) and deployed on 0G. Focus on advancing how agents are created in 2026 - architectures, developer tooling, and infrastructure primitives that other builders will use. Ideas to get you started: 🔹 New OpenClaw modules for hierarchical planning, reflection loops, or multi-modal reasoning that natively integrate 0G Compute’s sealed inference (live models like qwen3.6-plus or GLM-5-FP8) 🔹 Self-evolving agent framework that autonomously generates/tests/integrates new skills/tools using persistent 0G Storage memory 🔹 Modular “agent brain” library with easy swapping of memory layers (0G Storage KV/Log), LLM backends, or decision engines 🔹 No-code/low-code visual agent builder with one-click deployment to 0G Compute + Storage
Qualifications
Submission requirements: 🔹 Project name and a short description 🔹 Contract deployment addresses 🔹 Public GitHub repo (README + setup instructions) 🔹 Demo video & live demo link (keep the video under 3 mins!) 🔹 Explain which protocol features or SDKs you used 🔹 Team member names and contact info (Telegram & X) You must also include: 🔹 At least one working example agent built using your framework/tooling (include the example code or link in the README) 🔹 Architecture diagram (optional but strongly recommended) showing integration with OpenClaw + 0G Storage/Compute
Best Autonomous Agents, Swarms & iNFT Innovations
$7,500$1,500 × 5 winners
- 0AgentMeshx$1,500
- 0Brainpedia$1,500
- 0CodeGuardian iNFT$1,500
- 0Federated Reserve$1,500
- 0Mnemo Agents$1,500
Prize details
This track is strictly for building the actual agents. Create the most capable autonomous single agents, powerful multi-agent swarms/collectives, or any highly creative open agent project deployed on 0G. This track celebrates long-running goal-driven agents, emergent collaboration, and novel uses of iNFTs (ERC-7857) for ownership, composability, and monetization on 0G. Ideas to get you started: 🔹 Personal “Digital Twin” agent that learns from user behavior and maintains evolving persistent memory via 0G Storage (KV for real-time state + Log for conversation/history) 🔹 Advanced research/knowledge or creative agent with persistent context on 0G Storage + self-fact-checking/reflection using verifiable 0G Compute inference 🔹 Specialist agent swarms (planner + researcher + critic + executor) that collaborate in real time via shared 0G Storage memory and coordinate inference on 0G Compute 🔹 iNFT-minted agents with embedded intelligence (encrypted on 0G Storage), persistent memory, dynamic upgrades, and automatic royalty splits on usage 🔹 Agent breeding/merging via iNFTs, emergent behavior experiments, agent arenas, or completely new paradigms leveraging 0G’s full stack
Qualifications
Submission requirements: 🔹 Project name and a short description 🔹 Contract deployment addresses 🔹 Public GitHub repo (README + setup instructions) 🔹 Demo video & live demo link (keep the video under 3 mins!) 🔹 Explain which protocol features or SDKs you used 🔹 Team member names and contact info (Telegram & X) You must also include: 🔹 For swarms: clear explanation of how agents communicate and coordinate 🔹 For iNFT projects: link to the minted iNFT on 0G explorer + proof that the intelligence/memory is embedded
ENS
$5,000 prize pool · Core · 6 prizes awardedBest ENS Integration for AI Agents
$2,5001st $1,250 · 2nd $750 · 3rd $500
Prize details
AI agents need persistent, human-readable identities too. Build a functional project where ENS is the identity mechanism for one or more AI agents. ENS should be doing real work — resolving the agent's address, storing its metadata, gating access, enabling discovery, or coordinating agent-to-agent interaction.
Qualifications
It should be obvious how ENS improves your agent's identity or discoverability — not just a cosmetic add-on. Demo must be functional (no hard-coded values). Submit with a video or live demo link.
Most Creative Use of ENS
$2,5001st $1,250 · 2nd $750 · 3rd $500
Prize details
Most people know ENS for name → address lookups. We want to see what else it can do. Store verifiable credentials or zk proofs in text records. Build privacy features with auto-rotating addresses on each resolution. Use subnames as access tokens. Surprise us!
Qualifications
ENS should clearly improve the product. Demo must be functional (no hard-coded values). Submit with a video or live demo link.
KeeperHub
$5,000 prize pool · Participant · 5 prizes awardedBest Use of KeeperHub
$4,5001st $2,500 · 2nd $1,500 · 3rd $500
- KTradewise Agentlab1st place · $2,500
- KKeeper-Gate2nd place · $1,500
- KZW.ARM3rd place · $500
Prize details
𝗧𝘄𝗼 𝗳𝗼𝗰𝘂𝘀 𝗮𝗿𝗲𝗮𝘀, 𝗼𝗻𝗲 𝗿𝗮𝗻𝗸𝗲𝗱 𝗽𝗿𝗶𝘇𝗲 𝗽𝗼𝗼𝗹. 𝗕𝗲𝘀𝘁 𝘄𝗼𝗿𝗸 𝘄𝗶𝗻𝘀 𝗿𝗲𝗴𝗮𝗿𝗱𝗹𝗲𝘀𝘀 𝗼𝗳 𝘄𝗵𝗶𝗰𝗵 𝗮𝗿𝗲𝗮 𝘆𝗼𝘂 𝗯𝘂𝗶𝗹𝗱 𝗶𝗻. 🟢 𝗙𝗼𝗰𝘂𝘀 𝗔𝗿𝗲𝗮 𝟭: 𝗕𝗲𝘀𝘁 𝗜𝗻𝗻𝗼𝘃𝗮𝘁𝗶𝘃𝗲 𝗨𝘀𝗲 𝗼𝗳 𝗞𝗲𝗲𝗽𝗲𝗿𝗛𝘂𝗯. Show us something we haven't seen before. Use KeeperHub's execution layer in a way that solves a real problem, whether that's an • agent, • a workflow, • a dApp, • a dev tool, • or something entirely new. 𝗪𝗵𝗮𝘁 𝗰𝗼𝘂𝗻𝘁𝘀: any project that uses KeeperHub (MCP server or CLI) in a meaningful way. No format restrictions. If it works and solves a real problem, it qualifies. 🟢 𝗙𝗼𝗰𝘂𝘀 𝗔𝗿𝗲𝗮 𝟮: 𝗕𝗲𝘀𝘁 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝗞𝗲𝗲𝗽𝗲𝗿𝗛𝘂𝗯. Connect KeeperHub to something. Build the bridge so other developers don't have to. Two potential angles: • 𝗣𝗮𝘆𝗺𝗲𝗻𝘁𝘀. Integrate KeeperHub with payment rails like x402 or MPP. Show how agents can pay for services, settle transactions, or route payment flows into KeeperHub execution. • 𝗔𝗴𝗲𝗻𝘁 frameworks and tools. Build a plugin, connector, or SDK integration for ElizaOS, OpenClaw, LangChain, CrewAI, or any framework with an active builder community. 🟢 𝗝𝘂𝗱𝗴𝗶𝗻𝗴 𝗰𝗿𝗶𝘁𝗲𝗿𝗶𝗮: • Does it work? • Would someone actually use it? Real utility over novelty. • Depth of KeeperHub integration • Mergeable quality: clean code, clear documentation, working examples
Qualifications
𝗘𝗮𝗰𝗵 𝘀𝘂𝗯𝗺𝗶𝘀𝘀𝗶𝗼𝗻 𝗺𝘂𝘀𝘁 𝗶𝗻𝗰𝗹𝘂𝗱𝗲: • A working demo, live or recorded • A public GitHub repository with a README covering setup and architecture • A brief write-up explaining the approach and how KeeperHub is used • Project name, team members, and contact info
Builder Feedback Bounty
$500$250 × 2 winners
- KComputePool$250
- KEvoYield$250
Prize details
🟢 A separate bounty for builders who give us honest, actionable feedback while integrating KeeperHub during the hackathon. Open to any team that uses KeeperHub, whether or not they place in the main prize pool. We want feedback that helps us make KeeperHub better. • UX and UI friction, • reproducible bugs, • documentation gaps that slowed you down, • feature requests that would have made your build easier. This isn't a consolation prize. Honest feedback from builders working under time pressure is some of the most valuable product input we get. 𝗧𝘄𝗼 𝘄𝗶𝗻𝗻𝗲𝗿𝘀, $𝟮𝟱𝟬 𝗲𝗮𝗰𝗵.
Qualifications
𝗦𝘂𝗯𝗺𝗶𝘀𝘀𝗶𝗼𝗻𝘀 𝗺𝘂𝘀𝘁 𝗰𝗼𝘃𝗲𝗿 𝗮𝘁 𝗹𝗲𝗮𝘀𝘁 𝗼𝗻𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗳𝗼𝗹𝗹𝗼𝘄𝗶𝗻𝗴: • UX or UI friction: what was confusing, slow, or unclear when using KeeperHub • Reproducible bugs: issues with clear steps to replicate • Documentation gaps: where the docs left you stuck • Feature requests: what's missing that would have made the build easier Feedback must be specific and actionable. Generic praise or vague criticism will not qualify.
Gensyn
$5,000 prize pool · Participant · 3 prizes awardedBest Application of Agent eXchange Layer (AXL)
$5,0001st $2,500 · 2nd $1,500 · 3rd $1,000
Prize details
One prize pool, ranked. Best work wins regardless of what you build. Build something on AXL, our peer-to-peer network node that gives your applications encrypted, decentralised communication with zero infrastructure. Your app talks to localhost, AXL handles encryption, routing, and peer discovery across the mesh. Any language that can make HTTP requests can use it. We don't want to be prescriptive. If it works and it uses AXL in a meaningful way, it qualifies. Please review the suggestions below on things you can build, and use your imagination: - Agent Town: Build a multi-agent simulation where agents have distinct personalities, communicate freely over AXL, and interact in ways you can watch unfold. A generative-agents sandbox, a hackathon simulator, an agentic website with zero humans. Give agents personalities, let them loose, see what happens. - Decentralised Agent Messaging: Build a messaging or discovery platform where AI agents find each other, form groups, and communicate peer-to-peer. Think Telegram, except every user is an AI agent. Agent social networks, agent marketplaces, self-organising working groups. Or something else entirely! All winners are fast-tracked into the Gensyn Foundation grant programme. Judging Criteria: We want participants to create something on top of AXL with real utility, not just novelty. We will consider: - Depth of AXL integration - Quality of code - Clear documentation - Working examples
Qualifications
- Must use AXL for inter-agent or inter-node communication (no centralised message broker replacing what AXL provides). - Must demonstrate communication across separate AXL nodes, not just in-process. Project must be built during the hackathon.
Uniswap Foundation
$5,000 prize pool · Core · 3 prizes awardedBest Uniswap API integration
$5,0001st $2,500 · 2nd $1,500 · 3rd $1,000
Prize details
Build the future of agentic finance with Uniswap. Integrate the Uniswap API to give your agent the ability to swap and settle value onchain with transparency, composability, and real execution. Agents that trade, coordinate with other agents, or invent primitives we haven't imagined yet - we want to see it.
Qualifications
Every submission must include: A FEEDBACK.md file in the repo root, required for prize eligibility. Tell us everything about your builder experience with the Uniswap API and Developer Platform: what worked, what didn't, bugs you hit, docs gaps, DX friction, missing endpoints, and what you wish existed.
