What a Blockchain Is
A ledger maintained by many parties at once, where entries are appended in batches and the ordering is agreed by a mechanism rather than by an institution.
MadStockAlerts Research · Updated August 29, 2026
What to take away
- It is a shared ledger, replicated across many independent machines.
- Entries are grouped into blocks and linked cryptographically to the previous one.
- A consensus mechanism decides which version of the ledger is authoritative.
- The design solves ordering without a central record keeper, at substantial cost.
- Nothing about the technology says anything about what any token is worth.
MAD Academy Training Video · 0:45
A Ledger Nobody Owns
A blockchain is a shared record that many parties can verify and none can quietly rewrite, and that property is the entire technical claim.
This lesson is part of a Stock Alerts + Tools plan.
The problem it addresses
Any digital record can be copied. A system representing ownership therefore needs a way to establish which record is authoritative, and the conventional solution is an institution: a bank, a registrar, a clearing house whose copy is the one that counts.
A blockchain replaces that institution with a procedure. Many participants keep a copy, a mechanism determines which additions are accepted, and each batch of entries is cryptographically linked to the one before it so that altering an old entry invalidates everything after it.
That is the whole of the technical claim: agreement on an ordering, without a party whose word settles it. Whether the problem is worth the cost of solving that way is a separate question and a contested one.
The pieces
| Component | What it does |
|---|---|
| A block | A batch of transactions, timestamped and linked to the previous block |
| A hash | A fixed-length fingerprint of data; changing the data changes the hash |
| A node | A machine holding a copy of the ledger and validating additions |
| A consensus mechanism | The rule deciding which proposed block is accepted |
| A private key | The secret that authorises a transfer from an address |
The last row is where the practical consequences for a holder concentrate, and it is the subject of the custody article. Control of the key is control of the asset, with no institution positioned to reverse a transfer.
- 1A transaction is signedWith the private key controlling the address
- 2It is broadcastTo the network of nodes holding copies of the ledger
- 3A proposer assembles a blockChosen by the consensus mechanism
- 4The block is linked to the previous oneCryptographically, so altering an old entry invalidates everything after
- 5It is finalWhich is also to say irreversible
The two main consensus approaches
| Proof of work | Proof of stake | |
|---|---|---|
| How a proposer is chosen | By expending computation to solve a puzzle | By committing tokens as collateral |
| Cost of participating | Hardware and electricity | Capital locked as stake |
| Energy consumption | Substantial, by design | Far lower |
| Penalty for misbehaviour | Wasted computation | The stake can be forfeited |
Both are mechanisms for making it expensive to propose a false history. They differ in what the expense consists of, and the energy consumption of the first is one of the most substantive criticisms directed at the sector.
What it does not establish
- That an entry is true. A ledger records what was submitted, not whether the underlying claim is accurate.
- That a token has value. The mechanism secures the record; it says nothing about what the recorded thing is worth.
- That a transaction is reversible. Finality is a design feature and there is no recourse for an error.
- That the holder is anonymous. Most public chains are pseudonymous, and the full transaction history is visible to everyone.
The second item is the one most often elided. A robust ledger and a valuable asset are unrelated propositions, and conflating them is the most common category error in the whole subject.
The trade-offs the design makes
Replacing an institution with a consensus mechanism buys specific properties and costs specific ones. Stating both is what distinguishes a description from a promotion.
| Property gained | Cost paid |
|---|---|
| No single party controls the record | Throughput far below a centralised system |
| Entries cannot be altered retroactively | Errors cannot be corrected either |
| Anyone can verify the history | Every participant stores and processes everything |
| No permission required to transact | No recourse when something goes wrong |
| Settlement is final | Finality is also irreversibility |
Each row is the same property read from two directions. Immutability and irreversibility are the same thing; permissionlessness and the absence of recourse are the same thing.
Whether the trade is worth making depends entirely on the use, which is why the technology question and the investment question are separate. A design can be well suited to a problem and say nothing about what a token is worth.