Using Bitcoin as Money

Bitcoin Is Money, So Use It

It's easy to think of Bitcoin as something you just buy and hold. Saving in sound money is powerful, but money has a second job: it has to move. A currency nobody can spend or earn isn't really money; it's a collectible.

Bitcoin was designed as peer-to-peer electronic cash: money you can send to anyone, anywhere, without asking a bank's permission. It only reaches its potential when we actually use it that way: paying a local vendor, tipping a creator, settling up with a friend. The more we circulate Bitcoin, the stronger and more useful the network we're all building becomes.

Value-for-Value: Money With Meaning

One of the most natural ways to start using Bitcoin as money is Value-for-Value (V4V). Instead of ads, paywalls, or middlemen, V4V lets you support the people and projects you appreciate by sending them Bitcoin directly: streaming a few sats per minute to a podcaster as you listen, or sending a "boost" when something really lands.

That's real money flowing straight from listener to creator, with no platform skimming the middle. Our #40HPW page is full of Value-for-Value podcasts you can support this way. But to take part, and to use Bitcoin as money at all, you need to be comfortable sending and receiving. Here's how it works.

Two Layers: The Base Chain and Lightning

Bitcoin has two layers, and it helps to know which one you're using:

• The base chain is the bedrock. Every transaction is recorded on the blockchain, settled and final. It's ideal for larger amounts and savings, costs a small fee, and takes a confirmation or two. It's what most of this guide describes.
• The Lightning Network sits on top of Bitcoin and is built for the small, everyday stuff: payments that are near-instant and cost a fraction of a cent. This is what makes Value-for-Value practical: streaming sats and sending boosts without paying a base-chain fee each time.

Most people use both: Lightning for spending and V4V, the base chain for bigger payments and moving savings into cold storage.

Receiving Bitcoin

To get paid, you share a Bitcoin address, a string of letters and numbers that's really an encoded lock: a little script that only your key can open. Your wallet can show it as text or as a QR code for someone to scan, which avoids typos.

• A fresh address each time. Good wallets create a new address for every payment. That's for privacy: it makes it harder for anyone to link your payments together. Reusing an old address works, but a new one is better.
• Built-in error checking. Every address carries a checksum, so your wallet will reject one with a typo. You only need to eyeball the first and last few characters.
• Different flavours. Older addresses start with 1 or 3; modern SegWit and Taproot addresses start with bc1 and are a little cheaper to spend and better for privacy. When given the choice, prefer a bc1 address.

Sending Bitcoin

Sending takes three things: the recipient's address, an amount (in bitcoin or sats), and a fee. Your wallet then builds the transaction and broadcasts it to the network.

Under the hood, your wallet uses your private key to produce a signature that unlocks the coins you're spending. The signature mathematically commits to that exact transaction (change a single detail and it's invalid) and proves the coins are yours without ever revealing the key. (Older wallets sign with ECDSA; Taproot upgraded this to Schnorr signatures, which are smaller and more private.)

Coins Are Chunks: The UTXO Model

Here's a detail that explains a lot. Your balance isn't a single number in an account. It's a collection of discrete chunks of bitcoin called UTXOs (unspent transaction outputs). Picture the individual coins and bills in a physical wallet: you might be holding a 0.5, a 0.2, and a 0.05.

When you spend, your wallet selects enough chunks to cover the amount (these become the transaction's inputs) and creates new chunks as outputs: one to the recipient, and usually one back to you as change, exactly like getting change from a $20 bill. Each output is locked by a script; to spend it later, your signature has to satisfy that lock. The new outputs become fresh UTXOs in each wallet.

This is why the total leaving your wallet can look bigger than what you sent: you spent a whole chunk and the remainder came back as change. Two practical notes: very tiny UTXOs (dust) can cost more in fees to spend than they're worth, and when fees are low it's smart to consolidate, combining many small chunks into one, so future payments are cheaper. Modern wallets manage most of this for you automatically.

Fees: Paying for Block Space

Every transaction competes for limited space in the next block. Unconfirmed transactions wait in the mempool (a kind of waiting room), and miners include the ones offering the most. The fee itself is simply the leftover, your inputs minus your outputs, which the miner collects for including you.

Fees are priced in sats per vByte: satoshis per unit of transaction size, not as a percentage of the amount you send. Size is measured in weight units (a vByte is four weight units), and SegWit gives signature data a discount, which is part of why bc1 addresses are cheaper to spend. A transaction with many inputs is physically larger, so it costs more; that's why sending $10 and sending $10,000 can cost the same if the transactions are the same size.

• In a hurry? Pay a higher feerate to land in the next block or two.
• Not in a hurry? Pay a lower feerate and let it confirm when the network is quieter. When things are calm, even 1 sat/vByte gets there.
• Stuck? If a low-fee transaction stalls, most wallets can rescue it, either by raising its fee directly (RBF, opt-in replace-by-fee) or by spending its change with a high fee to drag it along (CPFP, child-pays-for-parent). Unconfirmed transactions are eventually dropped after about two weeks, so bump rather than wait forever.

Confirmations

Your transaction is confirmed once it's included in a mined block. Each new block stacked on top adds another confirmation, making it ever harder to reverse. This is what's often called probabilistic finality: never quite 100%, but exponentially closer with every block.

• 1 confirmation is plenty for everyday payments.
• 2 confirmations guard against rare, natural chain reorganizations.
• 6 confirmations is old-school caution, really only needed for very large amounts.

Every transaction has a TXID (a unique ID). Paste it into a block explorer like mempool.space to watch it confirm in real time. Curious how blocks actually get mined, and why a reorganization can briefly undo the newest one? See The Bitcoin Network.

A Closer Look at Lightning

So how does Lightning move money instantly without touching the blockchain each time? Two people open a payment channel, which is really a shared 2-of-2 multisig address funded by an on-chain transaction. From then on they can pay each other back and forth instantly by re-signing who owns what, with nothing hitting the chain. And because these channels link up across the network, you can pay someone you have no direct channel with. The payment is routed through intermediaries, who can't steal it in transit. You only settle on-chain when you open or close a channel. A Lightning invoice (or a reusable Lightning address) is just the request you scan or paste to pay. That's the plumbing behind V4V boosts and streaming sats.