A public blockchain lets anyone read the ledger, submit transactions, and take part in validation under the protocol's rules. A permissioned blockchain limits those rights to approved participants. A consortium blockchain is a permissioned network run jointly by a group of organizations, so identity checks and oversight duties are shared among known members rather than left to an open validator set.
Last updated: October 12, 2026.
What separates the three models?
The difference is who holds each right on the network. Reading data, sending transactions, and validating blocks can each be open or restricted, and the combination defines the model.
| Model | Who can transact | Who validates | Who is accountable |
|---|---|---|---|
| Public | Anyone with a wallet | An open set chosen by protocol rules | No single operator, rules set by the protocol and its community |
| Private | Users approved by one firm | Nodes run by that firm | The operating firm |
| Consortium | Users approved by members | Nodes run by member organizations | The members, under their governance agreement |
A fourth pattern sits between them: a public chain with access controls in the asset itself. The network stays open, but the token contract decides which addresses may hold or receive it.
Why do institutions look at consortium networks?
Regulated markets usually need to know who every participant is and who is responsible when something goes wrong. A consortium network builds both into the network itself. Members are onboarded through an agreed process, validators are identifiable organizations, and a governance agreement assigns duties such as upgrades, dispute handling, and data access.
Privacy is the other common reason. On a permissioned network, transaction data can be restricted to the parties involved and to supervisors, instead of being visible to anyone.
What do public networks offer instead?
Public networks give an asset access to a wider set of wallets, applications, and liquidity without each counterparty joining a private network first. Their validators are not appointed by any one institution, which removes a single operator but also removes a single party to hold accountable.
Institutions that use public chains for regulated assets often move identity and oversight into the token layer. Allowlists, transfer rules, and issuer controls apply wherever the token is held. The multi-chain stablecoin operations guide lists those controls and how far each one reaches when the asset spans several chains.
Do the models have to be exclusive?
No. Many institutions operate on more than one kind of network, keeping some activity on a permissioned ledger and using public chains for distribution or settlement. Interoperability lets assets and messages move between them while each side keeps its own access rules. The private blockchain interoperability guide covers how those connections are built and what stays private.
FAQ
Is a consortium blockchain the same as a private blockchain?
Not quite. Both are permissioned, but a private blockchain is run by one organization while a consortium network is run by several, which spreads validation and governance across members.
Can a public blockchain support verified identities?
Yes. Identity is usually enforced at the asset or application layer, for example by allowing only verified addresses to hold a token. The base network stays open.
Does a permissioned network remove the need for oversight rules?
No. It makes participants known, but members still need agreed rules for upgrades, access to data, and resolving disputes.
Choose where the asset lives
To discuss which network model fits a tokenized asset program, request a custom briefing.