Run the rules yourself.

Validity under a TLD begins at its published activation height: claims inscribed before activation are void, so nobody can squat a TLD before it exists. Each activation is inscribed as a signed record — the TLD’s birth certificate — giving every TLD a registry-id of the form bsv:sns:<activation-txid>.

Namespaces are identified by the hash of their frozen ruleset: a registry is its rules, so its rules are its fingerprint — already embedded in every on-chain commitment.

Launch scope: BSV / SNS. The format is chain-agnostic by design; a new namespace joins with deterministic rules published as a frozen, hashed ruleset, a conformance vector set, an operating indexer, and a commitment path. Where the same label exists elsewhere, the recognised entry is canonical for the coordinated ecosystem.

Read STD-004 →

The indexer’s canonical state is periodically frozen as a merkle tree; the root is inscribed on-chain as a commit record carrying the state height, name count, the ruleset hash, and a prev link — commitments chain into an auditable history.

Every holder can obtain a Certificate of Ownership — leaf, merkle path, chain anchor — verifiable offline with the published reference verifier, and mintable on-chain (sns-cert) as a permanent, self-contained attestation.

Web2 registries deposit their data with escrow agents. Here the chain is the deposit, the commitment chain is the receipt, and the certificate is the holder’s own copy. The failure of any operator — including the founding one — loses convenience, never names.

Run the vectors, publish a key

Implement ODNCA-STD-001, reproduce the signature test vector bit-for-bit, publish your signing key with the rotation procedure, and apply your own POL-003 measures under your own law — a second independent operator is this ecosystem’s safety valve, and a standing goal.