Naming infrastructure on Chia

Names that carry identity, services, and trust.

NamID is an open protocol for decentralized names, identity records, certificates, and service discovery built around Chia covenants.

Read the documentation Open the testnet outlet

Documentation onlyNo wallet keys or signatures

Chia-native designCovenants define ownership rules

Testnet firstProduction claims stay separate

Open verificationSpecifications and source are public

A simple path

Learn here. Use an outlet. Verify locally.

The protocol identity, public products, and engineering laboratory have different jobs. Keeping those boundaries visible is part of the security model.

01 / LEARN

Understand NamID

Read the protocol model, chain guarantees, resolver design, and current limitations at namid.net.

Browse documentation

02 / USE

Register on NamIDBase

Move from documentation to the application outlet when you are ready to bid, register and manage names. Testnet until launch; the apex opens when it does.

Go to testnet.namidbase.com

03 / TRADE

Trade on names.cat

Transferable second-level names change hands as Chia offer files. names.cat lists them, mirrors each to Dexie and OfferFiles, and never takes custody.

Open the marketplace

Domain map

One protocol, distinct outlets.

A shared protocol does not make every deployment the same service or trust boundary. Five surfaces, five different answers to "may this write chain state?" — and one address every client is built to talk to.

PROTOCOL HOME · CLIENT DEFAULT

namid.net

Documentation, company information and contact identity — and the address every NamID client is built to talk to. These pages are static and non-custodial; /api/ is a proxy to the application outlet and stores nothing here.

You are here

PUBLIC OUTLET

namidbase.com

A user-facing place to browse, register, and manage NamID names through its own deployment.

Visit outlet

SLD MARKETPLACE

names.cat

Where transferable second-level names are bought and sold as offer files. Listings are mirrored to Dexie and OfferFiles; a name that is permanent or soulbound is never listed.

Browse the market

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.

1. NormalizeReduce a request to one canonical NamID root label.

2. ClassifyApply explicit gifts and service policy before general locks.

3. Refuse bidsReserved, screened, and ICANN-locked roots cannot enter auction.

4. Verify claimsAny future gift still needs the class-specific recipient proof and authorization.

DAO-held scarce roots

25 single letters except x, all 10 single digits, and six governance words.

a-wyz0-9admindaodidnullroottld

9,998 popular-site gifts

DAO-held gifts mapped to a pinned Cisco Umbrella DNS ranking. .google is explicitly mapped to google.com at source rank 3, inside the 10,000 total.

googlegoogle.comrank 3DNSSEC claimDAO vote

Protocol and ecosystem roots

Infrastructure roots are held by Web3UTXOS. 91 Chia participant names are treasury-held for possible verified good-faith gifts.

chiaididsmojomojosnamenamesnamidnamidbasenamidswalletwalletsxxchxchandlexchandlesbram gene justin mariano nicholas

External collision and safety screens

1,438 ICANN root-zone labels are recognized, with 1,277 effectively locked after higher-priority policy classes. 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.

Protocol layers

More than a domain lookup.

A NamID name can become an entry point for web resolution, wallet addresses, identity, certificates, and application services.

NamingHuman-readable TLD and SLD ownership anchored by Chia singleton lineage.

IdentityDID and profile records selected by namespace policy.

CertificatesAuthenticated certificate records for resolver and browser trust experiments.

Service discoveryTyped records that direct wallets and applications to the right capability.

Documentation

Start with the trust model.

The repository is the current source for detailed specifications and implementation status.

Technical overviewA dated, detailed tour of covenants, pricing, services, and known limitations. did:namid DID methodEvery name is a W3C Decentralized Identifier: syntax, document, resolution, operations. Protocol specificationThe record model, namespace rules, ownership flow, and protocol contracts. Mainnet gap ledgerWhat remains incomplete, unproven, unaudited, or intentionally disabled. Resolver trust modelHow SageX verifies Chia consensus data instead of trusting a web server. SageX walletDesktop, CLI, native browser host, and web extension implementation. Source repositoryCode, tests, deployment kits, standards, and reproducible verification gates.

Development evidence · 24 September 2026

Funded testnet experiments. Public readiness still in progress.

Real TXCH escrow deposits have been confirmed on testnet11. Winning name minting and two-bid second-price settlement have now confirmed on testnet11. General testnet bidding is enabled; independent security review and broader lifecycle testing remain.

Read the dated validation report Inspect test auctions

Build with NamID

Start with the protocol, then prove the integration on testnet.

Company and protocol contact addresses will use @namid.net after authenticated mail and monitored inboxes are configured.

Open the marketplace Use NamIDBase (testnet)