NamID Protocol
Roadmap · revised 22 September 2026

From one testnet outlet to a naming layer the whole Chia ecosystem resolves.

The protocol is built and running on testnet11. What follows is the order in which the surfaces around it go live, what each one needs, and where funding changes the pace. Dates are targets, not promises; the gap ledger says what is still unproven.

Phase 0 done · 2026 Q3

Protocol on testnet11 shipped

  • Soulbound roots (TLDs) auctioned under a threshold-signed DAO; 10,000 popular-site gifts and 99 ecosystem gifts reserved; 38,953 OFAC labels refused at the registry.
  • SageX wallet — desktop, CLI and browser extension — resolves names against Chia consensus, not a web server.
  • Three outlets, one bundle: namid.net (home + client default), testnet.namidbase.com (application), names.cat (marketplace). Deployments are generated from the reference installer and gated so they cannot drift.
Phase 1 now · 2026 Q4

Mainnet launch of the domains in progress

  • namidbase.com opens at the apex — the launch is a switch on namid.net's /api/ upstream, not a wallet release.
  • names.cat mainnet marketplace: SLD offer files, mirrored to Dexie and OfferFiles, never custodial.
  • Mail and Calls on your name (the mailbox and the line your key claimed) leave testnet with it.
  • Security review of the covenants and the auction escrow — the largest single item on the gap ledger and the first use of funds.
Phase 2 2027 H1

Ecosystem integrations next

A name is worth what resolves it. Each integration below is a place a NamID name shows, sells, or signs — in the order their APIs make possible.

DexieOfferFiles.comMintGardenXCHandleschianfts.comSpacescanXCHscanSage wallet (upstream)GobyPermutoSplitXCHHashtunesGo4.meMarvelous Marmots
  • Marketplaces (MintGarden, chianfts.com, Dexie, OfferFiles): list and take name offers with the name shown as a name, not a launcher id.
  • Explorers (Spacescan, XCHscan): resolve alice.nm beside the address; show NamID records on the coin page.
  • Wallets (Sage, Goby): send-to-name and sign-in-with-name via the resolver library SageX already ships.
  • XCHandles: bidirectional resolution so a handle and a NamID name can point at each other.
Phase 3 2027 H2

Browser-native resolution planned

  • TLDs and SLDs resolving in the browser bar through the SageX extension and a native host, with certificates issued against the name's on-chain record.
  • Public resolver operators with a light-client proof per answer; a hosted API for apps that cannot run one.
  • DAO handover: the treasury's reserve classes and the gift program governed by the member set, not the founder.
What it takes

Funding changes the pace, not the plan

Every phase above is sequenced so it can be built by a small team. Funding buys the security review, the integration engineers and the operator budget that turn 2027 into 2026 Q4.

1

Security review

Independent audit of covenants, escrow and the DAO signer before value is held at the apex.

2

Integrations

One engineer per marketplace/explorer pairing for the Phase 2 list, plus the resolver SDK docs they need.

3

Operations

Resolver operators, mainnet infrastructure and the compliance screen kept current.

Read the investor pitch   Donate to the protocol