Linux Foundation Decentralized Trust report counts its technology in 29.4% of institutional blockchain platforms that disclose a stack

A research report commissioned by the Linux Foundation Decentralized Trust and conducted by Ledger Insights counts the foundation's technology inside 29.4% of institutional blockchain platforms, measured against the projects that disclosed what they run on — and more than a quarter of the sample said nothing at all. Hyperledger Fabric and Besu rank among the top three technologies by deployment, and the remaining two slots in the top four belong to categories the report treats as catch-alls: EVM-compatible stacks and proprietary systems.

The names on the list carry more weight than the percentage: Project Agorá, which the report describes as involving all G7 economies, and the Eurosystem's Project Pontes both run on LFDT technology, as do projects at Clearstream, DTCC and Euroclear — what the report calls the world's three largest central securities depositories — and at BNP Paribas, Citi and HSBC, three of the top five global systemically important banks, with Swift, one of the market infrastructures the report singles out, also in the count.

Daniela Barbosa, the Linux Foundation's general manager for decentralized technologies and executive director of LFDT, frames the exercise as stewardship: decisions made by central banks, market infrastructures and commercial banks shape how financial systems will connect, she said, and they "bring long-term responsibilities for the communities maintaining the underlying code."

The headline figure covers disclosed deployments only, so the silent quarter is excluded from both the numerator and the denominator, and two of the top four slots belong to categories rather than products — EVM-compatible technologies and proprietary systems together hold 25% of the disclosed field. The authors say their reading of sources and of project staff's skills indicates some of those EVM-compatible deployments almost certainly run Besu, which they left uncounted for lack of confirmation, and they describe the number of proprietary systems built from a genuinely clean sheet as likely very few, without estimating the size of the correction.

The provenance deserves naming: the organization whose technologies were counted paid for the counting, which does not make 29.4% wrong. A depository running Fabric is a checkable fact, and the roster of named projects can be verified one at a time, but the report's forward-leaning claims — that Besu hides inside the EVM bucket, that proprietary stacks owe more to open-source foundations than their labels admit — are precisely the claims a sponsor has reason to want and a reader has no way to audit.

What the survey does establish is that a handful of codebases has become the default procurement answer for institutions that cannot afford to be wrong. Three of the largest settlement depositories and three of the five largest global systemically important banks converging on the same two Hyperledger projects says something about standardization, and standardization arrives with a bill: integration gets cheaper while every participant takes on a dependency on maintainers it does not employ. Open-source maintenance as a diligence line item is not a new argument here, but a central bank cannot swap out a settlement stack on a quarter's notice the way a wealth platform can retire a reporting tool.

The report also pushes back on the reading that the foundation's position is inherited, noting Hyperledger Fabric was one of the earliest enterprise blockchain technologies and some of those deployments are still running, which alone would produce a high share from history. The authors argue the size and recency of the projects in the count — central bank initiatives, depositories, G-SIBs — point to a footprint that is expanding rather than coasting, a distinction that separates a standard from an installed base and is the one an institution choosing a stack this year would most want settled, though the report asserts it more than it proves it.

Adaptation is the third path, and the report names two examples: Citi and India's National Payments Corporation of India, which also operates the country's UPI payment system, are open about having adapted LFDT technology inside their own systems, each a proprietary label sitting over an open-source foundation. Whether the pattern extends through the rest of the proprietary bucket is the report's biggest open question, and it decides how far 29.4% understates the real number.

The tokenization evidence points the same way: as this publication wrote about Hana's $100 million digital bond, the clearing rail, not the token, was doing the work, with settlement through Euroclear on existing shelf documents, and Swift's ledger has netted the obligations of two banks' tokenized deposits while final settlement stayed on legacy systems. If the rails are where institutional value accumulates, then the code the rails are built from is a strategic dependency, and a survey that counts which foundation's technology each project runs on becomes an inventory of who has already signed up for it.

In tokenization, as this masthead has argued, value accrues to whoever controls the collateral and settlement rails, not the issuance layer, and codebase concentration is the layer underneath those rails. A depository that settles tokenized issuance on Fabric has made a choice that constrains what its participants can build next, and those participants — custodians, banks, issuers — will meet the constraint the first time a feature they need sits behind a foundation committee rather than a purchase order. The undisclosed quarter is where the next revision of the number comes from, and no new deployment is required for the share to move; more projects simply need to start answering the question.