Public and private chains
Suggest an editBitcoin is one blockchain among many. They differ in dozens of ways, but two questions capture the differences that matter most and let you place any chain you meet. First: who is allowed to run a node, validate transactions, and submit data to the chain? Second: what is the chain designed to do?
The first question: who can participate?
Every blockchain has rules about who is allowed to take part. Those rules sort chains into two broad camps.
A public blockchain lets anyone participate without permission. You can download the node software, run it on any computer, and start validating blocks. You can submit transactions without registering an identity. There is no operator who can ban you or revoke your access. Bitcoin and Ethereum are public, and so are most of the chains you'll encounter as a web3 developer.
A private blockchain, also called a permissioned one, restricts participation. Some operator controls who is allowed to run a node, who can validate, and who can submit transactions. The operator might be a company, a government, or a consortium. If you want in, you ask the operator, and the operator can refuse. Private chains are used inside companies and industry groups for shared record-keeping where the participants are known to each other but want the data structure of a blockchain.
An operator removes Bitcoin's costs together with its guarantees
Bitcoin's design started from five constraints, and all five came from having no operator, as The Bitcoin design philosophy showed. A private chain has an operator, so each constraint changes.
| Bitcoin's constraint | Without an operator | With an operator |
|---|---|---|
| Sybil resistance without identity | Adding a block costs proof of work, so fake participants cost real money | The operator admits only known members, so fake participants can't join and proof of work isn't needed |
| Public verifiability | All data is public, so any node can check it | The operator decides who sees the data, and it can stay closed to outsiders |
| Convergence despite network delay | Blocks are ten minutes apart, so each one reaches the whole network | Blocks only have to reach a few known nodes, so the chain doesn't need a ten-minute margin |
| Censorship resistance | No single party can keep a participant or a transaction out | The operator can refuse a participant or a transaction |
| Permanence | Rewriting history means redoing the proof of work | Nothing makes rewriting expensive, so the validating members can do it if they agree |
The first three rows are what a private chain gets: no energy bill, data closed to outsiders, and no need for a ten-minute gap between blocks. The last two rows are what it pays. Its members have to trust the operator not to shut them out and not to rewrite the record, and Bitcoin was designed so that nobody has to be trusted with that.
This makes private chains essentially shared databases with cryptographic auditing, run by a small group that trusts each other. What they keep over an ordinary database is the hash-linked record. Members hold their own copies, so an edit to past records shows up as a mismatch between copies.
When the operator is a group rather than a single company, the chain is called a consortium chain. Examples are banks running a shared settlement network, or a group of supply-chain participants tracking shipments together. The mechanics are the same as in any private chain, and the governance is shared.
You'll encounter two private-chain platforms in industry contexts. In Hyperledger Fabric approved participants run the validating nodes, and a separate ordering service decides transaction order in place of mining. It's used in supply chains, food traceability, and a number of inter-bank pilots. R3 Corda is built for financial institutions and goes further in closing the data: instead of every node holding the full chain, each transaction is shared only between the parties involved and the regulators who need to see it. If you end up at a bank or a large enterprise doing "blockchain," it'll usually be one of these.
The second question: what is the chain for?
Among public chains, there's a second distinction that matters more for developers than the first.
A coin chain is designed to track money. The transactions on it move value from one address to another. The chain's protocol cares about preventing double-spending, enforcing a supply schedule, and verifying signatures. Bitcoin is the canonical coin chain. Everything Bitcoin's protocol enforces is in service of "is this spend allowed, yes or no."
A smart contract is a program that lives at its own address on the chain, has its own storage, and can hold funds. You'll see the term constantly from here on. Anyone can call it by submitting a transaction that points at its address. When called, it runs whatever code its creator deployed and updates its own state accordingly. The chain enforces the contract's rules: whatever the code says happens, happens, and nobody can override that. Tokens, NFTs, decentralised exchanges, and lending markets are all smart contracts, or collections of them working together. These are the familiar things you've heard about on smart-contract chains.
A smart-contract chain is designed to run these programs. Transactions on a smart-contract chain can do more than move money. They can invoke contracts that read shared state, perform computations, conditionally move money, and write new state back. The chain's protocol cares about all the same things a coin chain cares about, plus a whole layer of execution: which contracts get called, what they're allowed to do, how much computation costs, and how the resulting state changes get committed. Ethereum is the canonical smart-contract chain, and Solana is another. Most of the public chains active today fall on this side.
The distinction matters because it determines what's possible on the chain. On Bitcoin you can build payment systems and little else, because the locking conditions on UTXOs are deliberately limited.
Take a lending market, where many people deposit coins into one pool and others borrow from the pool against collateral. Say Alice leaves 150 dollars' worth of one token as collateral and borrows 100 dollars' worth of another. The market has to remember both numbers, and when Alice repays the 100, it has to find her record, check the amount, and release her collateral. A Bitcoin locking condition has nowhere to keep such a record. It belongs to one coin, it is checked once, when that coin is spent, and it answers one question, whether this spend is allowed. A smart contract has its own storage and holds the funds itself. It can keep a record for every depositor and borrower, update it on each deposit, loan and repayment, and pay out by its own rules.
Exchanges, prediction markets, in-game economies and ownership records need the same thing, a program that keeps its own state, so they are built on smart-contract chains.
Both questions on one map
Every public chain on this map runs into the same limit when it tries to be fast, secure and open to everyone at once. The next lesson is about that limit, which is called the blockchain trilemma.