Large organisations invested substantially in distributed ledger projects over the past decade, and the record is instructive about where the technology adds value.
The initial pitch
Shared records between organisations without a central intermediary.
Which addressed the genuine problem of reconciliation between separate corporate systems.
Trade finance, supply chain and settlement were the most common targets.
What was actually built
Permissioned networks with known participants and controlled access.
Which removed most of the properties distinguishing public chains, leaving a shared database with cryptographic integrity.
Several critics observed that a well-designed conventional system would have served equally.
The consortium problem
Networks require multiple organisations to participate.
Which is a coordination problem involving competitors agreeing on governance, cost sharing and data standards.
Many projects failed here rather than technically.
Data standards
Shared records require agreement on what is recorded and how.
Which is the work that provides most of the benefit and is not a blockchain problem.
Projects that delivered value frequently did so through the standardisation rather than through the ledger.
The oracle problem in physical supply chains
Recording that goods were shipped requires someone to enter that information.
Which means the ledger records claims rather than facts.
Tamper-evidence of the record does not make the underlying assertion true, which was frequently glossed over.
Where it worked
Settlement and post-trade processing between financial institutions, where the participants are few, regulated and have a shared interest.
Which is closest to the original design intent of shared record-keeping between distrusting parties.
Several such systems are in production.
The pivot to public networks
Institutional interest shifted toward public chains and tokenised instruments.
Which reflects that the network effects and liquidity are there rather than in private consortia.
The lesson
The technology addresses coordination between parties who cannot rely on a common authority.
Where such an authority exists and works, it is generally simpler and cheaper.
Central bank experiments
Numerous central banks have run distributed ledger experiments for wholesale settlement.
Which are among the more substantial institutional deployments.
Findings have generally been published and are considerably more measured than commercial claims.
Interoperability
Private networks that cannot communicate reproduce the silo problem they aimed to solve.
Which drove interest in standards and in connecting to public infrastructure.
This was a recurring finding across consortium projects.
Vendor dependency
Platforms built on specific vendor frameworks carry ongoing dependency.
Which became consequential when several enterprise frameworks were discontinued or deprioritised.
Organisations were left maintaining systems on unsupported platforms.
Cost of operation
Running a node imposes ongoing cost on each participant.
Which participants weighed against benefit and frequently found wanting.
Participation attrition killed several networks that were technically functional.
What survives
Systems solving genuine multi-party coordination problems where no acceptable central operator exists.
Which is a narrower set of use cases than was originally proposed, and it is a real one.
Identity and credentials
Verifiable credentials and decentralised identifiers have progressed as standards.
Which addresses a genuine problem in cross-organisation verification.
Adoption has been slow and the standards work is substantive.
Provenance and traceability
Recording chain of custody for goods.
Which works where the data entry points are trustworthy and controlled.
Successful implementations generally pair the ledger with physical verification measures.
Internal use cases
Some organisations used the technology internally between business units.
Which removes the trustless justification entirely and is sometimes still the easiest way to build shared records.
Skills and staffing
Projects required expertise that was scarce and expensive during the peak of interest.
Which contributed to cost overruns and abandonment.
The realistic assessment
The record does not support the initial claims and does support a narrower set of applications where multi-party coordination without a central authority is genuinely required.
Reading claims critically
Ask what problem is being solved, whether a central operator could solve it, and why the parties cannot simply agree on one.
Which is the question that separates genuine applications from expensive databases.
Most projects that failed could not answer it.
A decade on
The technology found narrower applications than promised, which is the usual pattern for any general-purpose technology after an initial wave of enthusiasm.
Which does not make the applications that survived less real.
The standards, identity work and settlement systems that came out of the period are the durable outcomes.
For organisations evaluating now
Start from the coordination problem rather than from the technology.
Which produces a shorter list of candidate applications and a much higher success rate among them.
The record of the past decade is publicly documented and is worth reading before committing budget.
A closing observation
The projects that quietly succeeded generally involved a small number of regulated institutions with a genuine reconciliation problem and no acceptable candidate for a central operator. Everything else was a database with extra steps and a longer procurement cycle.
That distinction was available at the outset and was frequently ignored in favour of the more exciting version.