ODNCA is an initiative of ORDnet.ioinfo@odnca.org
ODNCA
DECISIONS · PARAMETERS · ROADMAP

A decision that is not published is not a decision.

This page is the changelog of the authority itself: what was decided, when, and why — plus the live parameters and the honest state of the roadmap.

Live parameters

ODNCA-STD-002 — the living document. Resolvers load these lists live from the registry; this table is the human view of the same single source.

PARAMETERVALUE
Registrable TLDsweb3 · bitcoin · crypto · blockchain · ordnet
Retired TLDs (resolve-only)bsv · bitcoinsv
Withheld TLDs1sat — standing activation right with the 1Sat Ordinals ecosystem
Resolver answer TTL300 s
Dispute cure period7 days (POL-003 §4.2)
Flag thresholdpublished parameter — automatic WARNING + review queue, never automatic BLOCK
Resolver public keysns.ordnet.io/pubkey — pin on first use; rotations signed by the predecessor key

Recompute us — the toolkit

Everything needed to check ODNCA’s claims without trusting ODNCA, in one place.

RULESET-SNS-COMMIT-1.mdThe frozen ruleset behind every commit. Its SHA-256 — e2e14400…d7c922 — is bound into each on-chain commit inscription: a root claims exactly these rules, or it is a different namespace.
verify-cert.jsThe offline reference verifier: feed it a certificate’s proof JSON and the published key, and it checks the merkle path and API signature on a machine with no ODNCA access at all.
GET /commit-keyThe API signing pubkey every proof answer is signed with — pin on first use.
Commitment wallet1NETBhQt9NanKPdjAkVDDtyNgBxr5MiixX — the published on-chain identity that posts every sns-commit inscription; rotations only ever via a signed handover.
Daily state snapshotThe full committed state, published daily right after each sns-commit (gzip, ±33 MB), with metadata: height and SHA-256 of both forms. Recompute the root from it yourself — or feed it to the open-source resolver, which refuses to serve unless its recomputed root matches the on-chain commit.
Verify it yourselfThe short guide: four verification levels, from reading a certificate to recomputing the root from the chain.

Decision log · 2026

DATEDECISION
SEP 2026ODNCA-STD-010 adopted — ORD-META-1: On-Chain Content Discovery — the first adoption through the full GOV-001 §5 cycle: proposed 30 August, 14-day public review closed 13 September without blocking input, adopted 14 September 2026.
AUG 2026Adoption of the complete document corpus — eight standards (STD-001…008), three policies (POL-001…003), the governance charter (GOV-001), and the trust framework (TF-001), all v1.0. The Foundation Document published as the official summary.
AUG 2026ODNCA-STD-009 adopted — Paymail Compatibility Profile — web3 names served in byte-compatible bsvalias form; the profile endpoint is live and the one-line wallet integration published.
AUG 2026The genesis commit inscribed on-chain — sns-commit at block 961546, 651,482 names, prev: null, txid b65b03f0…e60c6ec9 — the first link of the auditable commitment chain (/commits).
AUG 2026Root Registry model adopted — TLD activation heights as normative parameters; activation records anchored on-chain; retro-activation records for the seven existing TLDs scheduled.
AUG 2026State commitments operational — prev-linked sns-commit chain with ruleset-hash binding; Certificates of Ownership with offline reference verifier; mintable sns-cert.
2026TLD retirement: .bsv / .bitcoinsv — registration closed out of respect for the BSV Association’s registration of these names; existing names resolve forever.
2026TLD withheld: .1sat — held for the 1Sat Ordinals ecosystem; activates only by or with its steward’s consent.

The roadmap, honestly

Done is marked done; open is marked open. Neutrality is earned, not claimed.

STATUSITEM
✓ DONEThe complete standards, policies, governance, and trust corpus — adopted and published
✓ DONESigned resolution live · conformance vectors frozen · state commitments and certificates operational
○ OPENOpen-sourcing the reference resolver and indexer
○ OPENAn independent second resolver operator — the standing invitation of the operator page
○ OPENPer-TLD activation enforcement in the indexer — lands with the first new TLD activation (STD-004 annex)
○ OPENRDAP endpoint serving the STD-008 mapping · OpNS canonical state and its commitment chain
○ OPENRetro-activation records inscribed for the seven existing TLDs