Roadmap

Where .agt stands today and where it's headed, from the live registry through resolution surfaces and the agent layer.

For the live, queryable roadmap, see GitHub Issues (the Registry v2 work is tracked under epic #140). The phases below are a high-level orientation, not an authoritative list.

Live

  • AGT Registry on Polygon mainnet — self-sovereign registry, ENS-compatible resolver, sales controller, and migration contract, with admin behind a timelock and multisig.
  • Migration open — existing holders migrate to free, perpetual names via same-chain, proof, or zone-owner challenge.
  • Signed v3 manifests — wallet-signed JSON, pointer on chain, verified against the on-chain owner.
  • On-chain identity badge and public name pages at /name/<label>.
  • Agent directory backed by an on-chain indexer.
  • @agtnames/resolver and @agtnames/mcp on npm — resolve mainnet names with no configuration; the MCP server works in any MCP-compatible client, with a Claude Code plugin in ds1/agt-plugins.
  • Documentation — Quick start, guides, examples and reference for every surface.

Now

  • Announcing the migration window to existing holders.
  • Durable IPFS pinning for published manifests.
  • Crypto and card sales of new names (behind the launch gate).

Resolution surfaces

  • Own authoritative Handshake nameservers for .agt, with the zone projected from registry state and DNSSEC-signed.
  • DNS-over-HTTPS resolution for HNS-aware clients.
  • A MetaMask Snap for in-wallet resolution.

Agent layer

  • ERC-8004 adapter (serve a manifest as an 8004 registration document).
  • Write tools for the MCP server and plugin (register, renew, publish a manifest) behind explicit wallet confirmation — the read side is live.
  • Delegation (an agent acting for a principal) and x402 payments.

Network effects

  • Agent-to-agent discovery protocol.
  • Trust and reputation layer (on-chain attestations).
  • Open standard publication.
  • Multi-platform clients (VS Code, Slack, and more).