Public, Private and Consortium Blockchains
Not every blockchain is a wild, open frontier where anyone can join. Some blockchains are like public parks, open to all; others are like private clubs with a guest list. In this lesson, we'll explore the spectrum from public to private to consortium blockchains. You'll learn how they differ in openness, speed, and control, and how to choose the right one for a given scenario. By the end, you'll be able to match real-world needs to the appropriate network type.
In this lesson
- Distinguish public, private, and consortium blockchains
- Explain trade-offs between openness, speed, and control
- Match a scenario to the network type that fits it best
The Blockchain Spectrum: From Open to Permissioned
Imagine three different ways to organize a community garden:
- Public garden: Anyone can walk in, plant seeds, and harvest. There's no gatekeeper, but it can get crowded and messy.
- Private garden: Owned by a single family. Only they can plant and harvest. It's tidy and fast, but not open to outsiders.
- Community garden: A group of neighbors share ownership and decide together who can join and what to plant. It's more controlled than a public garden but more open than a private one.
Blockchains work similarly. The three main types are public, private, and consortium. Each balances openness, speed, and control differently.
Public Blockchains: Open to All
A public blockchain is permissionless: anyone can join, read the ledger, submit transactions, and even participate in consensus (e.g., mining or staking). There's no central authority. Examples include Bitcoin, Ethereum, and Solana.
Key traits:
- Open access: No one can be denied participation.
- Decentralized: Thousands of nodes worldwide maintain the ledger.
- Transparent: All transactions are visible on the blockchain explorer.
- Censorship-resistant: No single entity can block transactions.
Trade-offs:
- Slower and more expensive: Consensus requires broad agreement, which takes time and energy (or capital).
- Less privacy: Transactions are pseudonymous but public.
- Governance challenges: Upgrades require community consensus, which can be slow.
Example · Real-World Example: Bitcoin
Bitcoin is the quintessential public blockchain. Anyone with an internet connection can download the Bitcoin software, become a node, and start validating transactions. Miners compete to add new blocks using proof-of-work. There's no company or government controlling it. This openness is why Bitcoin is often called censorship-resistant money—no one can stop you from sending BTC to anyone else, as long as you pay the network fee.
Private Blockchains: Controlled and Fast
A private blockchain is permissioned: a single organization controls who can join, read, and write. It's essentially a distributed database with cryptographic guarantees, but without the open, decentralized ethos of public chains.
Key traits:
- Restricted access: Only invited participants can join.
- Centralized control: One entity decides the rules and can change them.
- High throughput: Fewer nodes mean faster consensus (often using algorithms like PBFT or Raft).
- Privacy: Transactions are only visible to authorized parties.
Trade-offs:
- Less decentralized: Trust is placed in the controlling organization.
- Limited transparency: Not open to public audit.
- Potential for censorship: The operator can block transactions.
Private blockchains are often used inside enterprises for supply chain tracking, internal record-keeping, or consortium databases where all parties trust the operator.
Example · Real-World Example: Hyperledger Fabric in Supply Chains
Walmart and IBM used Hyperledger Fabric, a private blockchain framework, to track food products from farm to shelf. Only Walmart, its suppliers, and regulators can access the ledger. This speeds up traceability (from days to seconds) and keeps sensitive data private. But it's not open to the public—you can't just join and start validating.
Consortium Blockchains: Shared Control
A consortium blockchain is a hybrid: a group of organizations jointly govern the network. It's permissioned (you need an invite), but no single entity has full control. Consensus is typically achieved by a set of trusted validators chosen by the consortium.
Key traits:
- Multi-party governance: Decisions are made by a consortium of members.
- Permissioned access: Participants are known and vetted.
- Better scalability than public chains: Fewer validators, faster finality.
- Shared trust: No single point of control, but not fully open either.
Trade-offs:
- Complex governance: Getting multiple organizations to agree can be slow.
- Partial decentralization: More decentralized than private, less than public.
- Limited public verifiability: Often not open to public audit.
Consortium blockchains are popular in banking, trade finance, and healthcare, where multiple institutions need to share data without a central authority.
Example · Real-World Example: R3 Corda in Banking
R3 Corda is a consortium blockchain platform used by a network of banks for trade finance and payments. Each bank runs a node, and transactions are validated by the parties involved and a notary service. No single bank controls the network, but it's not open to the public. This balances privacy, speed, and shared trust.
| Feature | Public | Private | Consortium |
|---|---|---|---|
| Access | Anyone | Single org | Invited orgs |
| Decentralization | High | Low | Medium |
| Speed | Slow | Fast | Fast |
| Privacy | Low | High | Medium-High |
| Governance | Community | Central | Consortium |
| Examples | Bitcoin, Ethereum | Hyperledger Fabric (internal) | R3 Corda, Quorum |
Trade-offs: Openness vs. Speed vs. Control
Choosing a blockchain type is a balancing act. Here's a simple way to think about it:
- Openness: Public chains are open to all, private chains are closed, consortium chains are partially open.
- Speed: Private and consortium chains are faster because they have fewer validators and don't need global consensus.
- Control: Private chains give one org full control; consortium chains share control; public chains have no central control.
There's no free lunch. More openness usually means slower speed and less privacy. More control means faster speed but less decentralization. The right choice depends on your use case.
Decentralization vs. Control
As control by a single entity increases, decentralization decreases. Public chains have low control and high decentralization; private chains have high control and low decentralization.
- Anyone can join
- Slow, energy-intensive consensus
- Transparent to all
- Censorship-resistant
- Example: Bitcoin
- Only invited participants
- Fast, lightweight consensus
- Private to participants
- Operator can censor
- Example: Internal Hyperledger Fabric
How to Choose: Matching Scenario to Network Type
Use these questions to pick the right type:
- Who needs to access the data? If the public must verify, choose public. If only a few parties, consider private or consortium.
- How much trust do participants share? If there's a trusted central party, private works. If multiple orgs need shared control, consortium.
- What are the speed and cost requirements? High throughput and low latency favor private/consortium.
- Is censorship resistance critical? If yes, public is the only option.
- Do you need regulatory compliance? Private/consortium allow known participants, which can simplify compliance.
For example, a central bank digital currency (CBDC) might use a private or consortium chain for control and speed. A decentralized finance (DeFi) app would use a public chain for open access.
Compare Consensus in Public vs Private Chains
In this demo, you'll simulate consensus in a public chain (proof-of-work) and a private chain (PBFT). See how the number of participants affects speed and finality.
Is a private blockchain still a blockchain?
<p>Yes, if it uses cryptographic linking of blocks and a distributed ledger. However, it sacrifices some core blockchain properties like decentralization and censorship resistance. Some purists argue it's more accurately called a 'distributed ledger technology' (DLT).</p>
Can a public blockchain become private?
<p>Not really. Public blockchains are defined by their open, permissionless nature. You could fork the code to create a private version, but the original network remains public.</p>
Which type is best for supply chain tracking?
<p>Consortium blockchains are often ideal because multiple companies (suppliers, manufacturers, retailers) need to share data without a single point of control. Private chains can work if one company dominates the supply chain.</p>
Are private blockchains more secure?
<p>Not necessarily. They are less exposed to 51% attacks because validators are known, but they have a single point of failure (the controlling organization). Public chains are more resilient to censorship but can suffer from other attacks.</p>
What is a permissioned blockchain?
<p>A permissioned blockchain restricts who can participate in the network. Both private and consortium blockchains are permissioned. Public blockchains are permissionless.</p>
Check your understanding
Practice · server-graded