Unified, Vendor-Neutral, Unchanging, and Open BSV Blockchain Standard Wallet-to-Application Interface
The central application-to-wallet boundary. Start here for most Metanet apps.
Synced to upstream · Sep 1, 2026
Build on the standards.
See the system.
The implementation map for Metanet technologies: find the BRCs that matter, understand how they compose, and move from an open specification to interoperable software.
Implementation stack living map
187upstream proposals
12technical domains
152with specification sections
0runtime frameworks required
Choose the job, then the standards
Implementation paths
A BRC number is not an architecture. These paths show the smallest coherent standards stack for a concrete build outcome.
01Start here
Build a Metanet application
Keep keys out of app code, ask a standards-compatible wallet to act, and make permissions legible to users.
BRC-100BRC-42BRC-43BRC-46BRC-65 +2
02People and peers
Add identity and private communication
Derive relationship-specific keys, reveal only needed certificate fields, and authenticate both ends of a channel.
BRC-42BRC-43BRC-52BRC-53BRC-77 +3
03Shared application state
Run an overlay service
Admit only protocol-valid transactions, expose focused lookups, discover peers, and keep topic state synchronized.
BRC-62BRC-95BRC-22BRC-24BRC-64 +4
04Value exchange
Send and receive peer payments
Compose derivation data, proof-carrying transactions, wallet receipt, and HTTP payment negotiation.
BRC-29BRC-50BRC-62BRC-70BRC-95 +4
05SPV foundation
Exchange proof-carrying transactions
Choose current transaction and Merkle-proof containers, then scope them to a transaction or output.
BRC-62BRC-71BRC-74BRC-95BRC-96 +1
06Digital assets
Support 1Sat assets in a BRC-100 wallet
Track wallet-owned token outputs, origin provenance, inscription envelopes, and portable proof packages.
BRC-46BRC-100BRC-147BRC-150BRC-158 +2
The missing middle
A standard is a part.
Interoperability is the system.
OpenStandards connects normative text to the decisions an implementer actually has to make.
- 01
Read the source
Full upstream text, exact snapshot, original authors, and canonical link.
- 02
Follow relations
Dependencies, citations, status notes, extensions, and historical context.
- 03
Find the code
Implementation sections, libraries, vectors, and package-level entry points.
- 04
Ship coherently
Use a task-based path so the pieces agree at every protocol boundary.
From reading to running
Field notes for builders
Short, inspectable starting points. Run a maintained reference service, borrow a prompt, then replace assumptions with tests.
Notebook 01 Maintained reference infrastructure
Run your own Wallet Storage
Boot the maintained Wallet Infrastructure reference server and MySQL locally, then connect a BRC-100 wallet without giving the storage service custody of user keys.
docker compose up --build Open runnable recipe → Notebook 02 Experimental reference implementation Run a reference CHIRP host
Boot the maintained filesystem UHRP server with BRC-167 complete-host routes, persistent object storage, closure validation, and a readiness check.
curl /ready Open runnable recipe → High-leverage interfaces
Core standards
BSV Key Derivation Scheme (BKDS)
The privacy-preserving key-derivation foundation beneath much of the stack.
Background Evaluation Extended Format (BEEF) Transactions
The core proof-carrying transaction container used by current implementations.
Atomic BEEF Transactions
Adds a single subject transaction to a BEEF package for portable verification.
Peer-to-Peer Mutual Authentication and Certificate Exchange Protocol
The current peer mutual-authentication and certificate-exchange protocol.
Overlay Network Data Synchronization
Defines the admission side of an overlay: which outputs belong to a topic.
From specification to software
Start from working implementations.
Standards create choice. Reference implementations make that choice practical. These are starting points, not exclusive vendors.
@bsv/sdk Transactions, keys, proofs, peer authentication, overlays, and the BRC-100 client surface. ↗ @bsv/wallet-toolbox BRC-100 wallet storage, services, signing, monitoring, and implementation tooling. ↗ Overlay packages Topic managers, lookup services, synchronization, and HTTP service integration. ↗ Official BRC repository The authoritative proposal text, history, issues, and contribution workflow. ↗
Open by design
Better maps make
bigger ecosystems.
Read openly. Implement independently. Interoperate by default.