NamID Protocol · one page · September 2026

Names people own, on a chain that can prove it.

A naming and identity layer on Chia. Roots are soulbound coins auctioned once in XCH; the names under them are ordinary Chia coins; every name is a W3C DID (did:namid); a wallet resolves a name only with a proof it verified against consensus. No token. XCH is the only currency.

Live today

testnet11 · three outlets · a desktop wallet · three ecosystem venues already issuing and resolving names

Standard

A CHIP drafted on DID1 + NFT1, no consensus change; the did:namid method specified and headed to the W3C registry

The ask

USD 30k to test on mainnet now; a seed round to open it. Founder: MayankR, Web3UTXOs Technologies

The problem

Chia has addresses, DIDs, NFTs and offers — and no name a wallet can prove.

Addresses are unmemorable

Nobody types xch1…. Every payment starts with a copy-paste and a hope.

Handles are custodial

Every "name" on Chia so far is a web server you have to trust. If the server lies, the wallet cannot tell.

Identity has no home

did:chia is printed by wallets but is not a registered, specified DID method. Nothing lets a Chia identity be a login anywhere else.

The protocol

Roots are soulbound and sold once. Names are yours. Resolution is verify-or-refuse.

Root = one coin

A root (.xch, .mojo, .chia, .x) is a singleton whose covenant refuses transfer. Won at a sealed-bid auction in XCH under a threshold-signed DAO. Recovery by vault, never by sale.

Name = a Chia coin

Transferable names are NFT1 coins that trade as standard offer files on any marketplace. Soulbound names are bound to a DID and never renewed — a login that cannot be bought.

Every name is a DID

did:namid:alice.mojo resolves to a DID document projected from the coin and its records. Sign in with your name; the wallet that holds it signs.

Proof, not trust

The resolver answers with the coin's lineage; the wallet checks it with a light client against consensus, or refuses. A lying resolver is caught by arithmetic.

Products

One protocol, four surfaces, three venues.

namid.net

Home, documentation, the client default; proxies the API to the application outlet.

namidbase.com

Root auctions, registration, the DAO treasury, records, mail, calls.

names.cat

The marketplace for transferable names — by rule it lists nothing soulbound.

SageX wallet

Desktop, CLI and extension; verifies every answer; signs you in with your name; WalletConnect to every venue.

offerfiles.com

Issues .xch, .wallet, .wallets; names sign in; RWA platforms with Web3UTXOS as transfer agent.

chianfts.com · mymojos.com

Issue .chia and soulbound .mojo names; resolve every NamID beside NFTs and profiles.

Revenue model

Roots, names and services are sold for XCH. Every one of them is a coin spend.

Three income lines, one treasury, and a side effect Chia is paid for directly: every root, name, renewal and record update is a singleton or NFT1 spend that pays fees and consumes block space. The protocol grows demand for Chia's block space as it grows.

Root auctions (TLDs) sealed-bid, paid once, in XCH Name issuance (SLDs) registration, renewal, marketplace fee Services on top records, mail, calls, venue integrations, RWA Treasury · 100% Web3UTXOS, for ecosystem development no split, no token, no emission threshold-signed; every spend public More on-chain activity every name is a coin spend → block-space demand Ecosystem development audits, wallets, venues, integrations Value for everyone on Chia fees to farmers, names for users, rails for apps

Roots (TLDs)

Sold once, at auction, for XCH. Soulbound afterwards, so the auction is the only time a root is ever sold — scarcity by covenant, not by policy. Twenty a day on the schedule; the base price rises with the count and again before mainnet.

Names (SLDs)

Issued under each root on the issuer's terms — termed, transferable or soulbound — with renewals for termed names and a marketplace fee on names.cat trades.

Services

Records, mail, calls, DID resolution, venue integrations and the RWA transfer-agent platforms — sold to the venues and holders who use them.

Traction · testnet11

Built, deployed, gated — and already integrated.

3 + 1

outlets and a wallet live: namid.net, namidbase.com, names.cat, SageX

3

venues issuing and resolving names at their own cost: OfferFiles, chianfts, MyMojos

10,000

popular-site gift names reserved; 99 ecosystem gifts; 38,953 OFAC labels refused

1,270+

automated tests on every deploy; seven drift gates from the reference tree to the outlets

Roadmap

From a testnet you can use to a mainnet you can trust.

2026 Q3 · done

Protocol, outlets, wallet, venue issuance, did:namid, CHIP draft.

2026 Q4

Independent audit of the covenants; first real root auction on mainnet; CHIP to Review; did:namid registered with W3C.

2027 H1

Dexie, MintGarden, XCHandles and the explorers; names as login across the ecosystem; RWA platforms live with counsel sign-off.

2027 H2

Browser-native names (.x as web domains); DAO handover of the treasury.

The ask

USD 30,000 to prove it on mainnet. A seed round to open it.

Independent review of the deployed covenants, escrow and DAO signer12,000
Mainnet bring-up: treasury, signer ceremony, first real root auction and first names6,000
Integration engineering: SageX mainnet, XCHandles binding, the three venues6,000
Six months of resolver and node operations, OFAC refresh, runbooks3,000
Contingency3,000
Total, milestone-released, reported monthly in public30,000

Line-by-line against the mainnet gap ledger: MAINNET-TEST-30K.md. Seed terms are discussed directly with the founder.

Talk to the founder

MayankR · Web3UTXOs Technologies · web3utxos.com

Source, tests and the gap ledger are public — diligence starts at the repository: github.com/DIPMR/Codex-Namid-Protocol-V0

Investor page · Roadmap · did:namid · Donate