In this article
- TL;DR
- Where is my bitcoin before I send it?
- What happens when I press send?
- How does the network know I am allowed to spend it?
- Who checks that the transaction is legitimate?
- What actually changes on the blockchain?
- Where does the 0.05 BTC go afterwards?
- So what is my wallet balance?
- If you are in Switzerland
- Reader takeaway
- Sources
I work in the crypto self-custody space, and the first thing I tell beginners is that nothing moves when you send bitcoin. A lock changes hands.
The question I hear most often is the one a reader posted on r/Bitcoin in September 2026 after a few nights of research: she knew the words, wallets, keys, miners, nodes, blockchain, and still could not see how they connect. She had 0.1 BTC, wanted to send 0.05 BTC, and listed six questions. In my view the best reply came from u/SimpleHeadcount, and it began with advice I now give everyone: stop picturing coins moving around. I take her six questions in her order and carry her example through each one.
TL;DR
Your wallet holds keys, not coins. The coins are entries on a shared ledger, each entry locked to one key. Sending means your wallet writes a message that unlocks one entry and creates new ones, signs the message with your key, and hands it to the network. Every node checks the signature and that the entry is still unspent. A miner puts the message in a block. The old entry is now spent and two new entries exist, one locked to her key and one locked to a fresh key of yours. No coin travelled anywhere. A lock changed.
Where is my bitcoin before I send it?
On the ledger, in every copy of it. The ledger is the blockchain, and about 25,500 computers that accept connections, called nodes, each keep a full copy, plus an unknown number behind home routers that Bitnodes cannot count (25,564 reachable on 11 October 2026, Bitnodes). Your 0.1 BTC is one line in that ledger. The line says two things: an amount, and a lock. The lock is derived from your public key. Only the matching private key can open it.
That line has a name in Bitcoin: an unspent transaction output, or UTXO. Every bitcoin that exists sits in one of these (Bitcoin developer guide). Your wallet does not contain the line. It contains the private key, and it scans the ledger for every line its keys can open, then adds them up. That sum is your balance. As u/chainglance_cm put it in the thread, the balance is your app adding up the chunks it can see are yours.
This is why "your bitcoin is not in your wallet" is true and still confusing. The phone app is a keyring plus a calculator. Delete the app and the lines stay on the ledger. Restore the keys from your 12 or 24 words on another phone and the same balance appears, because the ledger never changed. The wallet recovery guide walks through that restore.
One more thing about the line. Its amount is fixed. A 0.1 BTC entry is like a single banknote worth 0.1. You cannot tear a corner off to pay 0.05. You spend the whole note and get change.
What happens when I press send?
Your wallet writes a short message. In plain words it says: unlock the 0.1 BTC entry, create a 0.05 BTC entry locked to her key, create a 0.0499 BTC entry locked to a new key of yours, and leave the 0.0001 BTC difference as a fee. That message is the transaction. It has one input, the entry being spent, and two outputs, the new entries being created. If you want to see the raw fields, learnmeabitcoin has a transaction walkthrough with real examples.
Then your wallet signs the message with your private key. The signature is a piece of maths that proves the message was approved by whoever holds the key behind the lock, without revealing the key. The private key never leaves your device. On a hardware wallet such as the BitBox02, designed and manufactured in Switzerland, the seed stays encrypted on the device and signing happens inside it; the phone or laptop only sees the signed message (BitBox security architecture).
Then your wallet hands the signed message to a handful of nodes it is connected to. Each of those checks it and passes it to its own peers after a short random delay, which Bitcoin Core sets at 2 seconds on average toward peers it connected to and 5 seconds toward peers that connected to it (net_processing.cpp). A few hops later most of the network has seen it. At this point the transaction is unconfirmed. Most nodes know about it, and no block holds it yet.
The change output is the part that surprises people. Your wallet created a new address from your seed and sent 0.0499 BTC to it. In a block explorer that address looks like a stranger. It is yours, and your wallet will count it in your balance a moment later. Most wallets do this so that no address is used twice, as the Bitcoin developer guide recommends, which keeps your history harder to trace. The privacy chapter covers why that matters.
How does the network know I am allowed to spend it?
Only the signature.
The reader's follow-up question in the thread was sharper than the original: what makes an entry belong to me in the first place, and how does the network know her address is connected to her private key? Nobody knows, and nobody checks in advance. There is no registry of who owns which address. Most addresses are a fingerprint, a hash, of a public key; a newer Taproot address carries the public key itself (BIP 341). A public key is derived from a private key. Your wallet generated the key, and that was the whole act of ownership. As u/Hissykittykat wrote, the only thing that makes it yours is that only you know it.
When she gives you an address, you lock the 0.05 BTC entry to it. The network accepts the lock without asking whose it is. When she later wants to spend the entry, her wallet signs with her private key, and every node checks: does this signature match the public key on the lock? Yes, so the spend is valid. If she gave you a typo that happened to be a valid address nobody holds the key for, the coins would be locked forever. Bitcoin addresses carry a checksum, and the newer bech32 format guarantees it detects any error affecting at most 4 characters (BIP 173), so your wallet rejects a typo before sending. A real address that belongs to the wrong person passes that check.
The thread also asked whether big companies with enough computers could brute-force a key. A private key is a number below a limit of about 1.16 times 10 to the power of 77 (SEC 2, secp256k1). No hardware that exists can try enough of them to find one that holds coins. You lose coins in duller ways: you type the seed phrase into a website, or a backup photo sits in a cloud album. The self-custody guide closes those doors.
Who checks that the transaction is legitimate?
Every node, on its own, before it tells anyone else.
When a node receives your signed message it runs the same checks as every other node: the signature opens the lock on the input, nobody has spent that input already, the outputs add up to no more than the input, and the message is well formed. The node drops a transaction that fails any check and never forwards it. It forwards one that passes and holds it in its waiting room, the mempool.
Miners run nodes too, or work for a pool whose node builds the block. They take transactions from the mempool, run the same checks again, and bundle them into a candidate block. Then they race to find a number that makes the block's hash fall below a target, which is the proof of work. The protocol targets one block every 10 minutes on average (Bitcoin Core); the miner who wins broadcasts the block. Every node then checks every transaction in the block, and the proof of work, before adding the block to its own copy of the ledger. Nodes accept a block only if all its transactions are valid and not already spent (whitepaper, section 5), so a miner who includes an invalid transaction has wasted electricity on a block the network throws away.
No single party checks for the others, so every node checks for itself. You have no head office to ask. If you run a node, your own software performs those checks on your own hardware, and your wallet can ask it instead of a company's server. In my view that is the only vote you get in the system.
What actually changes on the blockchain?
Two small things.
Your 0.1 BTC entry is marked spent. It is not deleted; the history stays, but every node removes it from the set of entries that can still be spent. Then two new entries are added to that set: 0.05 BTC locked to her key, 0.0499 BTC locked to your new key. The 0.0001 BTC that is neither goes to the miner who found the block, as the fee (whitepaper, section 6). Fees are set by the size of the signed transaction in bytes, and the amount moved plays no part (Bitcoin developer guide): a 100 BTC send and a 0.001 BTC send of the same size need the same fee to compete for the same block. On 11 October 2026 mempool.space recommended 1 satoshi per virtual byte even for the next block (fee API), so at that day's CHF 69,063 per bitcoin (price API) a simple send cost well under CHF 1. The 0.0001 BTC in the example is far more than that day required.
Confirmations are how many blocks have been built on top of the one holding your transaction. One confirmation means it is in the newest block. Each further block makes reversing it harder (whitepaper, section 11). Each exchange sets its own count; Kraken credits a bitcoin deposit after 3 confirmations (Kraken support). My rule of thumb: for a coffee, one confirmation or even zero is fine; for a car, wait for six.
Where does the 0.05 BTC go afterwards?
Nowhere. u/SimpleHeadcount said it early in the thread: the ledger updates the pointers. The reader answered that she was starting to get it.
Her wallet has been watching the ledger for entries locked to her keys. After the block, it finds one worth 0.05 BTC and shows her balance went up. Her phone received no file and no message; her wallet noticed a new line it can open. The same happens on your side with the 0.0499 BTC change entry, which is why your balance drops by 0.0501 BTC rather than 0.05.
Later, when she pays someone, her wallet will use that 0.05 BTC entry as an input to a new transaction, and the whole story repeats. Every bitcoin that exists is a chain of these hand-offs going back to the block in which a miner first created it (whitepaper, sections 2 and 6). You can follow any of them yourself on a block explorer such as mempool.space. Paste a transaction ID and you see the inputs, the outputs, the fee, and how many confirmations it has.
So what is my wallet balance?
The sum of every ledger entry your keys can unlock. Neither your phone nor any company stores that number, and only a transaction you sign can change it.
The keys are the asset, so back up the 12 or 24 words on paper or steel and the phone becomes replaceable. There is no undo: a signed transaction that reached the network is done, and the checks that protect you from theft also rule out a refund, which is why I send a small test amount to any new address before the real one. And no single party can freeze the entries. A bank can block a transfer; one node can refuse to relay your transaction, but every other node and miner still accepts a valid signature.
One warning the thread got right: the reader offered to take questions in private, and a commenter replied that invitations to private conversations are almost always scams, because isolating the victim comes first. If you are learning, learn in public. Anyone who offers private help with your wallet wants your seed phrase. The scams chapter lists the patterns.
If you are in Switzerland
The mechanics are the same in every country. The on-ramp differs. Relai and Pocket Bitcoin send each purchase straight to a wallet only you control, with a transaction like the one above that has your address as an output. Swissquote keeps the coins in its custody until you withdraw them, and charges USD 10 for each bitcoin withdrawal. From the moment the entry is locked to your key, the broker is out of the picture, which is the point of buying to your own wallet rather than leaving coins on an exchange. The buying guide compares the options and the cold storage guide covers what to do once the coins arrive. If you want the keys on Swiss hardware, BitBox devices are designed and manufactured in Switzerland by Zurich-based Shift Crypto (BitBox blog).
For tax, sending bitcoin between your own addresses is not a sale, and the change output is not income: the ESTV working paper says holding bitcoin produces no income and puts it under the cantonal wealth tax (ESTV, Arbeitspapier Kryptowährungen). What your cantonal tax office wants is the total you hold at the end of the tax period, at the value the ESTV publishes in its Kursliste, which the Swiss tax guide explains.
Reader takeaway
- Bitcoin lives on the ledger as locked entries. Your wallet holds the keys and adds up the entries it can open.
- Sending means writing a message that spends one entry whole and creates new ones, then signing it.
- Ownership is the signature. There is no registry, and there is no need for one.
- Every node checks every transaction. Miners order them into blocks. Nobody is in charge.
- The old entry is marked spent, new entries appear, the fee goes to the miner.
- The coins go nowhere. A lock changes. Her wallet finds an entry it can open.
Not financial, legal, or tax advice. Amounts in the example are illustrative; the fee depends on network load on the day.
Sources
- Bitcoin whitepaper, sections 2, 5, 6 and 11
- Bitcoin developer guide, transactions
- Bitcoin Core source, block interval and relay delays
- SEC 2, secp256k1 parameters
- BIP 173 and BIP 341
- Bitnodes, reachable node count
- mempool.space block explorer
- ESTV working paper on cryptocurrencies
- learnmeabitcoin, transactions and UTXOs
- r/Bitcoin thread, I feel like I am missing something really obvious about Bitcoin
