BSV blockchain glossary
Look up a term you meet while building on the BSV blockchain, in one line. When a page explains the term in depth, the term links to it.
| Term | Meaning |
|---|---|
| Arcade | The former name of BSV Broadcaster, until version 0.19.0. The public endpoint hostnames still contain arcade. |
| AtomicBEEF | BEEF for a single transaction (BRC-95). |
| basket | A named group of outputs in a wallet, so an app can list them later. |
| BEEF | Background Evaluation Extended Format (BRC-62): a transaction with the proof a host needs to verify it, without running a node. |
| BRC | BSV Request for Comments: a numbered standard for the BSV blockchain, such as BRC-100. |
| BRC-29 | The payment protocol between a sender and a recipient: the sender derives the recipient’s key with BRC-42 and sends the transaction as BEEF. |
| BRC-42 | BSV Key Derivation Scheme: two parties derive new keys for each other from their keys and an invoice number, without sharing a private key. |
| BRC-100 | The standard interface between an app and a wallet. |
| BSV | BitcoinSV (BSV), the native coin of the BSV blockchain. |
| BSV blockchain | The blockchain that implements the original Bitcoin protocol. |
@bsv/sdk | The base package for building on the BSV blockchain: hashing, keys, Script, BEEF and Merkle paths, and WalletClient. |
@bsv/simple | A package with helpers for payments and tokens. |
@bsv/wallet-toolbox | A package for building a wallet. |
| BSV Broadcaster | BSV Association’s transaction broadcaster, formerly called Arcade. It delivers a signed transaction to the network, follows it until a miner includes it in a block and returns the Merkle path that proves it. |
| BSV Desktop | A desktop wallet for the BSV blockchain. It holds the keys, chooses the coins, signs, and asks the user to approve each payment. |
| BUMP | BSV Unified Merkle Path (BRC-74): a compact Merkle path that proves a transaction is in a block. |
| certificate | A signed statement about a user, issued by a third party, like a verifiable credential. |
| Chaintracks | A block header service. A wallet uses it to check Merkle paths against the block headers. |
| EF | Extended Format (BRC-30): the raw transaction plus the satoshis and locking script of every output it spends. |
| faucet | A site that sends free testnet coins, such as bsvfaucet.com. |
| identity key | The public key that identifies a wallet to an app. The private key never leaves the wallet. |
| internalize | Add a received payment to the wallet so its coins can be spent. |
| locking script | The part of a transaction output that sets the condition to spend it. |
| lookup service | The part of an overlay service that answers queries about what its topic managers admitted. |
| Mainnet | The live BSV blockchain network, where coins have real value and a payment cannot be undone. |
| Merkle path | The proof that a transaction is in a block, checked against the block header. |
| MessageBox | A service that delivers encrypted messages and payments between users by their identity key. A host holds each message until its recipient reads it. |
| originator | The name of your app, passed as the second argument of WalletClient, that BSV Desktop shows in its windows. |
| overlay service | A service that tracks the transactions of a topic: topic managers decide what is admitted, and lookup services query it. |
| P2PKH | Pay to Public Key Hash: the locking script that pays to an address. |
| Paymail | A handle that resolves to a user’s identity key. Its domain lists the Paymail services it supports. |
| private key | The secret key that signs transactions. It stays in the wallet and never goes in app code. |
| recovery phrase | The words that restore a wallet’s keys, twelve in BSV Desktop 3. Anyone who has them can access the wallet. |
| satoshi | The smallest unit of BSV. 100,000,000 satoshis make 1 BSV. |
SEEN_ON_NETWORK | The BSV Broadcaster status of a transaction seen in a miner’s subtree. Safe to treat as zero-confirmation, before it is mined. |
| Spending Request | The BSV Desktop window where the user checks a payment an app asks for, then approves it with Authorize or refuses it with Deny. |
| SPV | Simplified Payment Verification: checking a transaction with its Merkle path and block headers, without running a node. |
| STEAK | Submitted Transaction Execution AcKnowledgment: the answer of an overlay host that says which outputs each topic admitted. |
| Teranode | The node software of the BSV blockchain. |
| testnet | The BSV blockchain test network, where coins are free from a faucet, for building and testing. |
| topic manager | The part of an overlay service that decides which transactions are admitted. |
| transaction ID | The 64-character ID of a transaction, used to look it up. Written txid in code. |
| UHRP | Universal Hash Resolution Protocol (BRC-26): file storage where a file is found by the hash of its content. |
| UTXO | Unspent transaction output: a coin that can still be spent. The BSV blockchain runs on the UTXO model. |
| wallet | Holds the user’s keys, chooses the coins and signs transactions. Apps ask it to pay, and the user approves. |
WalletClient | The @bsv/sdk class an app uses to talk to the user’s wallet, such as BSV Desktop. |
Related articles
To learn more about these terms on the BSV blockchain, review these articles:
Learn › How the BSV blockchain works › About the BSV blockchain