Network profile

Bitcoin: the network, the asset and its limits

Bitcoin is a settlement network optimised for censorship resistance, not for throughput. Every other property follows from that choice.

Layer 1 · Proof of WorkChecked 8 Nov 2026

Bitcoin is a settlement network built around a single promise: no one can stop a valid transaction or create an invalid one, and the supply cannot be quietly changed.

Native token
BTC, issued by the protocol and capped at 21 million coins
Type
Layer 1 base chain without general-purpose smart contracts
Consensus
Proof of work; the chain with the most accumulated work is the valid one
Fees
Open auction in satoshis per virtual byte (sat/vB) for space in a block
Settlement
Self-settled; finality is probabilistic and deepens with each confirmation
Ecosystem
Payments, Lightning, custody, mining, limited asset issuance

How it works

Bitcoin does not store balances. It stores unspent transaction outputs, and every transaction consumes existing outputs and creates new ones. Your wallet balance is the sum of the outputs your keys can unlock, which is why a payment usually leaves a change output pointing back at you and why «coin control» exists as a feature.

Ownership is a spending condition, not an entry in an account table. The common case is a public key hash that requires a signature from the matching private key, but the same mechanism covers multisignature arrangements, timelocks and hash locks. SegWit changed how witness data is counted and stored; Taproot added Schnorr signatures and made complicated spending conditions look like ordinary payments on chain.

Blocks are produced on a target of roughly ten minutes, and difficulty retargets every 2,016 blocks so that the average holds when hash rate changes. Miners extend the chain by spending electricity to find a header hash below a threshold, and they are paid in new issuance plus the fees of every transaction they include. Issuance halves on a fixed schedule until the cap is reached, so miner revenue shifts towards fees over decades.

The narrow scripting language is the point. There is less to get wrong, the rules are easier to verify, and the upgrade path is deliberately slow.

Fees: the mechanism

No protocol constant sets your fee. A transaction declares what it pays per virtual byte, and miners pick from the mempool, ordering by fee density because block space is fixed. When demand rises the effective price rises; when the queue empties, it collapses.

The fee is a bid, so it can be changed after the fact:

  • Replacement (RBF). You resubmit the same transaction with a higher bid, and nodes replace the old version in their mempool.
  • Child pays for parent (CPFP). You spend an unconfirmed output in a new transaction that pays enough for both.

You pay for size, not for value. A large transfer with few inputs can cost less than a small one with many, which is why consolidating small outputs during quiet periods is a real practice.

Fee revenue is also the long-term security budget. As issuance declines, miners depend more on fees, so a chain with little activity funds less work than one with heavy use. That is a structural question, not a prediction.

What is actually built there

Settlement and custody dominate: institutional and individual transfers, treasury reserves, and remittances where the local rail is slower or less reliable. Around that sit wallets, hardware signers, multisignature custody and a mining industry.

Lightning is the main scaling layer. It opens payment channels, moves payments off chain and settles the net result later, which makes small payments cheap but introduces inbound liquidity, channel management and routing as new problems. It is not «Bitcoin but faster» for arbitrary transactions; it is a payment network with its own operational limits.

Asset issuance exists through add-on protocols that write data into Bitcoin transactions. They inherit Bitcoin's availability, not its full security model, and each one brings its own trust assumptions.

Risks and limits

  • No general programmability. Complex logic lives in layers, sidechains or federations, each with a different security story.
  • Finality is probabilistic. Confirmations reduce risk; they do not erase it.
  • Mining is concentrated in a few large pools and cheap-energy regions, which keeps censorship resistance an open question.
  • Privacy is weak by default. The ledger is public and permanent, and address reuse or a KYC withdrawal links your identity to it.
  • Self-custody is absolute. No reset, no chargeback, no support desk, and a wrong address is a completed donation.

Official sources

  • bitcoin.org — protocol overview, wallets and developer documentation.
  • Bitcoin Core — the reference implementation and its release notes.
  • mempool.space - blocks, mempool state and fee estimates.

If you want the concept before the protocol, Bitcoin and blockchain: how a ledger becomes money covers UTXOs, proof of work and what an address actually is.