ORDnet · ODNCA

Names, mail, payments and websites — natively on-chain

Web3 infrastructure on BSV around the SNS naming protocol: name.tld domains as 1Sat ordinals, roughly 650,000 names indexed. ODNCA — the ORDnet Decentralized Names Coordination Authority — stewards the open standards and commits the full name state to the chain daily as a merkle root, so nobody has to trust an indexer.

Don't trust us — recompute us.

Building on names? Read the specification set at ODNCA-standards, then resolve with ORDnet-SNS-client or run your own ORDnet-SNS-Merkle-Resolver. Using a wallet? See wallets and browser below. Building AI agents? Start at ORDnet-MCP-Server and the ORDnet-CLAWD skill. Auditing our claims? Everything is verifiable against the chain — begin at odnca.org/transparency and ODNCA-verify.

Every layer below is not just a repository — it runs. These are the live ORDnet services:

flowchart TB
    STD["ODNCA-standards<br/>13 protocol documents"]
    CHAIN["BSV chain<br/>daily state commitments"]
    VERIFY["ODNCA-verify<br/>offline proof verification"]
    RESOLVER["SNS-Merkle-Resolver<br/>merkle proof in every answer"]
    CLIENT["SNS-client<br/>verifies per STD-001"]
    W3N["web3names<br/>integration module"]
    BRIDGE["bsvalias-bridge<br/>paymail compatibility"]
    WALLETS["Wallets and browser<br/>Chrome · iOS · Android · Web3-Browser"]
    AGENTS["AI agents<br/>MCP-Server · CLAWD"]
    PAY["Payments<br/>x402 · Swap"]

    STD --> RESOLVER
    STD --> VERIFY
    CHAIN --> VERIFY
    CHAIN --> RESOLVER
    RESOLVER --> CLIENT
    CLIENT --> W3N
    RESOLVER --> BRIDGE
    W3N --> WALLETS
    CLIENT --> AGENTS
    BRIDGE --> PAY

ODNCA-standards is the thirteen-document library that defines the protocol: the SNS resolution specification (STD-001), the name format (SNS-NAME-1), the root registry, URI schemes, data channels, the registration protocol, registration data, the paymail compatibility profile, the fair-use, registrar and dispute policies, the trust framework and the governance process. Each document is individually versioned and adopted; changes follow the review process defined in GOV-001 and, where they change recognised state, are anchored on-chain.

The namespace is not just described — it is committed. The full SNS state is periodically frozen as a merkle root and inscribed on the BSV chain, with each commit embedding the SHA-256 of its frozen ruleset. ODNCA-verify is the offline certificate and proof verifier, and contains the reference commitment pipeline and the frozen ruleset itself. Anyone can recompute the root from public chain data and compare it against the published commitment.

ORDnet-SNS-Merkle-Resolver lets anyone run a trustless resolver: every answer carries a merkle proof against the on-chain root, on zero-dependency Node. ORDnet-SNS-client is the zero-dependency client that verifies those answers per STD-001 — signature, expiry and name binding. ORDnet-web3names is the TypeScript integration module with layered trust levels, and the module behind bsv-browser PR #114. ORDnet-bsvalias-bridge connects the existing paymail ecosystem: any bsvalias wallet can pay mailbox@name.tld with one extra line of code.

ORDnet-Chrome-Wallet is the Manifest V3 browser extension (published in the Chrome Web Store as ORDnet Web3 Browser), with a 192-test suite covering its security gates. ORDnet-iOS-Wallet and ORDnet-Android-Wallet are the native mobile wallets; they share one byte-identical JavaScript crypto engine, verified by the same test vectors on both platforms. ORDnet-Web3-Browser is the single-file web3 browser — one HTML file that also lives on-chain as ordinals.

ORDnet-x402 is an HTTP 402 micropayment facilitator in native BSV satoshis, using watch-only key derivation so the facilitator never holds spending keys for incoming funds. ORDnet-Swap is a self-hostable reference implementation of a DOGE/LTC to BSV on-ramp; ORDnet deliberately operates no hosted instance.

ORDnet-MCP-Server gives AI agents 45 tools for creating permanent Web3 content: inscriptions, .web3 domains, payments and BRC-100 identity, guarded by spend-policy ceilings. ORDnet-CLAWD is the published agent skill (clawd.ordnet.io) that teaches any agent to use them.

Two early repositories — BDNS (the 2023 concept note this all grew from) and opns-ui — are archived for the record.

Every claim above is checkable against public chain data: the daily state commitments, the frozen ruleset hashes and the merkle proofs in every resolver answer. Start at odnca.org/transparency — and hold us to our own line: don't trust us, recompute us.