In short
- Blockchains order and replicate validated state transitions.
- Authorization, execution, ordering and consensus are distinct stages.
- Hash links provide tamper evidence; consensus provides accepted history.
- A blockchain does not guarantee off-chain truth, flawless code, privacy or permanence under every assumption.
After this lesson you can
- Trace a transaction from signature through validation and block inclusion
- Explain the separate roles of execution, consensus and data availability
- Identify what blockchain replication solves and what it does not
A replicated state machine
A blockchain is an ordered data structure used by a distributed network to agree on state transitions. A user signs a transaction; nodes check it against protocol rules; a block producer proposes an ordering; the consensus process lets participants choose the accepted history. Cryptographic links make later alteration detectable, while economic and network rules determine which chain participants follow. A blockchain coordinates agreement among parties; it does not make input data true or software bug-free.
Key point: Separate transaction authorization, execution validity, ordering, consensus and finality.
Follow one transaction
Trace a transfer without using the vague phrase the blockchain processes it.
- A wallet constructs and signs a transaction with the relevant key.
- Nodes verify signature, balance or state rules and propagate valid candidates.
- A proposer orders transactions into a candidate block.
- Consensus selects accepted history; confirmations or finality increase settlement confidence.
What replication changes
| Can help with | Does not guarantee | |
|---|---|---|
| Shared history | Participants verify common state | Truth of off-chain inputs |
| Tamper evidence | Changes conflict with later hashes and consensus | No vulnerabilities in contract code |
| Fault tolerance | No single database operator is required | Unlimited throughput or zero cost |
| Auditability | Rules and state may be independently checked | Privacy by default |
Common trap: calling data immutable
Practical finality is a property of consensus, network assumptions and elapsed confirmations, not a magical property of hashing alone. Protocols can reorganize recent blocks, upgrade rules or split communities. Data can also be correct according to protocol while representing a fraudulent off-chain claim. Immutable should be replaced with the precise question: what would it cost or require to alter accepted history?
Practise what you just read
Take this lesson's quiz and review cards in the app, then try the idea with virtual money in paper trading. Free account, no card.
Education only, not investment advice. Examples are illustrative. Read the full disclaimer