Blockchain

What Is a Blockchain?

A blockchain is a distributed, append-only data structure that records transactions in sequential groups called blocks. Each block is cryptographically linked to the one before it, creating an immutable chain of records. Once data is written to a blockchain, altering it requires recomputing every subsequent block: a task that is computationally infeasible on a well-secured network.

The concept was first implemented by Satoshi Nakamoto in 2009 with the launch of Bitcoin. The genesis block embedded the headline "Chancellor on brink of second bailout for banks" from The Times, serving both as a timestamp and a statement about the financial system that motivated Bitcoin's creation. Since then, blockchain technology has expanded well beyond digital currencies into supply chain management, decentralized finance, and identity systems.

At its core, a blockchain solves the double-spend problem without requiring a trusted intermediary. Instead of a bank verifying that you haven't spent the same money twice, the network's participants collectively validate and record every transaction, making the ledger transparent and verifiable by anyone.

How It Works

A blockchain operates through three interlocking mechanisms: block construction, cryptographic linking, and distributed consensus. Together, these ensure that the ledger remains consistent across thousands of independent nodes without any central coordinator.

Block Structure

Every block consists of two parts: a header and a body. The header is an 80-byte summary (on Bitcoin) containing metadata, while the body holds the actual transaction data.

The header includes six fields:

• Version number: indicates which protocol rules the block follows
• Previous block hash: the SHA-256 hash of the prior block's header, creating the chain link
• Merkle root: a single hash that cryptographically commits to every transaction in the block
• Timestamp: when the miner assembled the block
• Difficulty target: the threshold the block's hash must fall below to be considered valid
• Nonce: a counter that miners increment to search for a valid hash

The body contains a list of transactions organized into a Merkle tree. This tree structure allows anyone to efficiently verify that a specific transaction is included in the block without downloading every transaction: a property that SPV clients rely on.

Cryptographic Linking

Each block stores the hash of the previous block's header. This creates a chain where every block is connected to its predecessor, all the way back to the genesis block. The linking mechanism is what makes blockchains tamper-evident:

1. A block's hash is computed from its header contents, which include the previous block hash
2. If an attacker modifies a transaction in block N, the Merkle root changes
3. The changed Merkle root produces a different block hash for block N
4. Block N+1 still references the original hash of block N, creating a mismatch
5. The attacker must now recompute block N+1, then N+2, and every subsequent block

On Bitcoin, this means an attacker would need to redo the Proof of Work for every block after the tampered one, while also outpacing the honest network that continues adding new blocks. This is why deeper confirmations provide stronger settlement assurance.

Simplified Block Diagram

Block N-1                Block N                  Block N+1
┌──────────────────┐   ┌──────────────────┐   ┌──────────────────┐
│ Header           │   │ Header           │   │ Header           │
│  prev_hash: ...  │◄──│  prev_hash: H(N-1)│◄──│  prev_hash: H(N) │
│  merkle_root     │   │  merkle_root     │   │  merkle_root     │
│  timestamp       │   │  timestamp       │   │  timestamp       │
│  nonce           │   │  nonce           │   │  nonce           │
├──────────────────┤   ├──────────────────┤   ├──────────────────┤
│ Transactions     │   │ Transactions     │   │ Transactions     │
│  tx0 (coinbase)  │   │  tx0 (coinbase)  │   │  tx0 (coinbase)  │
│  tx1             │   │  tx1             │   │  tx1             │
│  tx2             │   │  tx2             │   │  tx2             │
│  ...             │   │  ...             │   │  ...             │
└──────────────────┘   └──────────────────┘   └──────────────────┘

Consensus Mechanisms

A blockchain is only as trustworthy as the mechanism that determines which blocks get added to it. Without a central authority, the network needs a set of rules for participants to agree on the canonical chain. These rules are called consensus mechanisms.

Proof of Work

Proof of Work (PoW) requires miners to expend computational energy finding a nonce that produces a block hash below the network's difficulty target. Bitcoin uses PoW with the SHA-256 algorithm, targeting an average block time of 10 minutes. The difficulty adjustment recalibrates every 2,016 blocks (roughly two weeks) to maintain this cadence regardless of how much hashrate joins or leaves the network.

PoW's security comes from the real-world cost of energy: to rewrite the chain, an attacker must outspend all honest miners combined. This makes 51% attacks prohibitively expensive on large networks like Bitcoin, where the cumulative hashrate represents billions of dollars in hardware and electricity.

Proof of Stake

Proof of Stake (PoS) replaces energy expenditure with economic collateral. Validators lock up (stake) cryptocurrency as a bond, and the protocol selects validators to propose and attest to new blocks. Misbehaving validators risk having their stake slashed.

Ethereum transitioned from PoW to PoS in September 2022 during an upgrade known as "The Merge," reducing its energy consumption by approximately 99.95%. PoS enables faster finality than PoW: Ethereum achieves finality in about 13 minutes (two epochs) compared to Bitcoin's probabilistic finality that strengthens with each additional confirmation.

Public vs. Private Blockchains

Not all blockchains operate the same way. The distinction between public and private blockchains comes down to who can participate in the network and who can validate transactions.

Public blockchains like Bitcoin prioritize censorship resistance and open participation. Anyone can run a node, validate transactions, and verify the entire history independently. This openness is core to Bitcoin's value proposition as a trustless monetary network.

Private or permissioned blockchains like Hyperledger Fabric and R3 Corda sacrifice decentralization for performance and privacy. Participation requires authorization from a governing entity, and transaction data is often visible only to involved parties. These platforms are used in enterprise settings such as supply chain tracking and interbank settlement.

The Blockchain Trilemma

The blockchain trilemma, a concept popularized by Vitalik Buterin, describes the tradeoff among three desirable properties:

• Decentralization: distributing control across many independent participants
• Security: resistance to attacks and censorship
• Scalability: the ability to handle high transaction throughput

Optimizing for any two properties tends to compromise the third. Bitcoin prioritizes decentralization and security through its PoW mechanism and conservative block size limit, but processes only about 7 transactions per second on the base layer. Networks that increase throughput by raising block sizes or reducing validator requirements often sacrifice decentralization (fewer nodes can keep up) or security (smaller validator sets are easier to attack).

This trilemma is a primary driver behind Layer 2 solutions. Rather than compromising the base layer, protocols like the Lightning Network and Spark move transactions off-chain while inheriting the security guarantees of the underlying blockchain. This allows Bitcoin to remain maximally decentralized and secure at Layer 1 while achieving higher throughput at Layer 2.

Use Cases

Digital Currency and Payments

The original and most prominent use case. Bitcoin demonstrated that a blockchain can function as a peer-to-peer electronic cash system without intermediaries. Today, blockchain-based payment rails are being used for cross-border payments, micropayments, and instant settlement that traditional banking infrastructure cannot match.

Decentralized Finance

Decentralized applications built on blockchains like Ethereum enable lending, borrowing, and trading without traditional financial intermediaries. Smart contracts encode the rules of financial agreements directly in code, making them self-executing and transparent. The total value locked in DeFi protocols demonstrates the scale of this ecosystem.

Stablecoins

Blockchains serve as the settlement layer for fiat-backed stablecoins like USDC and USDT, which maintain a 1:1 peg with the US dollar. These tokens combine the programmability and global accessibility of blockchain with the price stability of traditional currency. Bitcoin-native stablecoins like USDB extend this capability to the Bitcoin ecosystem through Layer 2 protocols.

Supply Chain and Provenance

Permissioned blockchains track goods through supply chains, providing an auditable trail from manufacturer to consumer. Each step in the chain is recorded as a transaction, making it difficult to introduce counterfeit goods or falsify origin records. Industries including pharmaceuticals, food safety, and luxury goods use blockchain-based tracking systems.

Why It Matters for Bitcoin Layer 2

Understanding blockchain fundamentals is essential for understanding why Layer 2 protocols exist. Bitcoin's base-layer blockchain is intentionally constrained: its block size limit and 10-minute block time prioritize decentralization and security over throughput. This design choice means the base chain can process roughly 7 transactions per second.

Layer 2 solutions address this by processing transactions off the main blockchain while periodically anchoring state back to it. The Lightning Network uses payment channels, while Spark uses a statechain-based architecture with FROST threshold signatures. Both inherit Bitcoin's security guarantees because users can always fall back to the base-layer blockchain to enforce their claims.

Risks and Considerations

Scalability Constraints

Public blockchains face inherent throughput limitations. Every full node must process and store every transaction, which bounds the network's capacity by the capabilities of individual participants. Increasing block sizes or block frequency raises hardware requirements, potentially centralizing the network as fewer participants can afford to run nodes.

Energy Consumption

Proof of Work blockchains consume significant energy. Bitcoin's mining network uses electricity comparable to that of a mid-sized country. While proponents argue that this energy expenditure secures trillions of dollars in value and increasingly draws on renewable sources, the environmental impact remains a point of debate.

Immutability Cuts Both Ways

The same property that prevents tampering also means mistakes are permanent. A transaction sent to the wrong address or a smart contract with a bug cannot be reversed without network-wide coordination (a hard fork). This places a higher burden on users to verify actions before executing them.

51% Attacks on Smaller Networks

While 51% attacks are economically infeasible against Bitcoin, smaller blockchains with less hashrate or fewer validators are vulnerable. An attacker who controls the majority of a network's consensus power can double-spend transactions or censor specific participants. Several smaller PoW chains have experienced successful 51% attacks in practice.

Regulatory Uncertainty

Blockchain technology operates across jurisdictions with varying and evolving regulatory frameworks. Laws around digital assets, privacy (the right to be forgotten vs. immutability), and cross-border transactions continue to develop. Frameworks like the EU's MiCA regulation and the U.S. GENIUS Act are beginning to provide clearer guidelines, particularly for stablecoins issued on blockchain networks.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.