Post Oak Labs principals have worked inside several of the large vendors covered in this briefing. We approach vendor claims in this market with professional skepticism. This briefing condenses the available evidence on market sizing, platform deployment, and revenue, and says clearly where the data runs thin.
The global blockchain technology market was valued at approximately $24.5 billion in 2025 and is projected to reach roughly $39.8 billion in 2026 per Mordor Intelligence, with a CAGR near 63% through 2031.[1] Private and consortium chains are projected to capture approximately 42% of total blockchain market share in 2026, though that figure reflects enterprise software procurement spending, not on-chain transaction volume, which is measured differently and dominated by public chains. Blockchain-as-a-Service is the primary revenue vehicle, projected at around 52% of the permissioned segment by 2026, with AWS, Azure, and Google Cloud controlling approximately 63% of the public cloud BaaS market and capturing the lion's share of platform economics.[1]
On the data - read this first
No single authoritative dataset exists for permissioned blockchain market share. Vendor revenues are privately held and rarely disclosed at the platform level.[2] Figures throughout this briefing derive from deployment surveys, analyst estimates, and verified public disclosures, not audited financials. All market-share percentages should be treated as directional indicators. Pilot inflation has been a structural feature of this industry for a decade: announced pilots have chronically outnumbered live production networks, and press-release volume is not a reliable proxy for economic activity.
Hyperledger Fabric generates no licensing income. Economic value flows to IBM, AWS, Oracle, and systems integrators, none of whom isolate blockchain revenue in their financial disclosures.[2]
R3, ConsenSys, and Digital Asset are not publicly listed and are not required to publish audited financials. Revenue estimates from third-party SaaS databases are indicative only.[3]
'Market share' is sometimes deployment count, sometimes analyst mindshare survey, sometimes developer activity. PeerSpot mindshare figures showed Corda rising from 7.1% to 31.0% year-on-year while Fabric fell from 42.9% to 33.8%, using a methodology that differs substantially from deployment surveys and produces incomparable results.[7]
For most of the past decade, announced pilots far outnumbered live production networks. The ratio has improved, but the history of high-profile wind-downs (TradeLens, we.trade, Marco Polo, Contour) should inform how seriously any new announcement is weighted.[9] A persistent contributor to this pattern is what practitioners call chainwashing[23]: marketing by vendors and startups that positions blockchain as the solution to problems that existing relational databases, message queues, or shared APIs could address more cheaply. The honest due-diligence question, posed by Tim Swanson while Director of Market Research at R3, and independently documented across the literature, remains: what is it about a blockchain that solves a problem that cannot be solved with existing technology? Where a traditional database with appropriate access controls would serve, adding a blockchain layer adds complexity, cost, and vendor dependency without adding commensurate value.
Four platforms dominate institutional permissioned DLT in 2026. Their architectures, target verticals, governance models, and economics differ substantially enough that treating them as interchangeable alternatives is a procurement error.
| Attribute | Detail |
|---|---|
| Status | Open-source framework hosted by LF Decentralized Trust. No licensing revenue. Value flows to IBM, AWS, Oracle, and SIs.[2] |
| Deployment share | ~46% of enterprise permissioned deployments (Hyperledger Foundation survey, 2024, cited by ChainLaunch - not independently audited)[6] |
| Smart contracts | Go, Java, Node.js (chaincode) |
| Throughput | ~3,500 TPS (Raft consensus); benchmarks vary significantly by configuration |
| Primary verticals | Supply chain, trade finance, government records, healthcare interoperability, CBDC pilots |
| Revenue model | None at platform level. IBM, AWS, and Oracle capture value through BaaS and consulting; none break out blockchain-specific revenue.[2] |
Notable deployments. IBM Food Trust (food-safety provenance; Walmart and its supplier network) and TradeLens (container logistics; 42M+ shipments tracked across 300+ organisations before wind-down) are the most-cited examples.[8] TradeLens is a structural lesson: technically functional, commercially unsustainable. Thirteen CBDC initiatives were identified using Hyperledger frameworks as of 2021; production status of most remains unclear.[10] IBM Research published Fabric-X enhancements in May 2025 targeting regulated digital asset use cases.
Developer community: Stack Overflow activity for Fabric has declined since 2024. Developers have migrated to private Discord/Slack channels and AI-assisted tooling, a shift that complicates traditional community-health metrics.
| Attribute | Detail |
|---|---|
| Status & funding | Private company. Series A $107M (2017) plus 2019 debt round; ~$112M total. 45+ institutional investors including Bank of America, HSBC, ING, Temasek, and Intel.[5] |
| Revenue | 'Generating revenue' stage as of early 2025; exact figures not publicly disclosed. India subsidiary (R3 Corda LLP) reported ~$2.5M USD in FY2024 corporate filings, the only audited figure in the public record.[3] |
| On-chain RWAs | >$10B across live Corda-based platforms; >1M transactions/day (R3 press release, February 13, 2025; corroborated by RWA.xyz data cited in the release - vendor-issued, not independently audited)[4] |
| Smart contracts | Kotlin, Java (JVM-based CorDapps) |
| Throughput | ~1,000 TPS (benchmarked); immediate transaction finality |
| Primary verticals | Capital markets, RWA tokenisation, digital bond issuance, FX settlement, CBDC pilots |
| Strategic direction | Corda protocol launching on Solana (H1 2026) via R3 Foundation, a Solana-native curated RWA yield vault. The President of the Solana Foundation joined R3's board. Signals a deliberate pivot toward hybrid public-private architecture.[11] |
Notable live deployments: SIX Digital Exchange (SDX), Euroclear D-FMI (used by the World Bank for its 2023 digital bond issuance),[12] HQLAx (collateral mobility), Wells Fargo Coin, Progmat Coin, and the UK Regulated Liability Network (Barclays, Citi, HSBC, Lloyds, and others). R3 reported tokenisation of $17B in RWAs by late 2025.
Ecosystem volatility note: Contour, a Corda-based trade finance network backed by eight major banks including BNP Paribas, HSBC, ING, and Standard Chartered, went live but encountered significant operational difficulties in 2024.[9] Network sustainability requires more than sound technology; it requires durable commercial incentives across all consortium members.
Talent: Corda's Kotlin/JVM developer pool is estimated at ~2,500 specialists globally, thin relative to deployment ambition. Senior Corda developers command $150K–$300K in consulting rates.
Besu is an enterprise-grade Ethereum client holding approximately 28% of enterprise permissioned deployment share per the same 2024 Hyperledger Foundation survey.[6] Its primary competitive advantage is EVM compatibility: the ~23,000-strong Solidity/EVM developer pool is the largest of any permissioned platform, and it supports ERC-20/721/1155 token standards natively, making public-chain migration paths far less disruptive.
Key deployments include Nigeria's eNaira CBDC[10] and institutional tokenisation work by Citi. Approximately 31% of enterprises now run multiple DLT protocols concurrently, e.g., Fabric alongside Besu, reflecting pragmatic multi-platform reality rather than platform exclusivity.[6]
Critical migration alert: Tessera, the original Quorum private transaction manager, was deprecated in early 2026, with GitHub archival set for June 1, 2026. Any enterprise running Tessera should have migration plans in place.[13]
ConsenSys company-wide revenue estimated at ~$91M in 2025 (Latka SaaS database, unaudited). Primary sources: MetaMask, Infura, Linea, and enterprise tools, no Besu-specific revenue figure is disclosed.[3]
Canton is purpose-built for capital markets with privacy-by-design guarantees derived from the Daml smart contract language. Digital Asset raised $135M in 2025 from Goldman Sachs, BNP Paribas, DTCC, and Tradeweb, among others, and claims ~400 ecosystem participants.[14] Notable deployments include Goldman Sachs' Digital Asset Platform, HSBC Orion (compressing fixed-income settlement from T+5 toward near-T+1), and DTCC tokenisation of U.S. Treasury securities (production launch 2026).
Revenue is not publicly disclosed. The claim of 'trillions of dollars in RWAs' on Canton networks in company press materials has not been independently verified and should be treated as aspirational rather than audited.[14]
Daml is a purpose-designed smart contract language, not Solidity or JVM, which has both technical advantages for regulated workflows and a correspondingly narrow developer pool.
Not from analysts who observed them from the outside. Post Oak Labs principals have held positions at several of the large vendors discussed in this briefing, on both the technology and commercial sides. The observations below reflect that experience alongside available public evidence.
A small number of deployments are cited repeatedly as evidence that permissioned DLT works at scale: SDX, Euroclear D-FMI, HQLAx, Goldman DAP, HSBC Orion, IBM Food Trust.[8][12] These are real systems. Whether their actual transaction volumes, operational economics, and total cost of ownership justify the infrastructure versus simpler alternatives is not publicly disclosed. Vendor case studies are marketing materials. None of the parties involved publish independently audited throughput data, cost-per-transaction figures, or net economics compared to what the blockchain deployment replaced. Some of these systems may be working well. Some may be running at a cost that would not survive independent scrutiny. The publicly available evidence does not allow a confident judgment either way.
Vendor-claimed figures for on-chain RWA values (R3's press-released $10B+, Digital Asset's claimed trillions) are not independently audited.[4] They should be read as marketing, not market measurement. The underlying trend, financial institutions experimenting with tokenised settlement and bond issuance, is real. BlackRock's BUIDL fund crossed $1B on Ethereum in March 2024, deployed on a public chain, not a permissioned one.[15] Standard Chartered projects $30.1T in tokenised RWAs by 2034, a forecast issued by a bank with commercial interests in the outcome, covering a decade-long window that makes it unfalsifiable in the near term.[16]
CBDC outcomes so far are sobering. Nigeria's eNaira, built on Hyperledger Besu and launched in October 2021, had fewer than 1.15 million users by late 2022, under 0.5% of the population, with only 8% of opened wallets active. An IMF working paper noted adoption had not moved beyond a limited initial wave.[10] Cornell researchers concluded that as implemented, with all nodes running on Central Bank of Nigeria computers, eNaira was functionally indistinguishable from a centralised banking app. The eNaira has since been restructured. Thirteen CBDC initiatives identified using Hyperledger frameworks as of 2021 remain at various stages; the current production status of most is not publicly documented.
This is the central tension in the for-profit permissioned blockchain market, and it is rarely discussed openly. It is structurally very difficult for a private company to recoup its investment if the underlying protocol is genuinely open source with no vendor-controlled dependencies. Open source, by design, allows anyone to run the software without paying the original developer. This creates a powerful commercial incentive to deliberately insert the vendor as a key dependency: through proprietary tooling, a controlled ordering service, a closed certificate authority, a purpose-built smart contract language with no alternative runtime, or a BaaS layer only the vendor can operate at scale. The dependency is the product, even when it is not disclosed as such. The network's apparent openness may coexist with a commercial architecture that guarantees the vendor's indispensability. The Hyperledger projects under the Linux Foundation at least have a structural argument for vendor-neutrality that closed-source commercial platforms do not, though even open-source projects depend on who funds the maintainers and controls the roadmap.[22]
Consortium governance has not been solved. A peer-reviewed study applying Elinor Ostrom's theory of the commons to TradeLens identified lack of stakeholder engagement, unclear governance, and confidentiality concerns as the primary failure factors, not technical shortcomings.[9] TradeLens, we.trade, Marco Polo, and Contour all failed between 2022 and 2024 despite significant institutional backing. Researcher Timothy Ruff documented that the common factor was platform architecture requiring a single controlling party, fundamentally incompatible with the multi-stakeholder trust model the technology nominally provides. IBM exited its enterprise blockchain business following TradeLens, with analysts noting the ROI was not there. No one has demonstrated a governance model that durably aligns the commercial interests of competing consortium members at scale.
Corda's Kotlin/JVM specialist pool (~2,500) and Fabric's chaincode developer base (~8,000) are thin relative to deployment ambition, compared to the ~23,000 EVM developers available for Besu-based work.[6] Senior Corda developers command $150K-$300K; Fabric $150K-$200K; Besu/Solidity $120K-$170K. Proprietary smart contract languages narrow the pool further and create a switching cost that compounds over time. This is a total cost of ownership issue, not a licensing one.
For open-source platforms, economic value flows to the SI and cloud layer.[2] For closed-source vendors, revenue figures are either undisclosed or unaudited.[3] R3's only publicly audited revenue figure is its Indian subsidiary at ~$2.5M for FY2024. Digital Asset does not disclose revenue despite $135M in funding. This opacity is not incidental: it reflects an industry where the commercial case for the technology has not yet been demonstrated in public, auditable form. Buyers must model total ecosystem cost independently, including developer hiring, BaaS fees, SI implementation, governance overhead, and ongoing support.
The wall between permissioned and public DLT is dissolving. R3's Solana integration,[11] JPMorgan's use of Solana for commercial paper issuance ($50M Galaxy Digital transaction, December 2025),[17] and ~31% of enterprises already running multiple protocols concurrently all point the same direction. BlackRock BUIDL and JPMorgan Kinexys demonstrate that major institutions will use public chains when they meet regulatory requirements. Pure permissioned vendors face a structural strategic question about where they sit in a converged landscape.
It is 2026, and the honest answer is that no single platform has demonstrated decisive, durable fit-for-purpose superiority across the full range of enterprise use cases. The industry's track record of high-profile wind-downs and stalled pilots should induce caution about any document, including this one, that purports to tell you which platform to choose. What follows is not a recommendation guide; it is a set of questions that practitioners have found useful for stress-testing vendor proposals.
On endorsements - read before proceeding
This briefing does not endorse any platform for any use case. Technology selection for critical financial infrastructure is a context-specific determination that requires your legal counsel, technical architects, regulatory advisors, and operational teams, not a market briefing from an advisory firm. No one currently knows with confidence which architecture will prove most durable over a ten-year horizon. Treat vendor proposals, analyst rankings, and documents like this one with appropriate skepticism.
If your use case involves bilateral financial privacy
Capital markets workflows involving digital bond issuance, bilateral settlement, and RWA tokenisation often require transaction-level privacy between identified counterparties. Before selecting any platform, verify independently what the privacy model actually guarantees in your legal jurisdiction, whether regulators in your markets have formally engaged with the platform, and what the exit cost is if the vendor encounters commercial difficulty.
If your use case involves multi-party data sharing
Supply chain, government records, and multi-organisation networks have consistently struggled not with technical delivery but with governance sustainability. TradeLens, we.trade, Marco Polo, and Contour all failed with significant institutional backing.[9] Before committing architecture, stress-test the governance model: who pays when volumes disappoint? Who controls the ordering service? What happens if a major consortium member exits? Who benefits commercially from keeping the network running?
If your use case requires Ethereum toolchain compatibility
EVM-compatible permissioned chains offer the largest developer pool and the most portable token standards, but also inherit Ethereum's complexity surface and dependency on a large, fast-moving ecosystem. The June 2026 deprecation of Tessera[13] illustrates how quickly infrastructure dependencies can shift with no warning to deployers. Verify which privacy layer you are actually depending on and whether it has a funded, independent maintenance path.
If your use case targets regulated fixed-income or derivatives settlement
Purpose-designed smart contract languages may offer stronger formal verification properties for regulated workflows, but they also constrain your developer pool, reduce competitive tension among implementers, and create switching costs that compound over time. Claimed deployments in capital markets exist[14] but are narrow. Evaluate independently whether regulators in your jurisdiction have specifically approved the platform in question, and model the full cost of a bespoke developer talent pipeline before committing.
The structural problem no vendor will name
The deeper issue in this market is not immaturity but misaligned incentives. A private company cannot easily recoup its investment in a truly open, dependency-free protocol. The commercial pressure therefore runs toward inserting proprietary dependencies, whether through tooling, hosting, language choice, or governance control, that guarantee the vendor's indispensability. This is not a technical problem. It is a structural one, and it applies to every for-profit vendor in this space to varying degrees. Any deployment decision that does not explicitly address which elements the vendor controls, and what happens to the deployment if that vendor changes its terms or ceases to exist, has not completed its due diligence. The Hyperledger projects, backed by the Linux Foundation, have the most credible claim to vendor-neutrality in this market. That claim deserves scrutiny too: examine who funds the maintainers and who controls the roadmap in practice.
Before any architecture decision or procurement, go beyond analyst reports and vendor decks. The structural data limitations described throughout this briefing are not unusual, they are characteristic of this market.
Post Oak Labs principals have worked inside several of the large vendors covered in this briefing. If you are evaluating permissioned blockchain infrastructure, stablecoin integration, or tokenized payment architecture, we are happy to have a direct conversation.