How blockchain actually works

Why it matters

The word blockchain explains almost nothing by itself. The security claim lives in the rules, the participants, the consensus process and the cost of rewriting history.

Transactions begin with signatures

A digital signature lets a participant prove authorization without publishing the private key. Nodes can verify that proof against public information before accepting a transaction as valid.

Validity is not the same as ordering. Two valid transactions may compete for the same spend or state transition, so the network also needs a shared account of what happened first.

Blocks create batches and history

Many blockchains group transactions into blocks. A block summarizes its contents and references prior state using cryptographic hashes. Change an earlier record and the later references no longer line up.

This makes the ledger tamper-evident. Resistance to actual rewriting comes from the consensus system and the distribution of participants—not from hashes operating alone.

Consensus is the coordination layer

Proof of work asks participants to expend computation and energy, then makes competing histories costly to extend. Proof of stake uses committed capital and protocol rules to choose and discipline validators. Those labels still hide important network-specific differences.

Consensus decides which valid history the network treats as authoritative. Finality may be probabilistic, economic or protocol-defined. It is better understood as a security promise with assumptions than as an absolute switch.

Immutability is a spectrum

A network can reorganize, upgrade, pause through surrounding infrastructure, or coordinate a social response. The more concentrated its validators, infrastructure or governance, the more carefully its immutability claim must be read.

The honest evaluation asks who can change state, under what conditions, at what cost and with what visibility. That framework travels better than a slogan.