A private blockchain is a blockchain network operated and controlled by a single organisation, which decides who can join the network, what data each participant can see and which nodes may validate new records. It uses the same core techniques as public chains, such as cryptographically linked blocks and shared copies of the ledger, but access is restricted and participants are known rather than anonymous.
Private blockchains are a type of permissioned blockchain. They are usually contrasted with a public blockchain, open to anyone, and with a consortium blockchain, governed by a group of organisations. They are used mainly by companies and financial institutions for internal record-keeping, settlement and data sharing, and the term overlaps with enterprise blockchain and private ledger.
Private blockchains in plain terms
A public blockchain is like a town noticeboard in the square: anyone can read it, anyone can pin a notice following the rules, and nobody can remove notices once posted. A private blockchain is more like a shared logbook inside a company's offices. Only staff with a pass can enter, managers decide who may write in it, and some pages may be visible only to certain departments.
The logbook still has strong features: entries are numbered and linked, so tampering is easy to spot, and several offices keep matching copies. But because one organisation holds the keys to the building, users must trust that organisation in a way they do not need to on a public network.
History
Interest in private blockchains grew quickly from about 2015, as banks and large companies looked for ways to use the technology behind Bitcoin without its open membership, volatile coin or public data. In that year the Linux Foundation launched the Hyperledger project to develop open-source enterprise ledgers, and a group of banks formed the R3 consortium, which later built the Corda platform. JPMorgan released Quorum in 2016 and, in 2019, announced JPM Coin for moving dollars between institutional clients on its own network; Quorum was later transferred to the software company ConsenSys. Many early pilots faded after the initial excitement, but the approach has continued in bank settlement systems and tokenisation projects.
How private blockchains work
- Access control. Participants are issued identities, often digital certificates, and the network checks them before allowing any read or write.
- Consensus. Because validators are known and few, private chains use fast agreement methods such as practical Byzantine fault tolerance, Raft or proof of authority rather than mining or open staking.
- Privacy features. Data can be partitioned into channels or encrypted so that only parties to a transaction see its details.
- Governance. The operator sets the rules and can change software, reverse errors or remove participants, subject to internal policy and law.
Common software frameworks include Hyperledger Fabric, from the Hyperledger project, and Quorum, an enterprise version of Ethereum.
Private vs public blockchains
| Feature | Private blockchain | Public blockchain |
|---|---|---|
| Who can join | Approved participants only | Anyone |
| Validators | Chosen by the operator | Open miners or stakers |
| Speed and cost | Fast, low cost | Slower, fees vary |
| Data visibility | Restricted | Usually public |
| Trust model | Trust in the operator | Trust in code and incentives |
Uses
- Interbank settlement. Banks have used private networks to move tokenised deposits between their own entities and clients around the clock, as with JPMorgan's blockchain-based payment platform.
- Securities and collateral. Firms record ownership of bonds, funds or collateral to speed up settlement and reduce reconciliation.
- Supply chains. Manufacturers and retailers track goods and documents across a controlled set of suppliers.
- Internal audit trails. Organisations use a private chain as a tamper-evident log for sensitive records, helping with compliance and data rules such as the GDPR.
Criticism
Critics argue that many private blockchains add little to a well-designed shared database. If one organisation controls every node, it can rewrite history, so the property of immutability depends on internal controls rather than on the network's design. A large number of enterprise blockchain pilots launched in the late 2010s were later scaled back or closed. Supporters respond that private chains offer a common data standard, a built-in audit trail and easier connections to public networks or tokenised deposit systems. A growing number of institutions now take a hybrid approach, keeping sensitive activity on a private network while connecting to public chains for issuing tokens, settling with stablecoins or proving records, which blurs the line between the two models. In practice, the choice depends on whether the parties need shared, tamper-evident records more than they need open participation.