NamID Protocolyourname.x in its own coin, with a did:namid identifier. Names on .x, .nm, .ids and .mojo are permanent and soulbound: no renewal, no lapse.
Naming and identity on Chia · Web3UTXO LLC
Your name is a coin. Every answer is a proof.
Domain names made Web2 usable. NamID names do the same for Web3. A name such as yourname.x is a coin on Chia that only its owner's key controls. It carries the owner's payment address and records, and anyone can check them against the chain instead of taking them from us.
- Chia testnet11
- Not audited
- Specification v1.5.1 draft · 20 Oct 2026
- No protocol token
Documentation onlyThis site asks for no keys, signatures or payments
Chia coin-set modelEvery name is its own singleton coin
Chain-only resolutionAny Chia node answers; no trusted server
Testnet firstNo mainnet before an independent audit
Start here
The whole site, in six steps.
Each step is a short section on this page and a set of links to the full text. An AI agent can read the same map as plain text in llms.txt.
What NamID is
One name you own for life: get paid, sign in, publish records, take mail and calls.
How it works
A coin per name, an on-chain list per TLD, a client that checks both.
Live products
Two applications and the doors around them, each with its status today.
Documentation
The specification, the evidence, and the reservation policy.
For developers and AI agents
Resolve a name, read its records and agent card, ask a person to approve a name.
Company and contact
Web3UTXO LLC, New Mexico. One address for everything.
1 · What NamID is
Owned by you. Provable without us.
On the web you know, an operator keeps your account and can revoke it. A NamID name is a coin that only its owner key can spend, and everything below is bound to that coin, so anyone can check it against the chain without trusting a server, ours included.
Wallets pay the name, not a 62-character address, and say before you approve whose wallet the payment reaches.
Mail to a name is sealed to the key the name publishes, so only its owner can read it.
Voice, video and chat addressed to a name. Both ends prove their names before the call connects.
Software under its own name, with an agent card anyone can check and a spending limit the chain enforces.
2 · How it works
Four layers, each checkable on chain.
A name's coin carries its owner key and the hash of its records. The TLD's on-chain registrar proves the name is unique under that TLD. A client that talks only to a Chia node joins the two and returns either a verifiable answer or a refusal. The whitepaper specifies each layer; the technical overview says what is live.
- Singleton name coin
- One name, one coin, one lineage. The unspent tip says who controls the name. §3
- On-chain registrar
- A sorted list of coins per TLD; an insert must prove the gap between its neighbours, so a duplicate cannot exist. §8
- DATA_ROOT
- The hash of the name's records, in its coin. Every record comes with a proof against it. §10
- Chain-only resolution
- The open client
namid-openresolves a name from any node with no NamID server. §11 - Sealed-bid TLD auctions
- Each TLD is sold once, second price, in XCH; a bid stays sealed in the bidder's wallet until reveal. Auctions
- did:namid
- Every name is a W3C decentralized identifier. The method
If we vanished, your name would keep working. Since 19 October 2026 every TLD that issues names on testnet11 keeps its list of names on chain.
nocomp1019.nm was registered and then resolved from a Chia node with every NamID host blocked. The 109,029 older .nm and .ids names are sealed in two anchor coins that no one can spend. Still on our side today: hosting record documents (checkable against DATA_ROOT) and the web front ends, both of which anyone can run.
3 · Live products · Chia testnet11
Two applications, one protocol.
Both run today on Chia testnet11. Test coins (TXCH) carry no value, and nothing runs on mainnet before an independent audit. Both install in the official, unmodified Sage wallet: Apps → Install App → namid.net or mymojos.com.
protocol and appNamIDBid for a TLD; register, resolve and manage names; pay a name; and see every NamID transaction in plain words.
testnet.namidbase.com
built on NamIDMyMojosOne app for your .mojo name: profile, tips, payments, calls, mail, communities, agents and the Market, where shops pay a flat rent and no commission.mymojos.com
| Door | Where | Status |
|---|---|---|
| NamID app in Sage, with Messenger, Browser and DataLayer | Sage → Apps → Install App → namid.net | Live; NamID app 0.2.96 |
| names.cat, the name shop | names.cat | Live on testnet. A listed name is bought in one transaction, name and price in the same block; run from a test script, not yet signed from a wallet in a browser |
| Explorer | testnet.namidbase.com/explorer | Live |
| Agent cards | namid.net/agents/ | Live; read-only in a browser |
| Calls between names | namid.net/call/ | Live |
| A website on a name | namid.net/sites/site1022.x/ | Live; every file checked against the name's coin |
| Public profile of a name | namid.net/p/<name> | Live |
| DNS resolver for browsers | https://namid.net/dns-query and the NamID root certificate | Live; a stock browser needs both to open a NamID name, and answers can be slow |
| Mango wallet, our Sage fork | namid.net/mango/ | Windows installer 0.13.4 and browser extension 0.9.4; unsigned builds |
- Not audited. Payment channels, the sealed sets, the name-sale path and the MyMojos Market escrow have had no independent review.
- namid.net holds no registry, no auction book and no keys. Its
/api/is a proxy; the service behind it makes every decision, and a client should still check the chain. - testnet.namidbase.com and namidbase.com share a name and not a network. The public mainnet app opens at namidbase.com after the audit.
- Every application Web3UTXO runs, venues included, is listed at web3utxo.com/apps/.
4 · Documentation
The specification, and the evidence.
The whitepaper is the protocol specification and nothing else; every mechanic in it cites the constant that implements it. Open policy questions are listed in it rather than decided by assumption.
Technical overviewA dated tour of the puzzles, what servers do, and known limitations.
did:namid DID methodSyntax, document, resolution and operations.
Auctions and the release scheduleHow TLDs are released and sold, sealed-bid, second price.
Validation reportDated development evidence from September, and what remains.
Learn in ELI5 styleAn illustrated beginner's guide; also a 20-page PDF.
Code and the NamID BookCode, tests, the open client and the NamID Book are private for now; ask and we will share them.
4 · Documentation · reservation map
Scarce names are held before public bidding.
The policy separates community governance, verified gifts, ecosystem infrastructure, and mandatory safety screens. A reservation prevents a public bid; it does not prove identity or promise a transfer.
DAO-held scarce roots
24 single letters (every letter but the service roots x and i), all 10 single digits, and 9 DAO words.
a-hj-wyz0-9bharathnsindindiarootstricttldusaxch
10,000 popular-site gifts
Exactly 10,000 eligible, unique popular-site gifts. ICANN labels take priority; withdrawn entries are replenished from documented Cisco Umbrella rankings.
10,000 unique labelsDNSSEC claimDAO vote
Protocol and ecosystem roots
Infrastructure roots are held by Web3UTXO LLC. 84 Chia participant names are treasury-held for possible verified good-faith gifts.
External collision and safety screens
1,438 ICANN root-zone labels are recognized, with 1,281 effectively locked; ICANN labels take priority over company, DAO and gift allocations. The pinned OFAC exact-name normalization contains 38,953 labels.
ICANN root zoneOFAC exact screenfail closedno fuzzy identity claim
Policy boundary: first-name reservations are not identity credentials, endorsements, awards, or entitlements. The treasury must verify the intended recipient before any allocation. Browse the complete operational catalog and individual root status at testnet.namidbase.com/dao.
Development evidence · Chia testnet11
What runs today, in numbers.
- 153,159 names registered on chain, each in its own coin; 152,179 with records anchored in their own coin.
- 15 sealed-bid TLD auctions settled on chain, of 31 opened.
- 524 calls between agent names; 503 completed, all with both signed receipts verified.
- A name sold on chain in one transaction: name to the buyer and price to the seller in the same block, 4,876,973 (26 Oct).
- 109,029 older
.nmand.idsnames sealed in two anchor coins that can never be spent (19 Oct); 70,044 channel payments settled through two hubs (19 Oct).
Read from the live system on 27 October 2026 at block 4,884,912 unless dated otherwise. Testnet coins have no market value. Payment channels, the sealed sets and the MyMojos Market escrow are not audited.
What is live, in detail Check it in the explorer The September validation report
5 · For developers and AI agents
An ID for software that works and pays.
An agent can resolve a name, read its records and its agent card, read a TLD owner's rules, and ask a person for a name. It never holds the key that owns a name and never pays for one itself: a person approves in their own wallet. Everything here is public JSON on testnet11.
GET https://namid.net/api/agent
the whole API, described in one JSON document
GET https://namid.net/api/names/resolve?name=agentr.x
records, terms and the coin behind them
GET https://namid.net/api/names/agent?name=agentr.x
the agent card and its hash
GET https://namid.net/api/namespace/terms?root=x
the TLD owner's rules: expiry, transferThe agent guide
How an agent resolves a name, reads its records, checks an agent card and pays a name, and which APIs are public.
- skill.md, the same as a skill file
- llms.txt and llms-full.txt, this site as plain text
- /.well-known/namid.json, every product and endpoint with its status
- Every agent card on testnet
6 · Company and contact
Web3UTXO LLC, New Mexico, USA.
Contact: info@namid.net, the one address for everything. Revenue is paid in XCH; there is no token.
Validation
See what has been checked on testnet and what remains before mainnet. Validation report
Roadmap
The 2027 H2 mainnet target, after an independent audit and launch checks. Roadmap
Support the work
The protocol treasury, mainnet XCH only. Donate · web3utxo.com