Private Blockchain Promised CTOs Everything. Here’s Why 67% Switched to Public, and What the Other 33% Know That You Don’t
Private vs. public blockchain for enterprise: the core difference is control vs. connectivity. Private blockchains offer governance control; public blockchains offer open liquidity and network effects. As of 2026, most enterprises above $1B in revenue are adopting hybrid architectures rather than making a binary switch.
In November 2022, A.P. Moller-Maersk and IBM pulled the plug on TradeLens, the most expensive, most hyped private blockchain platform in enterprise history. Five years. Over 300 members. More than half of all global ocean container cargo flowing through it. Still not enough. The official reason: “full global industry collaboration has not been achieved.” The real reason: private blockchain carries a structural flaw that no amount of engineering can fix.
That announcement didn’t just close a platform. It effectively closed an era. Within 24 months, four more major private blockchain consortia collapsed. And the enterprises that once built their digital transformation strategies around permissioned blockchains started asking a question they hadn’t wanted to ask: what if we bet on the wrong architecture?
Fast-forward to December 2025. JPMorgan, whose CEO Jamie Dimon once called most crypto “garbage”, committed $100 million to launch a tokenized money market fund on the public Ethereum blockchain. BlackRock’s BUIDL fund, also on public Ethereum, surpassed $2 billion in assets. The tokenized real-world asset market crossed $32 billion in Q1 2026, up more than 400% since the start of 2025.
The debate between private vs. public blockchain for enterprise is no longer theoretical. The money has spoken. But the full picture is more nuanced than the headlines suggest, and if you’re a CTO making infrastructure decisions right now, that nuance is worth every minute of your attention.
The Promise That Sold a Generation of CTOs
From 2015 through 2022, “blockchain, not Bitcoin” was the enterprise technology mantra. The logic was clean and compelling. Take distributed ledger technology, immutable records, cryptographic verification, decentralized trust, and strip out the parts that make compliance officers nervous. No public visibility. No cryptocurrency exposure. No regulatory ambiguity. Just the efficiency gains.
Private or permissioned blockchains fit that brief perfectly. On a private blockchain, only authorized participants can read or write transactions. A central authority, typically a consortium of participating organizations, controls governance. Companies like IBM and R3 built entire product lines around this model. Hyperledger Fabric and R3 Corda became the enterprise-grade standards. Banks, shipping companies, and trade finance networks lined up to build on them.
The pitch to CTOs was almost irresistible: get the benefits of an immutable shared ledger, maintain full control over who sees what, satisfy compliance teams, and avoid the volatility of public cryptocurrency networks. Between 2017 and 2020, billions flowed into private blockchain consortium projects. The enterprise blockchain market was valued at $9.64 billion in 2023 and projected by MarketsandMarkets to reach $145.9 billion by 2030.
There was just one problem. A problem that Gartner saw coming as early as July 2019, when it predicted that 90% of enterprise blockchain implementations would require replacement within 18 months. Almost nobody listened.
Five Platforms. Five Failures. One Pattern.
The collapse wasn’t gradual. It was a concentrated demolition of the private blockchain consortium model between 2022 and 2024. Five platforms, all launched with serious institutional backing, all shut down or abandoned blockchain within five years.
| Platform | Launch Year | Technology | Key Backers | Fate |
|---|---|---|---|---|
| We.trade | 2017 | Hyperledger Fabric | Deutsche Bank, HSBC, Santander, UBS | Ceased operations, June 2022 |
| TradeLens | 2018 | Hyperledger Fabric | IBM, Maersk | Shut down Q1 2023 |
| Marco Polo | 2019 | R3 Corda | Commerzbank, BNY Mellon, SMBC | Entered administration, Nov 2022 |
| Contour | 2020 | R3 Corda | ANZ, BNP Paribas, HSBC, Standard Chartered | Ceased operations, Oct 2023 |
| Komgo | 2018 | Quorum | Citi, ING | Abandoned blockchain entirely |
Look at those names. The best banks in the world. The best shipping company in the world. Years of development. Combined, they represent hundreds of millions in investment and some of the best enterprise engineering talent available. None of it was enough.
Rotem Hershko, Head of Business Platforms at Maersk and the executive who led TradeLens, delivered the clearest post-mortem on record:
“While we successfully developed a viable platform, the need for full global industry collaboration has not been achieved. As a result, TradeLens has not reached the level of commercial viability necessary to continue work.”
Rotem Hershko, A.P. Moller-Maersk — Official Announcement, November 30, 2022
Avivah Litan, Vice President and Distinguished Analyst at Gartner Research, called TradeLens’s failure the end of an era:
“[TradeLens’s failure] seems like the last chapter in the era of costly enterprise blockchain projects. They only succeed when all parties are on the same win-win page, and there is clear demonstrable ROI when the application is implemented.”
Avivah Litan, Gartner Research — Computerworld, December 2022
Martha Bennett, Principal Analyst at Forrester Research, pointed to a structural truth that should have been obvious from the start: a private blockchain only delivers value when everyone joins it. And getting direct competitors to share infrastructure on terms that benefit everyone equally is, in practice, nearly impossible.
A peer-reviewed analysis published in Frontiers in Blockchain (February 2025) confirmed what industry observers had suspected: TradeLens didn’t fail because the technology was broken. It failed because of governance imbalances and misaligned economic incentives among participants. The blockchain worked. The business model didn’t.
The collapse of TradeLens in 2023 effectively closed the era of bilateral private blockchain consortia. The failure wasn’t technological. It was structural: private blockchains require near-universal adoption to deliver value, and that level of coordination among competitors is almost never achievable.
Why 67% Are Switching to Public Blockchain
Three forces converged in 2024 and 2025 that fundamentally changed the calculus for enterprise blockchain adoption. Each one, individually, would have been significant. Together, they’ve rewritten the playbook.
1. The Privacy Problem Got Solved
The single most cited reason enterprises chose private blockchains was data privacy. On a public blockchain, transaction data is visible to anyone. That was a non-starter for any regulated business handling sensitive financial data, trade secrets, or customer information.
That objection is now largely resolved. Zero-knowledge proof (ZKP) systems allow enterprises to transact on a public blockchain while revealing nothing about the underlying data. EY launched its OpsChain platform with Nightfall ZKP technology specifically for this purpose. Polygon’s zkEVM, zkSync, and StarkWare offer enterprise-grade privacy layers on top of Ethereum’s public infrastructure.
Paul Brody, EY’s Global Blockchain Leader and Chairman of the Enterprise Ethereum Alliance, is direct about what this means:
“A lot of people don’t realize private blockchains have no privacy. They’re centralized systems without the benefits of a decentralized ledger.”
Paul Brody, EY Global Blockchain Leader — Tearsheet Podcast, January 2025
Brody’s position isn’t a minority view. It’s the consensus among enterprise blockchain leaders who have worked through the technology’s evolution over the past decade:
“I strongly believe that the only way blockchain ever delivers on the kind of vision we have is if we use one global public blockchain.”
Paul Brody, EY Global Blockchain Leader — Enterprise Ethereum Alliance
2. Wall Street Committed Real Capital
Arguments change minds. Billions of dollars change industries. On December 15, 2025, JPMorgan Asset Management launched its My OnChain Net Yield Fund (MONY) on the public Ethereum blockchain, seeded with $100 million. This made JPMorgan the largest Global Systemically Important Bank to deploy a tokenized fund on public blockchain infrastructure.
That wasn’t a pilot. That wasn’t a proof of concept. That was the most systemically important bank in the United States putting nine figures of real capital on a public blockchain, the same technology that enterprise CTOs had spent years arguing was too risky, too uncontrolled, and too exposed for institutional use.
BlackRock’s BUIDL fund launched on Ethereum in March 2024 and surpassed $2 billion in assets by end-2025, later expanding to five blockchains. Larry Fink, BlackRock’s Chairman and CEO, has been unequivocal:
“Every financial asset can be tokenized. Tokenization allows for fractional ownership. This lowers one of the barriers to investing in valuable, previously inaccessible assets like private real estate and private equity.”
Larry Fink, Chairman and CEO, BlackRock — Annual Letter to Investors, 2025
Franklin Templeton had already moved earlier with its BENJI fund in 2021. Goldman Sachs and Fidelity have both filed for or launched tokenized products on public chains. When institutions collectively managing tens of trillions in assets all arrive at the same infrastructure decision, the message to enterprise technology leaders is unmistakable.
3. Regulation Became a Reason to Go Public, Not Stay Private
For years, “regulatory compliance” was the argument for private blockchain. Public chains were too ambiguous, too uncontrolled, too exposed to cryptocurrency volatility and regulatory scrutiny. That argument has been inverted.
The U.S. GENIUS Act (2025) and EU MiCA regulation have, for the first time, created legally defensible pathways for enterprises to deploy on public blockchains. The GENIUS Act and stablecoin regulation framework now means that compliance is increasingly becoming a reason to use public infrastructure, not avoid it. SEC Chairman Paul Atkins has explicitly endorsed tokenization as a key capital markets innovation.
For CTOs building blockchain strategies in 2026, the “public chain is too risky for compliance” argument has lost its most important anchor: JPMorgan’s legal and compliance teams blessed a $100 million public Ethereum deployment. If it’s defensible at that scale, it’s defensible at yours.
What the Other 33% Actually Know
Here’s where the headline narrative gets dangerous if taken too literally. The 67% figure from the Coinbase-EY 2026 survey reflects institutions that prioritize asset tokenization over the next 3-5 years. That is intent, not a completed migration. Many enterprises are pursuing hybrid approaches. The “switch” is frequently additive, not substitutive.
The 33% staying on private or permissioned blockchain infrastructure aren’t technologically backward. Several have entirely legitimate reasons.
Healthcare: HIPAA Doesn’t Negotiate
Patient data under HIPAA requires on-premises or controlled deployment in many scenarios. A public blockchain transaction is, by definition, visible on a distributed public ledger. Even with ZKP encryption, the compliance burden of proving that no Protected Health Information is exposed or derivable from on-chain data is substantial. Healthcare organizations processing millions of patient records aren’t going to rebuild their infrastructure on public chains until that legal clarity arrives explicitly, not by implication.
Performance: 10,000 TPS Is Not Optional for ERP
Ethereum mainnet processes 15-30 transactions per second. Visa processes 24,000 TPS at peak. Enterprise ERP systems running supply chain, manufacturing, or high-frequency financial workflows need consistent throughput at predictable costs. Even with Layer-2 rollup solutions, public blockchains cannot yet reliably deliver the performance that enterprise-grade operations demand. This is a real technical constraint, not a theoretical one.
Where Private Chains Still Win: Authenticated Luxury Goods
Cartier’s implementation through the AURA Blockchain Consortium demonstrates that private blockchains deliver measurable ROI in specific, well-governed contexts. Their private blockchain for timepiece authentication achieved a 15% increase in cost estimate approval rates and a 4.8/5 customer satisfaction rating. The use case is narrow, the participants are controlled, and the incentive alignment is clear. This is exactly the scenario where private blockchain’s governance model works, because nobody is asking competitors to share infrastructure with each other.
The 33% who stay on private blockchain aren’t losing this debate. They’re operating in verticals where the constraints that killed TradeLens don’t apply: regulated data environments, performance-critical workflows, or narrow use cases with fully aligned stakeholder incentives. The mistake is assuming their choice is the right default for everyone else.
The Hybrid Architecture: The Real Answer for 2026
JPMorgan itself proves the point. The bank’s Kinexys platform operates simultaneously across public Ethereum, its private Canton network, and Hyperledger Fabric. The institutions moving to public blockchain aren’t abandoning private infrastructure wholesale. They’re building hybrid architectures that use each layer for what it does best.
The optimal path for most enterprises in 2026 looks like this: sensitive operations, internal workflows, and regulated data run on a permissioned private or consortium network. Settlement, verification, liquidity access, and external counterparty interactions happen on a public chain like Ethereum or Solana.
This matters for CTOs who inherited private blockchain deployments and are now facing pressure to “go public.” The question isn’t which type to choose. It’s which operations belong on which layer, and how to build the bridges between them without creating new single points of failure.
Interoperability protocols including Chainlink CCIP, LayerZero, and Polkadot are making this hybrid model increasingly workable. Enterprises don’t need to blow up their existing private chain investments to access public chain liquidity. They need the right connective tissue between the two.
| Factor | Private Blockchain | Public Blockchain | Hybrid Architecture |
|---|---|---|---|
| Privacy | Controlled access, but no true cryptographic privacy | ZKPs now enable selective disclosure | Sensitive data stays private; attestations go public |
| Performance | High TPS, predictable costs | 15-30 TPS mainnet; L2s improve this significantly | Private layer handles throughput; public handles settlement |
| Liquidity Access | Isolated; no connection to DeFi or on-chain markets | Access to $32B+ RWA market and DeFi composability | Public settlement layer connects to on-chain liquidity |
| Regulatory Posture | Strong for HIPAA, GDPR; weaker for MiCA/GENIUS compliance | MiCA and GENIUS Act create clear pathways | Jurisdiction-specific layer selection |
| Governance | Central control; adoption paradox for consortia | Decentralized; smart contract risk | Internal governance retained; external trust outsourced |
| Developer Talent | Scarce; Fabric/Corda specialists hard to hire | Deep Ethereum/Solana developer pool | Public chain skills dominate; private layer is operational |
The Risks Nobody Is Talking About Loudly Enough
The optimistic narrative around public blockchain adoption for enterprise is broadly correct. But it is running ahead of operational reality in several important ways. If you’re making infrastructure decisions based purely on the JPMorgan and BlackRock headlines, here’s what the press releases tend to leave out.
Smart Contract Exploits at Enterprise Scale
DeFiLlama reported losses exceeding $200 million from smart contract exploits in June 2024 alone. Cumulative illicit activity tracked by Chainalysis reached $24.2 billion in 2023. When enterprises deploy tokenized assets on public chains, they inherit the public attack surface. A successful exploit against a major institutional tokenized asset product wouldn’t just harm one company. It could freeze the entire tokenized RWA market for regulatory review. The cross-chain bridge vulnerabilities discovered in 2026 demonstrate that this risk is ongoing, not theoretical.
ZKP Maturity Is Overstated for Most Enterprise Teams
Zero-knowledge proofs are computationally expensive and require specialized cryptographic engineering talent that most enterprise IT departments don’t have and can’t easily hire. EY’s OpsChain is impressive. It’s also a product built by one of the largest professional services firms in the world, with years of R&D investment behind it. The “privacy problem is solved” narrative is accurate at the frontier. For most enterprise teams, the operational reality of deploying ZKP systems in production is considerably more complex than the conference presentations suggest.
Layer-2 Centralization Is a Hidden Risk
Many Layer-2 blockchain solutions currently operate with centralized sequencers, meaning the “public” chain is actually controlled by a single operator at the sequencer level. Enterprises building on centralized L2s inherit exactly the single-point-of-failure risk they fled private blockchains to escape. If the sequencer operator fails, is compromised, or is acquired, the enterprise’s blockchain infrastructure is at risk. This isn’t a theoretical concern. It’s a live architectural question that deserves explicit due diligence before any L2 deployment.
JPMorgan and BlackRock haven’t abandoned private blockchains. They operate multi-chain hybrid architectures. Enterprise press coverage consistently omits this nuance. The correct read isn’t “private blockchain is dead.” It’s “pure private blockchain as a complete enterprise strategy is dead.” Hybrid is the destination, not full public-chain migration.
Regulatory Frameworks Are Not Universal
The GENIUS Act and EU MiCA are real regulatory progress. They apply in the United States and the European Union. An enterprise operating in Singapore, the UAE, Brazil, or India faces a completely different regulatory environment. Compliance teams in those jurisdictions cannot point to GENIUS Act safe harbors. The “regulation now supports public chains” argument is geographically bounded, and enterprise CTOs with global operations need to account for that variance explicitly.
FAQ: Private vs. Public Blockchain for Enterprise
What is the difference between public and private blockchain?
A public blockchain is open to anyone, anyone can read, write, and validate transactions (Ethereum and Bitcoin are the primary examples). A private blockchain restricts access to authorized participants only, with a central authority controlling governance. Public chains offer greater decentralization and network effects; private chains offer control, speed, and compliance alignment. Neither is inherently more secure. Each carries distinct risk profiles depending on the use case.
Why are enterprises moving from private to public blockchain?
The shift is driven by four converging forces: (1) zero-knowledge proofs have resolved the privacy problem that made public chains unworkable for regulated industries; (2) tokenized assets on public chains now access billions in liquidity that private chains cannot reach; (3) regulatory frameworks including the U.S. GENIUS Act and EU MiCA create compliance pathways; and (4) JPMorgan, BlackRock, and Franklin Templeton have demonstrated public chains are enterprise-viable at institutional scale.
What is the biggest problem with private blockchain?
The governance and adoption paradox. A private blockchain only delivers value when all relevant counterparties join it, but getting direct competitors to share infrastructure on mutually beneficial terms is nearly impossible at scale. TradeLens attracted 300+ members and covered more than half of all ocean container cargo, still not enough. The peer-reviewed post-mortem confirmed: the failure was governance, not technology.
Is Ethereum good for enterprise use?
Yes, as of 2025-2026, with the right architecture. EY’s Paul Brody argues Ethereum is the only viable long-term public infrastructure for enterprise blockchain because it’s the only global network with the network effects, developer ecosystem, and privacy tooling at the scale enterprises require. JPMorgan, BlackRock, and Franklin Templeton have all deployed institutional products on Ethereum’s public infrastructure. The caveat: enterprises need L2 solutions for throughput, and ZKP tooling for privacy compliance.
What is a hybrid blockchain architecture?
A hybrid blockchain combines private and public layers for different functions. Sensitive operations, regulated data, and internal workflows run on a permissioned private network. Settlement, verification, and liquidity access happen on a public chain like Ethereum. JPMorgan operates exactly this model: its private Canton network handles internal settlements, while public Ethereum hosts its tokenized fund products. For most enterprises above $500M in revenue, hybrid is the practical destination in 2026.
Did IBM abandon blockchain?
IBM has exited most of its consumer-facing blockchain product business. TradeLens (with Maersk) shut down in Q1 2023, and IBM Food Trust continues at reduced scale. However, Hyperledger Fabric, the open-source technology IBM originally developed, continues in 500+ enterprise production deployments globally according to IDC’s 2024 data. IBM’s exit reflects a business model failure around the consortium approach, not a failure of the underlying technology for appropriate use cases.
What Happens Next
The private vs. public blockchain debate for enterprise has effectively been resolved at the strategic level. Pure private blockchain consortia, the model that TradeLens, We.trade, Marco Polo, and Contour represented, is a failed architecture for any use case that requires cross-competitor participation. The governance problem is not solvable at that scale. Gartner said so in 2019. The market confirmed it between 2022 and 2024.
Public blockchain adoption by enterprises above $1 billion in revenue is now in scale phase. The tokenized real-world asset market at $32 billion in Q1 2026 is not a speculative future, it is present-tense infrastructure that enterprises either participate in or get locked out of. BCG projects $16 trillion in tokenized assets by 2030. Citi estimates $4-5 trillion in tokenized securities alone.
What the next 6 to 18 months will clarify is whether hybrid architecture becomes the default enterprise blockchain model, or whether a major smart contract exploit triggers the kind of regulatory reaction that pauses institutional public-chain deployment. Watch JPMorgan’s second Ethereum Treasury fund filing (May 2026) for signals about how regulators respond at scale. Watch the stablecoin and tokenization regulatory frameworks in the U.S. and EU for the compliance architecture that will govern the next phase of adoption.
Three things to watch or act on right now:
- If you’re evaluating public blockchain: audit your L2 vendor’s sequencer architecture before committing. Centralized sequencers undermine the core value proposition of public chain deployment.
- If you’re on private blockchain: the question isn’t whether to move, it’s which operations belong on a public settlement layer and which stay permissioned. Start with non-sensitive settlement and verification workflows.
- If you’re in healthcare or defense: the 33% who stay private are not wrong. But hybrid architecture, private for sensitive compute, public for attestation, is the direction that preserves compliance while accessing the network effects that pure private chains can’t offer.
The era of “blockchain, not Bitcoin” is over. The era of “public blockchain, with the right architecture” is here. The enterprises that understand the difference between those two statements are the ones building durable competitive advantage right now.