ODNCA is an initiative of ORDnet.ioinfo@odnca.org
ODNCA
ADOPTED · v1.0 · AUGUST 2026

Eight standards. One namespace.

Every standard documents deployed, running behaviour — the exact rules under which 651,483 names were indexed — and is frozen by conformance vectors. Conformance is technical and testable; no permission or committee is involved. Run the vectors, match the answers.

The standards

ODNCA-STD-001 · v1.0 · ADOPTEDSNS Resolution SpecificationClaims, sat-following transfers, the resolution algorithm, mailbox semantics, signed answers with the exact signature scheme and test vector, errors, key rotation, and the bridge annex.READ THE STANDARD →ODNCA-STD-002 · v1.0 · ADOPTEDProtocol Parameters RegistryThe living lists: registrable and retired TLD sets, flag thresholds, cure periods, published keys. Served live by the registry; changes are dated changelog entries.LIVING DOCUMENT · SEE TRANSPARENCY →ODNCA-STD-003 · v1.0 · ADOPTEDSNS-NAME-1 · Name FormatWhat a valid name is: the JSON registration form, normalization, one-dot structure, character and length rules, BSVmap, OpNS — with 19 human-readable vectors.READ THE STANDARD →ODNCA-STD-004 · v1.0 · ADOPTEDThe Root RegistryNamespaces identified by their ruleset hash, TLD activation records and the activation-height rule, collision handling, and the commitment & certificate backbone.READ THE STANDARD →ODNCA-STD-005 · v1.0 · ADOPTEDURI Schemessns: as the primary name scheme, ord:// for on-chain content in its mutable and permanent forms, and the ordns: reservation.READ THE STANDARD →ODNCA-STD-006 · v1.0 · ADOPTEDData ChannelsPayment, mail, and content as three native on-chain channels; the read surface; the custody rule; “central follows decentral”.READ THE STANDARD →ODNCA-STD-007 · v1.0 · ADOPTEDSNSP · Registration ProtocolThe assisted claim flow: availability, the claim lock, three payment shapes including same-transaction direct flow, the issuer-signed record, valid vs. verified.READ THE STANDARD →ODNCA-STD-008 · v1.0 · ADOPTEDRegistration Data (WHOIS)The public lookup: four honest statuses, the registered record, reverse lookup, and the RDAP mapping for existing tooling.READ THE STANDARD →

Conformance

What “conformant” means here — and why it needs nobody’s signature.

Two independent implementations conform when, given the same chain, they produce the same set of valid names with the same canonical keys, the same current outpoint and holder for every living name, and bit-identical sighashes for the answers they sign.

The vector sets freeze each standard: 34+ indexer vectors (validity and canonicalization), 19 human-readable name vectors, the resolver signature test vector, and the commitment layer’s golden vectors. Changing a frozen constant does not amend a standard — it demonstrably creates a different namespace.

The trust framework ties it together: five principles, three trust layers, the key inventory with one rotation procedure, escrow solved by construction, and the honest failure table — ending with the row that matters most: if ODNCA itself disappears, what is lost is a coordinator, not a registry.

ODNCA-TF-001 · Trust Framework →