Beginner-Friendly Topic
Take your time - it's perfectly normal to re-read this topic 2-3 times. Try the interactive code editor below to run code yourself. Use the Q&A section to check your understanding before moving on. You've got this! 🚀
Blockchain Taxonomy � Public, Private, Consortium
Blockchains are not one-size-fits-all. The landscape spans from fully open permissionless networks (anyone joins, anyone validates) to fully closed enterprise networks (vetted participants, known validators). Understanding the taxonomy helps choose the right architecture.
The Three Categories
- Public (Permissionless): Anyone can read the chain, submit transactions, and participate in consensus. No identity required. Examples: Bitcoin, Ethereum, Litecoin. Full transparency and censorship resistance, but lower throughput and public data
- Private (Permissioned): Only invited/approved entities participate. A single organization controls node membership and consensus. Examples: Hyperledger Fabric (single-org deployment), Quorum. Highest privacy, lowest decentralization � essentially a replicated database with cryptographic audit trail
- Consortium (Federated): A group of pre-selected organizations jointly operate the network. Semi-decentralized � no single organization controls it, but membership is restricted. Examples: R3 Corda (banking), Hyperledger Besu (multi-org enterprise), IBM Food Trust
- Hybrid: Some public blockchains have private layers. Some private chains anchor to public chains for auditability. A company might record data hashes on Bitcoin while keeping the actual data private
Architecture Comparison
# Blockchain type comparison matrix
BLOCKCHAIN_TYPES = {
"Public (Bitcoin)": {
"read_access": "Anyone",
"write_access": "Anyone",
"validator_set": "Open (15,000+ nodes)",
"identity_required": False,
"throughput_tps": 7,
"finality": "Probabilistic (~60 min)",
"transaction_cost": "Market-driven (variable)",
"data_privacy": "None (all public)",
"governance": "Decentralized (BIP process)",
"use_cases": "Digital gold, censorship-resistant money",
},
"Consortium (Hyperledger)": {
"read_access": "Members only",
"write_access": "Approved members",
"validator_set": "Known orgs (5-50 peers)",
"identity_required": True,
"throughput_tps": 10000,
"finality": "Deterministic (seconds)",
"transaction_cost": "Near zero",
"data_privacy": "Configurable (channels)",
"governance": "Member consortium",
"use_cases": "Supply chain, interbank, healthcare records",
},
"Private (Enterprise)": {
"read_access": "Organization only",
"write_access": "Organization only",
"validator_set": "Internal (2-20 nodes)",
"identity_required": True,
"throughput_tps": 100000,
"finality": "Immediate",
"transaction_cost": "Zero",
"data_privacy": "Full",
"governance": "Single organization",
"use_cases": "Internal audit trail, regulated financial records",
},
}
print(f"{'Property':>22} | {'Public':>25} | {'Consortium':>25} | {'Private':>20}")
print("=" * 100)
properties = list(list(BLOCKCHAIN_TYPES.values())[0].keys())
for prop in properties:
vals = [str(bt[prop]) for bt in BLOCKCHAIN_TYPES.values()]
print(f"{prop:>22} | {vals[0]:>25} | {vals[1]:>25} | {vals[2]:>20}")Common Mistakes
- Calling private blockchains 'more scalable blockchains' � private blockchains sacrifice decentralization and censorship resistance to achieve throughput. A private blockchain with one trusted operator is functionally just a database with cryptographic logs
- Assuming consortium blockchains avoid all trust � consortium blockchains distribute trust among members, but you still trust the member set. If 2/3 of members collude, they can manipulate the chain
Tip
Tip
Practice Blockchain Taxonomy Public Private Consortium in small, isolated examples before integrating into larger projects. Breaking concepts into small experiments builds genuine understanding faster than reading alone.
Each block references the previous block's hash, forming an immutable chain
Practice Task
Note
Practice Task - (1) Write a working example of Blockchain Taxonomy Public Private Consortium from scratch without looking at notes. (2) Modify it to handle an edge case (empty input, null value, or error state). (3) Share your solution in the Priygop community for feedback.
Quick Quiz
Common Mistake
Warning
A common mistake with Blockchain Taxonomy Public Private Consortium is skipping edge case testing - empty inputs, null values, and unexpected data types. Always validate boundary conditions to write robust, production-ready blockchain code.
Key Takeaways
- Blockchains are not one-size-fits-all.
- Public (Permissionless): Anyone can read the chain, submit transactions, and participate in consensus. No identity required. Examples: Bitcoin, Ethereum, Litecoin. Full transparency and censorship resistance, but lower throughput and public data
- Private (Permissioned): Only invited/approved entities participate. A single organization controls node membership and consensus. Examples: Hyperledger Fabric (single-org deployment), Quorum. Highest privacy, lowest decentralization � essentially a replicated database with cryptographic audit trail
- Consortium (Federated): A group of pre-selected organizations jointly operate the network. Semi-decentralized � no single organization controls it, but membership is restricted. Examples: R3 Corda (banking), Hyperledger Besu (multi-org enterprise), IBM Food Trust