Permissioned Blockchain

A permissioned blockchain is a distributed ledger on which the right to validate, read, or submit transactions is restricted to identified, pre-approved participants rather than open to anyone.

How it works

A permissioned blockchain gates one or more roles behind an access control layer: who can run a validating node, who can submit transactions, and who can read the ledger. Membership is tied to real-world identity through a certificate authority or a governance body, rather than to anonymous key ownership. Hyperledger Fabric uses a Membership Service Provider to issue X.509 certificates to each organization, and channels to partition data so only named members see a given subledger. R3 Corda, used in deployments such as HQLAx for collateral mobility, shares transaction data only with parties to a trade rather than broadcasting it network-wide.

Because validators are known, these networks typically use Byzantine fault tolerant or crash fault tolerant consensus instead of proof of work. The Canton Network, which underpins tokenized assets at Broadridge and the DTCC, coordinates independent synchronizers so participants transact across applications while retaining control over their own data. JPMorgan's Onyx and its Kinexys deposit token settlement run on a permissioned fork of Ethereum (Quorum lineage). The non-crypto sense of the word is the ordinary one: access requires permission.

Why it matters

Permissioned designs let regulated institutions meet KYC, AML, and data-confidentiality obligations that a public chain does not natively enforce, which is why most bank-led tokenization and settlement pilots use them. The tradeoff is centralization: a small, identified validator set can censor transactions or collude, and the governing consortium can alter rules. Settlement finality depends on trusting that membership operators behave honestly and stay available, so the security model rests on legal agreements and operator reputation rather than open economic incentives.

Related terms

• Public (permissionless) blockchain
• Consortium blockchain
• Byzantine fault tolerant consensus
• Tokenized deposit
• Membership Service Provider

Frequently asked questions

How is a permissioned blockchain different from a public blockchain?

Participation is restricted to identified, approved parties, and validators are known rather than anonymous. This supports KYC and data privacy but concentrates control in a defined set of operators instead of an open network.

Is a permissioned blockchain the same as a consortium blockchain?

A consortium blockchain is one type of permissioned blockchain, governed jointly by several organizations. Other permissioned networks are run by a single entity. Both restrict access, but they differ in how governance is distributed.

What is the main risk of a permissioned blockchain?

Centralization. A small, identified validator set can censor transactions or collude, and the governing body can change rules. Security relies on legal agreements and operator trust rather than open economic incentives.

See the data behind this post. Browse the full dataset catalogue, or read What Is Onchain Data Normalization? for how the records are put together.

Allium provides onchain data infrastructure. Companies named in this article may be Allium customers, prospects or commercial counterparties. The authors and other Allium personnel may hold positions in the assets discussed. This article is informational only and is not investment, legal or tax advice. Data and information last reviewed: October 23, 2026.