Skip to content
Glossary

Distributed Ledger

A distributed ledger is a record of data — such as transactions — that is shared and kept in sync across many independent computers, instead of living in a single central database.

How it works

Each participant holds a copy of the ledger, and a consensus process keeps every copy consistent as new entries are added. A blockchain is the best-known type of distributed ledger, organising data into a chain of cryptographically linked blocks, but other structures exist too. The defining feature is that no single party controls the master copy.

Why it matters

Distributing the ledger removes the single point of failure and control found in traditional databases, making records harder to tamper with or censor. This is the core idea that makes cryptocurrencies and many enterprise blockchain projects possible.

Example

Every full node on a network like Bitcoin keeps its own copy of the distributed ledger and checks new transactions against it.

Distributed Ledger: Frequently Asked Questions

How is a distributed ledger different from a normal database?
A traditional database lives in one central place controlled by a single party. A distributed ledger instead gives every participant a copy, and a consensus process keeps all copies in sync as new entries are added. Because no one holds the master copy, records are harder to tamper with or censor, removing the single point of failure and control.
Is a blockchain the same as a distributed ledger?
A blockchain is the best-known type of distributed ledger, but they are not identical. A blockchain organizes data into a chain of cryptographically linked blocks. Other distributed ledgers use different structures. What they all share is the defining feature: the ledger is replicated across many independent computers and no single party controls the master copy.
Why does distributing the ledger make records more secure?
Because every participant holds and checks their own copy, altering the record would require changing it across the network rather than editing one central file. New entries must pass a consensus process before being accepted. This removes the single point of failure found in central databases and makes the history far harder to tamper with or quietly censor.