BSV blockchainBSV blockchain

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.

TermMeaning
ArcadeThe former name of BSV Broadcaster, until version 0.19.0. The public endpoint hostnames still contain arcade.
AtomicBEEFBEEF for a single transaction (BRC-95).
basketA named group of outputs in a wallet, so an app can list them later.
BEEFBackground Evaluation Extended Format (BRC-62): a transaction with the proof a host needs to verify it, without running a node.
BRCBSV Request for Comments: a numbered standard for the BSV blockchain, such as BRC-100.
BRC-29The 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-42BSV Key Derivation Scheme: two parties derive new keys for each other from their keys and an invoice number, without sharing a private key.
BRC-100The standard interface between an app and a wallet.
BSVBitcoinSV (BSV), the native coin of the BSV blockchain.
BSV blockchainThe blockchain that implements the original Bitcoin protocol.
@bsv/sdkThe base package for building on the BSV blockchain: hashing, keys, Script, BEEF and Merkle paths, and WalletClient.
@bsv/simpleA package with helpers for payments and tokens.
@bsv/wallet-toolboxA package for building a wallet.
BSV BroadcasterBSV 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 DesktopA desktop wallet for the BSV blockchain. It holds the keys, chooses the coins, signs, and asks the user to approve each payment.
BUMPBSV Unified Merkle Path (BRC-74): a compact Merkle path that proves a transaction is in a block.
certificateA signed statement about a user, issued by a third party, like a verifiable credential.
ChaintracksA block header service. A wallet uses it to check Merkle paths against the block headers.
EFExtended Format (BRC-30): the raw transaction plus the satoshis and locking script of every output it spends.
faucetA site that sends free testnet coins, such as bsvfaucet.com.
identity keyThe public key that identifies a wallet to an app. The private key never leaves the wallet.
internalizeAdd a received payment to the wallet so its coins can be spent.
locking scriptThe part of a transaction output that sets the condition to spend it.
lookup serviceThe part of an overlay service that answers queries about what its topic managers admitted.
MainnetThe live BSV blockchain network, where coins have real value and a payment cannot be undone.
Merkle pathThe proof that a transaction is in a block, checked against the block header.
MessageBoxA service that delivers encrypted messages and payments between users by their identity key. A host holds each message until its recipient reads it.
originatorThe name of your app, passed as the second argument of WalletClient, that BSV Desktop shows in its windows.
overlay serviceA service that tracks the transactions of a topic: topic managers decide what is admitted, and lookup services query it.
P2PKHPay to Public Key Hash: the locking script that pays to an address.
PaymailA handle that resolves to a user’s identity key. Its domain lists the Paymail services it supports.
private keyThe secret key that signs transactions. It stays in the wallet and never goes in app code.
recovery phraseThe words that restore a wallet’s keys, twelve in BSV Desktop 3. Anyone who has them can access the wallet.
satoshiThe smallest unit of BSV. 100,000,000 satoshis make 1 BSV.
SEEN_ON_NETWORKThe BSV Broadcaster status of a transaction seen in a miner’s subtree. Safe to treat as zero-confirmation, before it is mined.
Spending RequestThe BSV Desktop window where the user checks a payment an app asks for, then approves it with Authorize or refuses it with Deny.
SPVSimplified Payment Verification: checking a transaction with its Merkle path and block headers, without running a node.
STEAKSubmitted Transaction Execution AcKnowledgment: the answer of an overlay host that says which outputs each topic admitted.
TeranodeThe node software of the BSV blockchain.
testnetThe BSV blockchain test network, where coins are free from a faucet, for building and testing.
topic managerThe part of an overlay service that decides which transactions are admitted.
transaction IDThe 64-character ID of a transaction, used to look it up. Written txid in code.
UHRPUniversal Hash Resolution Protocol (BRC-26): file storage where a file is found by the hash of its content.
UTXOUnspent transaction output: a coin that can still be spent. The BSV blockchain runs on the UTXO model.
walletHolds the user’s keys, chooses the coins and signs transactions. Apps ask it to pay, and the user approves.
WalletClientThe @bsv/sdk class an app uses to talk to the user’s wallet, such as BSV Desktop.

To learn more about these terms on the BSV blockchain, review these articles: