Distributed Ledgers | Blockchain & Networks

A distributed ledger is a shared record maintained across multiple computers or organisations. Blockchains are one important form of distributed ledger technology, but the broader concept is simply that the authoritative record is replicated and reconciled across participants rather than held by one central database operator.

Learning goal: Understand the mechanism well enough to interpret crypto transactions, network activity and trading-related operational risk without treating the blockchain as a black box.

The central idea

In a conventional centralised system, a trusted organisation typically owns the authoritative database. In a distributed ledger, multiple participants hold and update copies under agreed rules. The system needs mechanisms for agreeing which updates are valid and in what order they occurred.

Distributed does not automatically mean decentralised

Important distinction: A ledger can be technically distributed across many servers while operational control remains concentrated. Decentralisation is a spectrum involving validator concentration, governance, infrastructure, software development, custody and economic power.

Question	Why it matters
Who can validate?	Permissionless participation usually reduces reliance on a closed operator set.
Who can change rules?	Governance concentration can matter even if many nodes exist.
Where are nodes hosted?	Heavy reliance on a few cloud providers can create infrastructure concentration.

Replication and verification

Nodes do not merely store identical files. They apply deterministic rules to transactions and state transitions. If participants independently verify the same valid sequence of updates, they can converge on a shared state.

Replication

Multiple participants hold copies of ledger data.

Validation

Rules determine which updates are acceptable.

Consensus

The network coordinates around a canonical ordering or state.

Why this matters for crypto trading

The ledger is ultimately where ownership and settlement are recorded for native on-chain assets. Exchanges may show internal balances that move instantly inside their own database, while withdrawals and deposits interact with the external distributed ledger.

An exchange trade can settle internally without an immediate blockchain transaction.
A withdrawal creates an on-chain transaction and inherits network conditions.
Self-custody ownership depends on the ledger and valid cryptographic control, not on an exchange account statement.

Trade-offs

Distributed verification can improve resilience and reduce reliance on one operator, but it can introduce coordination costs. Networks must balance throughput, latency, decentralisation, security, storage and governance. There is no single architecture that maximises every property simultaneously.

Knowledge check

What is the core function described in this lesson?
Which part of the process can create delays or uncertainty for a trader?
What information would you verify before sending or acting on a transaction?

Common questions

Is every blockchain a distributed ledger?

Generally yes: blockchain is a ledger design in which data is linked in blocks. But not every distributed ledger necessarily uses a blockchain structure.

Does “distributed” mean data can never be changed?

No. Immutability is an emergent property of protocol design, consensus, economic security and history. Networks can reorganise, upgrade or in extreme cases coordinate changes.

Why do exchanges still use central databases?

Centralised exchanges need fast order matching and account updates. Recording every internal trade directly on a public chain would often be slower, more expensive and operationally impractical.

Summary

Key idea: distributed ledgers replicate and verify a shared record across participants. For traders, the distinction between an exchange’s internal ledger and the public blockchain is critical when thinking about settlement, custody and transfer risk.