Bitcoin runs on a blockchain. A blockchain is one specific way of building a distributed ledger technology (DLT) system, but not the only one, and not always the right one. This guide explains what a distributed ledger actually is, how it differs from a blockchain, and how to think about whether your project needs a public blockchain, a permissioned DLT, or neither.
What Is a Distributed Ledger?
Picture a village with one bookkeeper who tracks everyone's debts in a single notebook. That notebook is a centralized ledger: convenient, but a single point of failure: if the bookkeeper makes a mistake, gets bribed, or loses the notebook, everyone's records are compromised.
Now picture the same village, except the bookkeeper reads out every new entry to several neighbors, who each keep their own copy and cross-check it each morning. Altering one notebook no longer works, because the other copies disagree with it. That's the basic idea behind a distributed ledger: the same data, replicated across independent participants, who together decide what counts as the current, agreed-upon state.
How Distributed Ledgers Work
A DLT protocol lets a network of computers agree on a shared, append-only record without a central authority. Removing that central authority is the point: no single operator can rewrite history unnoticed, and the data stays available even if some participants go offline or turn malicious. What actually keeps everyone in sync is a consensus mechanism: a rule for how the network agrees on the next valid entry, and disagreement between mechanisms is what actually separates most DLT platforms from one another.
Public chains mostly rely on proof of work (miners compete to solve a puzzle, at a real energy cost) or proof of stake (validators lock up capital and lose it if they misbehave). Permissioned DLT frameworks more often use a Byzantine fault-tolerant protocol, where a known set of validators votes directly on each entry. It is faster and cheaper than PoW or PoS, but it only works because the validators are identifiable and can be held accountable, which is exactly the tradeoff a permissioned network makes.
Public Blockchain vs. Permissioned DLT
“DLT” and “blockchain” get used interchangeably, but the distinction matters once you're picking a platform. A public blockchain like Ethereum or Solana is permissionless: anyone can run a node, read the ledger and, depending on the network, help validate it. A permissioned DLT restricts who can run a node or see specific data, the tradeoff enterprises make deliberately when the participants are known counterparties (banks, insurers, a supply chain consortium) rather than an anonymous public.
If your project is consumer-facing, needs no gatekeeping, and benefits from an existing user base and liquidity, a public chain is usually the right starting point. See our guide to choosing the right blockchain for a dApp. If your counterparties are known, regulated, and need confidentiality between specific parties on the same network, a permissioned DLT framework is usually the better fit; our roundup of permissioned blockchain frameworks and our case study on why we chose Corda for one client project go into that side of the decision in depth.
Distributed Ledger vs. Blockchain: The Real Difference
A blockchain is a distributed ledger, but not every distributed ledger is a blockchain. The differences that matter in practice:
DLT in Production, Not Just in Theory
Distributed ledgers have moved well past the pilot stage. Central banks now run live wholesale experiments on shared ledgers: the Bank for International Settlements' Project Mariana tested automated cross-border settlement of wholesale central bank digital currencies between the central banks of France, Singapore and Switzerland on a DLT-based platform. Several national and commercial banks now run production or pilot central bank digital currency projects on permissioned ledgers, and regulated markets increasingly use DLT for post-trade settlement and repo transactions. None of this looked like Bitcoin; most of it never had a public token at all.
Where DLT Shows Up Today
- Payments and settlement. Public blockchains move value peer-to-peer without a bank in the middle; permissioned DLT increasingly settles interbank and wholesale transactions where counterparties are known.
- Smart contracts. Conditions written into code execute automatically: a shipment confirmation releases a payment, a maturity date triggers a bond redemption.
- Provenance and anti-counterfeiting. Once an origin record is on a DLT, it can't be rewritten later without detection, which is why the model shows up in supply-chain, luxury-goods and pharmaceutical tracking pilots.
- Records and credentials. Diplomas, certificates and identity documents stored on a ledger can be verified directly, without contacting the issuing institution each time.
- Tokenization. Real-world assets (bonds, funds, real estate, gold) get represented as on-chain tokens, which is its own fast-growing use case; see our guide to real-world asset tokenization.
Four Questions That Narrow the Field
Before you compare specific platforms, answer these, because they decide which half of the DLT market you're even shopping in:
- Who are the participants? A known, finite set of organizations points to permissioned DLT. An open, growing, anonymous user base points to a public blockchain.
- What has to stay private? Public chains make transaction data visible to everyone by default. If counterparties need to see only their own deals, that's a permissioned-network requirement, not a public-chain one.
- Does a native token help or hurt? A token is useful for aligning incentives among strangers. It's often a liability for a regulated enterprise consortium, which is one reason most permissioned frameworks skip it entirely.
- Who has to certify or audit the system? Regulators and auditors increasingly have opinions on both models, but permissioned DLT is easier to map onto existing compliance and data-residency rules because you control who runs a node.
How to Make the Right Choice
Start from the problem, not the technology. If you need an open network, a native token, and permissionless participation, you're choosing a public blockchain, and the decision becomes which one. See our blockchain selection guide for that comparison. If you need shared, tamper-evident records among a known set of counterparties, with privacy between them and no public token, you're choosing a permissioned DLT framework, and the decision becomes which one fits your industry, language and compliance requirements.
4IRE has built on both sides of that line since 2010, from public-chain DeFi products to permissioned Corda deployments for regulated clients. Our blockchain consulting team can help you work out which model actually fits your project before you commit engineering time to either one.
Conclusion
Distributed ledger technology is the umbrella; blockchain is one implementation of it, and a fairly specific one. The right question isn't “blockchain or not” but whether your project needs an open, permissionless network or a controlled, permissioned one, and that answer should come from your counterparties and your regulatory requirements, not from which technology is trending.
FAQ
Yes. Blockchain is a specific type of distributed ledger that groups entries into cryptographically linked blocks. Not every distributed ledger uses that block structure (some use a directed acyclic graph or another data structure entirely), so the two terms aren't interchangeable, even though blockchain is the most familiar example.
No. Public blockchains typically need a native token to pay for transactions and reward validators, but permissioned DLT frameworks built for enterprises (Hyperledger Fabric, Corda) run without any cryptocurrency at all. The token is a feature of the permissionless model, not of distributed ledgers in general.
Start with who your participants are. If anyone should be able to join and transact without permission, use a public blockchain. If your participants are known, regulated counterparties who need privacy from outsiders and from each other, a permissioned DLT framework is usually the better fit.