Every standard opens with what problem it solves, in plain English. Find the right one in seconds, then paste it into your AI and build.
Free, no account. Browse all 162
BSV Unified Merkle Path (BUMP) Format
Different proof formats each solved part of the problem, leaving processors and clients converting between them. This defines one format that is cheap for a transaction processor to produce and convenient for a client to check.
Unified, Vendor-Neutral, Unchanging, and Open BSV Blockchain Standard Wallet-to-Application Interface
Every wallet historically had its own way of being talked to, so an application had to pick one and be locked to it. This defines a single interface every wallet can implement, so applications work with whichever wallet the user already has.
Wallet Transaction Output Tracking (Output Baskets)
An application keeping things on chain has to track which outputs are its own, and leaving that bookkeeping to the application invites mistakes. This lets the wallet group outputs by application and hand them back on request.
Start here
Each path is the short run of standards one kind of app actually needs, five to seven of them, in the order they make sense in, with a line on why each is there.
The path most people need. By the end you will know which calls a wallet exposes, how it decides whether to allow one, and where your app's data lives.
7 standards, starting at BRC-100
For when you need to send a transaction somewhere and have the other side believe it, without either party running a node.
6 standards, starting at BRC-12
From a direct peer-to-peer payment to charging for a single HTTP request, by way of the identity you need before you can charge anyone.
5 standards, starting at BRC-29
Writing to the chain is easy. Finding what you wrote, and letting other people find it, is what overlay services are for.
5 standards, starting at BRC-22
Twelve groups, the same ones upstream uses, each saying what is inside before you open it.
The interface your application talks to. Start here if you are wiring an app up to a wallet and want to know which calls exist.
How a transaction is written down and passed around, and how a recipient checks it is real without downloading the chain.
How two parties generate an unlimited supply of keys for each other without ever exchanging a private one. The maths under everything else.
Getting money from one party to another: invoices, payment destinations, and charging for an HTTP request.
The spending conditions attached to an output, from the everyday P2PKH to templates that carry data or enforce a rule.
Treating an output as a thing somebody owns. Issuance, transfer, and the protocols that track who holds what.
Naming one specific output, and the extra instructions a wallet keeps alongside it so it knows what the output is for.
Indexes that watch the chain for the subset of transactions you care about, so you can find data without scanning everything.
Proving who you are to another party, exchanging certificates, and sending messages when the other side may be offline.
Standards at the application layer: how a project describes its own deployment, and protocols built for a specific kind of app.
Representing a long series of events on chain without paying for a long chain of transactions.
Argument and commentary rather than specification. Useful for understanding why the standards look the way they do. Nothing here is normative.
Ranked by how many other standards reference them, which says more about what you need than recency or number does.
Nobody reads all 162 standards. People come back to four or five, over and over, for months. Both of these exist so you do not have to find them again.
Press it once. Then ⌘K reaches any of the 162 standards from wherever you are.
Favorites are saved to your wallet identity rather than to this browser, so they follow you to another machine.
Favoriting needs a BRC-100 wallet. Reading never does.
Search standards by number, title, author or topic