# How the BSV blockchain works

> For the complete documentation index, see [llms.txt](https://bsvblockchain.com/docs/llms.txt).

How your app, the user's wallet and shared services work together on the BSV blockchain, and which page explains each concept.

import AppWalletFlowSteps from '/snippets/AppWalletFlowSteps.jsx';

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:

<div className="cards-interactive">

**[How transactions and fees work](https://bsvblockchain.com/docs/concepts/transactions/)**

Ownership lives in UTXOs (Unspent transaction output). You can handle each UTXO on its own, without a global account state.

**[BEEF (BRC-62)](https://bsvblockchain.com/docs/concepts/spv/)**

Your app verifies transactions itself through SPV (Simplified Payment Verification), with Merkle paths and block headers. BEEF bundles a transaction with the proofs that check needs.

**[BRC-100 Wallet Interface](https://bsvblockchain.com/docs/concepts/wallet-model/)**

Your app asks the wallet to act through BRC-100 (BSV Request for Comments 100), the standard wallet-to-application interface, and the wallet keeps the private keys.

**[How overlays work](https://bsvblockchain.com/docs/concepts/overlays/)**

An overlay service tracks your app's own transactions. Topic managers decide which outputs it admits, and lookup services answer queries about them.

</div>

## How an app talks to the wallet

The following diagram follows one request, from the app's call to the wallet's result:

<AppWalletFlowSteps />

The diagram has five steps. The app calls a BRC-100 method on the wallet, such as `createAction`, `signAction` or `listOutputs`. The wallet selects outputs, signs locally and returns the result. For `createAction`, the transaction can come back as AtomicBEEF. The app never takes custody of the private keys.

## Next steps

You can send a first transaction on testnet or see how the BSV blockchain stack fits together:

- [Send your first transaction](https://bsvblockchain.com/docs/get-started/quick-start-browser/)
- [How the BSV blockchain stack fits together](https://bsvblockchain.com/docs/concepts/architecture/)