Field Notes

entity

Bitcoin

StatusStableUpdatedStands on3 sourcesSupportsnotes

Bitcoin is a permissionless asset and settlement network. It lets participants transfer BTC under rules enforced by independently run software, without an issuer promising redemption or a central operator authorizing each payment. Its distinctive contribution is not maximum throughput. It is a deliberately conservative base layer that combines scarce issuance, bearer-style key control, and PoW ordering of a public transaction history.

Cryptocurrency design comparison places this base layer beside systems that optimize for privacy, programmability, or faster payments. The Lightning Network is a separate payment-channel layer that uses BTC and ultimately depends on Bitcoin transactions for channel enforcement.

How the base layer works

A Bitcoin transaction consumes earlier UTXOs and creates new ones whose locking conditions define who can spend them next. Nodes validate signatures, transaction structure, and consensus rules before accepting a transaction or block. Miners assemble valid transactions into candidate blocks and compete to extend the chain through PoW.1

flowchart TD
  A[Signed transaction] --> B[Node validation]
  B --> C[Mempool]
  C --> D[Proof-of-work block]
  D --> E[More blocks extend history]
  E --> F[Increasing settlement confidence]

The chain does not provide a moment of absolute finality. A payment becomes progressively harder to reverse as more work accumulates after its block. How many confirmations are adequate depends on the value at risk, the recipient’s tolerance for reorganization, and whether the transaction is replaceable or exposed to other payment risks.

Security and control are separate questions

Bitcoin’s consensus can make rewriting confirmed history expensive without protecting a user from losing a signing key, accepting a malicious transaction, or relying on an insolvent custodian. The security unit therefore includes node validation, wallet implementation, key custody, backup and recovery, and any exchange or payment processor in the path.

The protocol constrains issuance toward a terminal limit of 21 million BTC. That makes supply predictable under the maintained rules. Purchasing power is set on the demand side, where nothing is fixed. Market liquidity, leverage, regulation, custody failures, and demand can still produce large price changes.

Privacy is limited by the public graph

Bitcoin addresses are pseudonyms rather than identities, but transactions, amounts, and UTXO relationships are public. Address reuse, common-input heuristics, timing, amounts, exchange records, merchant data, and network observation can connect activity to people. Wallet practices and collaborative transactions can frustrate some heuristics, but the base ledger is not private by default.

This is why Monero and the Lightning Network change different parts of the comparison. Monero changes what the ledger reveals by default. Lightning normally keeps individual channel updates off the global ledger, while introducing routing, liquidity, online monitoring, and custody tradeoffs of its own.

Best-fit boundary

Bitcoin L1 is strongest when the priority is permissionless bearer settlement, predictable issuance, and resistance to unilateral transaction censorship or monetary control. It is a weaker fit for low-value interactive payments, stable unit-of-account pricing, default transaction privacy, or general application execution. Those are not implementation defects alone; they reflect the base layer’s chosen tradeoffs.

  1. Bitcoin Developer Guide, “Block Chain” and “Transactions”. Project documentation describing the protocol as designed, unsnapshotted and subject to revision. ↩

Built on 3 sources (3 external).

Working out connections…