Permissioned vs. permissionless blockchains

Blockchains are famous for open participation. A permissioned blockchain restricts it on purpose.

That one decision changes who can join, what they can see, and who is accountable when something goes wrong. A permissioned blockchain requires approval for one or more network roles. A fully permissionless blockchain lets anyone use or help operate the network under public protocol rules. Some newer chains split the difference: transactions and app deployment are open, but validation is limited to approved institutions.

Both permissioned and permissionless blockchains are distributed ledgers. The difference is who has access to the ledger and what they can do with it: read, write, or approve. Restricting users, developers, or validators creates different tradeoffs in privacy, accountability, performance, and operating cost.

What is a permissioned blockchain?

A permissioned blockchain restricts one or more network roles to approved participants. Operators may decide who can read the ledger, submit transactions, deploy apps, or validate blocks. Private single-organization chains and multi-organization consortium chains restrict most roles. A public-permissioned chain keeps the ledger publicly accessible while requiring approval for specific roles, such as block production or validation.

Permissioning can apply to different parts of a network:

• A private chain run by one organization
• A consortium chain shared by a known set of companies
• A public-permissioned chain, where anyone can use or inspect the network but only approved operators can validate new transactions or blocks

Once participants are known, operators can assign roles, run know-your-customer (KYC) and anti-money-laundering (AML) checks before granting write access, and limit sensitive ledger data to the parties who should see it. Hyperledger Fabric, an open-source framework hosted by LF Decentralized Trust, and R3 Corda, a permissioned distributed-ledger platform, are built for this pattern.

Use permissioning when named participation is a requirement, not a preference: interbank settlement, closed financial networks, and multi-party data sharing among known institutions.

What is a permissionless blockchain?

A permissionless blockchain lets people join core network roles under public protocol rules without approval from an administrator. Users create wallets, submit transactions, run nodes, and often help secure the chain through consensus. Public and permissionless describe different things: public means anyone can inspect the ledger, while permissionless means no administrator must approve participation in the relevant network role. Bitcoin, Ethereum, and Solana are the clearest fully permissionless examples.

Open participation is the defining feature. Network security relies on cryptography and economic incentives across independent operators, not on a membership list.

Choose a permissionless network when open participation makes the product more useful: open markets, public apps, and ecosystems that get stronger when third-party developers build on top of them.

How do permissioned and permissionless blockchains differ?

Both use a shared ledger. The difference is who can read it, write to it, or approve changes, and how much the network relies on known operators.

Permissionless networks reduce reliance on any one operator through protocol rules, cryptography, economic incentives, and independent operators. Permissioned networks rely more on an operator or consortium, then use that control to enforce privacy and policy.

The table compares fully permissionless and fully permissioned endpoints. Mixed public-permissioned networks can combine traits from both columns.

Neither model is automatically better. Open networks can expand reach and let other apps build on them, but they may face congestion and expose more transaction activity. Permissioned networks can enforce membership and selective visibility, but operators must fund infrastructure and participants rely more on those operators.

Which model should you use?

Start with the network role, not the brand of chain.

Use a permissioned blockchain when:

• Network participants must be known legal entities
• Ledger access or transaction submission must be restricted to approved parties
• Validators or other network operators must be approved institutions
• You need to revoke network access or enforce policy at the protocol level

Use a permissionless blockchain when:

• Anyone should be able to use or build on the product
• Independent operators should be able to help secure the network
• Public verifiability is part of the value
• Third-party developers make the product stronger

If you are not sure which model you need, consider a public-permissioned chain. Write down which roles must be open: reading, transaction submission, app deployment, block production or sequencing, and validation. You may want open access for users and developers but approved operators for block production or validation.

Start fully permissionless when open participation across those roles makes the product stronger. Start fully permissioned when every relevant role must be approved. Choose a public-permissioned model when open distribution matters but block production, validation, or specific workloads require named operators.

What do permissioned and permissionless deployments look like in practice?

Organizations in the same industry can choose different designs. What matters is which network roles must be open or restricted. The examples below show public networks with open user and developer access but restricted block production or validation, followed by fully permissioned institutional networks.

Open access with restricted block production or validation

For users and developers, Coinbase's Base is permissionless: anyone can submit transactions or deploy apps without approval. Base currently uses a single active sequencer to order transactions before settling them to Ethereum, so its access model also differs by role. As of August 2026, DeFiLlama tracked about $4.7B deposited in Base decentralized-finance protocols.

Tempo uses the same split. Its live mainnet allows anyone to deploy contracts, issue tokens, and send transactions, while the active validator set remains permissioned. Current validators include MoneyGram, Stripe, Visa, and Zodia Custody by Standard Chartered, with validator access expected to open over time.

Plasma follows a staged version of the same model. Developers can deploy Ethereum-compatible contracts and run non-validator nodes, but validator access remains limited to a small selected group while the protocol works toward permissionless validation.

Circle's Arc is designed to combine open app deployment and transactions with permissioned validation. As of August 2026, its public testnet is open to developers, but its production network remains a private mainnet with more than 100 companies and institutions building on it. Circle plans to open the public mainnet on September 16 with founding validators that include BlackRock, DTCC, Mastercard, Standard Chartered, and Visa.

Permissioned institutional networks

Swift will operate a blockchain-based shared ledger for participating banks to coordinate transfers of bank-issued digital deposits around the clock. Banks run their own environments and retain control of keys, assets, funding, and settlement, so participation is institutional rather than public. In July 2026, Swift said the ledger was ready for initial use, with 17 banks preparing pilot transactions.

In July 2026, Siam Commercial Bank became the first financial institution to go live with Citi Token Services and Citi's 24/7 USD Clearing. Citi Token Services uses a private permissioned blockchain inside the regulated banking system.

Regulated Layer One offers a chain-level example. Launched in July 2026, RL1 is a private permissioned network owned and governed by a European cooperative. Ten financial institutions founded the cooperative, and every member has an equal voice.

Canton Network sits between the categories. Its Global Synchronizer provides a public coordination layer, while each application defines its own access, privacy, and governance rules. Validator onboarding is managed, and each party sees only the transaction details it is authorized to view. This gives institutions shared infrastructure without making every transaction public.

Can you combine permissioned controls with public settlement?

An enterprise may want the openness of a public network with the control of a private one. A dedicated rollup can support that combination through custom admission and execution rules while settling results to a public network such as Ethereum. Private data still requires separate controls over where it is stored and who can access it.

Alchemy Rollups provide dedicated chains for teams that need a custom execution environment. Access controls and transaction privacy still need to be designed into the application and chain configuration. The enterprise blockchain infrastructure guide can help you choose the rest of the stack, from node access and data to chain operations.

Frequently asked questions

What is a permissioned blockchain?

A permissioned blockchain restricts one or more network roles to approved participants. Operators may control who can read, transact, deploy apps, or validate blocks. A private chain restricts most roles; a public-permissioned chain can allow open use while limiting validation to approved institutions.

What is a permissionless blockchain?

A permissionless blockchain is an open network anyone can use without prior approval. Users can create wallets, submit transactions, and often run nodes or help secure the network under the protocol rules. Bitcoin, Ethereum, and Solana are permissionless.

What is the difference between permissioned and permissionless blockchains?

The core difference is access control. A permissioned blockchain requires approval for at least one network role. A permissionless blockchain opens its core roles to anyone who follows the protocol rules. Some chains mix the models by allowing open transactions and app deployment while restricting validation.

Why would an enterprise use a permissioned blockchain?

Enterprises use permissioned blockchains when counterparties must be known, data visibility must be limited, and operators need to enforce policy on the network itself. This fits regulated finance and multi-party operations where access must be granted, audited, and revoked.

Is Ethereum permissioned or permissionless?

Ethereum is permissionless. Anyone can create a wallet, deploy a smart contract, or run a node without asking a network administrator for approval.

What is an example of a permissioned blockchain?

Regulated Layer One is a current permissioned-network example. Swift's shared ledger is another, now ready for initial bank pilots. Citi Token Services is a service that uses a private permissioned blockchain.

What does "permissionless" mean in blockchain?

Permissionless means a specific network role is open to anyone who follows the protocol rules, without approval from an administrator. A network may be permissionless for users and developers while permissioning validators or sequencers.

Are private blockchains the same as permissioned blockchains?

Not exactly. Permissioned describes whether one or more network roles require approval. Private describes whether access to the ledger or network is restricted. A private blockchain is permissioned, but a public-permissioned blockchain can allow open reading or transactions while restricting validation.