How the BSV blockchain works
On the BSV blockchain, the app, the wallet and shared services each have one job. Your app asks for actions and verifies the results, the user’s wallet holds the private keys and signs, and shared services broadcast transactions, provide block headers and index app data.
The core ideas
Four ideas shape how these parts work together, and each has its own page:
How transactions and fees work
Ownership lives in UTXOsUnspent transaction output. You can handle each UTXO on its own, without a global account state.
BEEF (BRC-62)
Your app verifies transactions itself through SPVSimplified Payment Verification, with Merkle paths and block headers. BEEF bundles a transaction with the proofs that check needs.
BRC-100 Wallet Interface
Your app asks the wallet to act through BRC-100BSV Request for Comments 100, the standard wallet-to-application interface, and the wallet keeps the private keys.
How overlays work
An overlay service tracks your app’s own transactions. Topic managers decide which outputs it admits, and lookup services answer queries about them.
How an app talks to the wallet
The following diagram follows one request, from the app’s call to the wallet’s result:
Next steps
You can send a first transaction on testnet or see how the BSV blockchain stack fits together: