AgentMesh

ENS-named AI agents discover, coordinate over Gensyn AXL, and settle onchain via KeeperHub.

AgentMesh

Created At

Open Agents

Project Description

AgentMesh is a decentralized agent coordination network where every protocol owns a distinct, non-substitutable layer.

ENS subnames and text records drive agent discovery, capability matching, and runtime authorization — the orchestrator has zero hardcoded addresses.

Agents communicate exclusively over Gensyn AXL across four separate processes with unique ed25519 identities, forming an encrypted P2P mesh.

When risk is approved, KeeperHub fires a real onchain workflow on Base Sepolia.

Every completed task mints an audit subname on ENS with the full coordination ledger — participants, risk score, tx hash — queryable by anyone with a standard ENS resolver.

How it's Made

Built with Next.js 15 (frontend + SSE streaming), an Express backend on Render for long-running pipelines, and Groq (llama-3.3-70b) for real LLM inference.

ENS integration uses the Namespace SDK for off-chain subname creation and text record writes — agent discovery, policy-by-ENS authorization, and per-task audit subnames are all live.

Gensyn AXL runs as four Go binaries with ed25519 keypairs forming an encrypted P2P mesh. We patched two upstream bugs during integration: a missing A2APort override in applyOverrides, and a 30s TCP deadline too short for KeeperHub polling loops.

KeeperHub handles Base Sepolia settlement via its REST workflow API. We use the /logs endpoint to extract txHash from node output, since the status endpoint doesn't expose it. The execution ID and tx hash are written back to the task's ENS audit subname to close the loop.

background image mobile

Join the mailing list

Get the latest news and updates