Names, mail, payments and websites — natively on-chain. ORDnet builds
Web3 infrastructure on BSV around the SNS naming protocol (name.tld,
1Sat-ordinals based, ~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.
- 🌐 ordnet.io · odnca.org — standards, transparency, verification
- ⛓️ Daily state commits on-chain · snapshots at odnca.org/snapshots
- 🤝 web3-names for the BSVA browser: bsv-browser PR #114
Standards & proofs (MIT)ODNCA-standards — the 12-document library: name format (SNS-NAME-1), resolution, commitments, policies · ODNCA-verify — offline certificate/proof verifier + the reference commitment pipeline and frozen ruleset (sha256-anchored in every on-chain commit)
Resolve & integrate (MIT)ORDnet-SNS-Merkle-Resolver — run a trustless resolver: merkle proof in every answer · ORDnet-SNS-client — zero-dep client per STD-001 · ORDnet-web3names — the browser-integration module behind PR #114 · ORDnet-bsvalias-bridge — paymail wallets → SNS names, one extra line
Wallets & browser (source-available)ORDnet-Chrome-Wallet · ORDnet-Android-Wallet · ORDnet-iOS-Wallet — one byte-identical crypto engine across all three · ORDnet-Web3-Browser — the single-file browser that also lives on-chain as ordinals
Agents & payments (MIT)ORDnet-MCP-Server — 43 tools for AI agents: inscriptions, .web3 domains, BRC-100 · ORDnet-CLAWD — the agent skill (clawd.ordnet.io) · ORDnet-x402 — HTTP 402 micropayments in native sats · ORDnet-Swap — self-hostable DOGE/LTC → BSV on-ramp
Everything here is verifiable against the chain. Start at odnca.org/transparency.