What Bitcoin is
Bitcoin is a shared global ledger plus the rules for keeping it consistent. A ledger is just a list of who has what. The "shared" part means many computers around the world keep the same list, in sync, by following the same rules. The "rules" are the Bitcoin software: open, public, and updated only slowly and carefully. The unit tracked on that ledger is also called Bitcoin, written as BTC.
That is the whole idea. Everything else, including wallets, mining, and fees, is detail about how the ledger stays consistent without a central administrator.
What Bitcoin is not
Plenty of confusion comes from things Bitcoin is often assumed to be, and is not.
- Bitcoin is not a company. It has no CEO, board, support line, or marketing team.
- Bitcoin is not anonymous. The ledger is public; addresses are not directly tied to names, but patterns can be analysed.
- Bitcoin is not a tradeable share of a business. Owning Bitcoin is not owning equity in anything.
- Bitcoin is not "blockchain technology". It uses a chain of blocks, but "blockchain" became a marketing word for many unrelated systems.
- Bitcoin is not a meme coin, a token, an NFT, or an altcoin. Those are different systems.
Why Bitcoin was designed
Bitcoin was designed to solve a specific, narrow problem: how to let strangers send a digital unit of value over the internet without any single party in charge of keeping the books. Before Bitcoin, the usual answer was "a bank, a card network, or a payment processor sits in the middle". Bitcoin is one attempt at saying "what if no single party sits in the middle". The design takes a strong position on that question and lives with the trade-offs.
The trade-offs are real. Transactions are slower than tapping a card. Mistakes are permanent. Energy use is real. Understanding why the design accepts those trade-offs is the point of the rest of this page.
Why a fixed supply is discussed
Bitcoin's rules cap the total number of units that will ever exist at twenty-one million. That number is not magic. It is a deliberate scarcity choice that the original software hard-coded and that node operators have collectively kept in place. The cap is one of the most discussed properties of the system.
We mention the cap here because it shows up in every beginner conversation, but we deliberately avoid wrapping it in price language. A fixed supply does not guarantee a rising price. It guarantees a known ceiling. Those are very different statements, and only one of them is honest.
Transactions
A Bitcoin transaction is a signed message. It says, roughly: "take these previously received pieces, send these amounts to these addresses, and leave the change here." Once the network accepts the transaction into a block, the ledger is updated and the change is effectively permanent.
Several details follow from that simple shape:
- Transactions reference earlier received pieces, not "account balances".
- Change is sent back to an address you control, in the same transaction.
- There is no chargeback. There is no recall. There is no "are you sure" after the fact.
- A typo in an address is not a customer-service problem. It is a permanent transfer to whoever (if anyone) controls that address.
Blocks
Transactions are grouped together into blocks. A block is a batch of transactions plus a reference to the previous block. Each new block extends the chain. The reason for batching, rather than confirming transactions one by one, is that batching makes it dramatically harder for any single participant to rewrite history. To change a confirmed transaction, an attacker would need to redo all the work from that block forward, faster than the rest of the network keeps producing new blocks.
Miners
A miner is a specialised participant that proposes new blocks. Mining involves repeatedly trying different combinations of inputs until a block meets the network's difficulty rule. The first miner to find a valid block broadcasts it; other participants check it and accept it if it follows the rules. The miner is paid in newly issued Bitcoin (until the issuance schedule ends) and in fees attached to the transactions in the block.
Mining looks dramatic from the outside. Inside the system, it is a quiet auction: whoever does the most work, finds the next block, and is paid for it. The "work" is what stops anyone from trivially rewriting the ledger.
Nodes
A node is any computer running the Bitcoin software, keeping a copy of the ledger, and checking incoming blocks and transactions against the rules. Nodes are not miners; they do not propose new blocks. They are the people in the room who decide whether a proposed block is valid.
This is the part most people miss. The network's rules are enforced by every node independently. If a miner produced a block that broke the rules, nodes would simply reject it and the rest of the network would carry on. That separation between proposing and validating is what makes the system politically interesting.
Fees
Each transaction can include a fee, paid to the miner that confirms it. Fees adjust based on demand: if many people are trying to transact at the same time, fees rise; if the network is quiet, fees fall. Beginners often overpay because their wallet software picked a "fast" default. Slow transactions on a quiet day are usually fine, and saving on fees adds up over time.
Confirmations
A transaction is confirmed once it is included in a block. Each additional block on top of it is an extra confirmation. More confirmations make it exponentially less likely that the transaction could be reversed. For small amounts, one confirmation is usually enough. For large amounts, exchanges and custodians often wait for several. There is no single correct number; it depends on the value at stake and how cautious you want to be.
How this all hangs together
Stepping back: users sign transactions with their keys; transactions are broadcast; miners batch them into blocks; nodes validate the blocks; the ledger updates; everyone stays in sync because everyone is running the same rules. That is the whole system. Wallets, exchanges, custodians, and tools sit around the edges and translate the system for humans.
Common beginner traps
- Treating the wallet app as "my Bitcoin". The Bitcoin is on the ledger; the wallet holds keys.
- Thinking confirmations mean a transaction is "approved" by a person. They are not.
- Believing customer support can reverse a sent transaction. They cannot.
- Assuming Bitcoin is anonymous. It is not.
- Equating Bitcoin with every other crypto asset. They are different systems with different rules.
What to read next
From here, the structured next steps are courses for the full module path, wallet safety for the practical risk layer, glossary for a vocabulary check, and FAQs for the small questions that always come up after a first read.