Unit
- Distributed ledger: A distributed ledger is a database shared across multiple network participants, each holding an identical copy. Unlike centralized databases, no single party has exclusive control, and updates require consensus among honest nodes. This structure eliminates single points of failure and supports transparency.
- Historical development: Distributed ledgers have roots in peer-to-peer file sharing, but Bitcoin demonstrated how to solve double-spending without a central authority. The innovation combined cryptography, networking, and game theory to create a resilient system.
- Core properties: Ledgers record transactions in chronological order, and each participant can verify the history independently. Cryptographic links between records make retroactive changes detectable, ensuring that tampering is obvious to all.
- Trust model: Traditional ledgers rely on trusted intermediaries such as banks or clearinghouses. Distributed ledgers replace that trust with algorithmic verification and economic incentives, allowing strangers to cooperate.
- Use cases: Beyond cryptocurrency, distributed ledgers track supply chains, manage digital identities, record land titles, and enable transparent voting systems across industries.
- Terminology: The terms blockchain, distributed ledger technology, and shared ledger are sometimes used interchangeably, but blockchain is a specific type of DLT with blocks and chains.
- Consensus necessity: Because participants may not trust each other, the system needs a mechanism to agree on the true state. Consensus protocols provide this agreement under specified assumptions about network participants.
- Node roles: Nodes validate, store, and propagate transactions. Full nodes keep the entire history, while light nodes store only headers for efficiency, balancing resource usage and security.
- Immutability: Hash chaining makes historical records practically immutable without breaking the chain. Recomputing every subsequent hash and coordinating that change across many nodes is computationally expensive. This design discourages retroactive editing and provides a clear audit trail for regulators, auditors, and business stakeholders who need verifiable records.
- Permission models: Distributed ledgers can be permissionless, meaning anyone can join and validate, or permissioned, where known organizations control access. Permissioned networks often use identity-based consensus and faster finality, while permissionless networks prioritize openness and decentralization. The choice depends on industry requirements, trust assumptions, and compliance obligations.
- Smart contracts: Programmable logic on a distributed ledger automatically executes agreed actions when specified conditions are met. These contracts reduce manual processing and lower operational costs by enforcing agreements in code rather than through intermediaries. However, they require careful design and auditing, because deployed code cannot be changed easily if errors or vulnerabilities are discovered.
- Scalability and performance: Replicating every transaction across all nodes creates significant storage, bandwidth, and latency demands. Many distributed ledgers use sharding, off-chain computation, or layer-two techniques to increase throughput. Without these enhancements, public networks can only process a limited number of transactions per second, which may be insufficient for global payment systems.
System Architecture
Pattern: Distributed Ledger Architecture
Components:
- Ledger database: Append-only store replicated across nodes.
- Consensus engine: Validates and orders transactions.
- P2P network: Enables node communication.
- Cryptographic layer: Signs and verifies data.
Code Example
Python
import hashlib
def compute_hash(data):
encoded = data.encode('utf-8')
return hashlib.sha256(encoded).hexdigest()
transaction = 'Alice:Bob:25'
print(compute_hash(transaction))This function demonstrates how a simple distributed ledger hashes transaction data. The SHA-256 algorithm produces a fixed-size fingerprint. Any change to the input produces a completely different hash, which makes tampering evident. In a real blockchain, each block contains the hash of the previous block, creating an immutable chain.
Quick Revision
- A distributed ledger is a shared database with no central authority.
- Blockchain is a specialized DLT with blocks and cryptographic hashes.
- Consensus protocols enable agreement among untrusted nodes.
- Full nodes store entire history; light nodes store headers.