TradeLens (Maersk + IBM), $100M+ Lost to Consortium Politics
TradeLens was the marquee enterprise blockchain project. Maersk, the world’s largest container shipping company, partnered with IBM to digitize global shipping documentation on Hyperledger Fabric. The platform would replace paper-based bills of lading, customs forms, and shipping manifests with blockchain-verified digital records.
Launched in 2018, it shut down in late 2022 after failing to achieve the industry-wide adoption required for viability.
What went wrong: Maersk’s competitors (CMA CGM, MSC, Hapag-Lloyd) refused to join a platform controlled by their largest rival. Despite IBM’s role as a neutral technology partner, the governance structure was perceived as Maersk-centric. The platform needed network effects, it is useless if only one carrier uses it, but the competitive dynamics of the shipping industry made those network effects structurally impossible under Maersk’s ownership.
The lesson: Blockchain for an industry consortium cannot be led by a dominant competitor. Either a neutral third party operates the platform, or the governance model must genuinely distribute control. Competitive industries need governance neutrality as a prerequisite for adoption, not as a future enhancement.
ASX CHESS Replacement, $250M+ and Seven Years Wasted
The Australian Securities Exchange announced in 2017 that it would replace its CHESS clearing and settlement system with a blockchain-based alternative built on Digital Asset’s DAML platform. It was supposed to be the proof that blockchain could handle critical financial infrastructure.
After repeated delays, the project was officially abandoned in November 2022. ASX took a $170 million write-down and launched an independent review that found fundamental project management failures.
What went wrong: Multiple factors compounded. The existing CHESS system worked, participants had no urgent pain point driving adoption. The project scope expanded repeatedly as stakeholder requirements grew. The technology was immature when development began, requiring significant custom engineering. And critically, the project failed to demonstrate that blockchain provided meaningful advantages over a modernized centralized system for this specific use case.
The lesson: Replacing working infrastructure with blockchain requires a compelling advantage beyond “it uses blockchain.” If the existing centralized system is trusted and functional, the burden of proof on the blockchain replacement is extremely high. Technology novelty is not a sufficient business case for replacing critical infrastructure.
We.trade, European Banking Consortium Dissolved
We.trade was a trade finance platform built on Hyperledger Fabric by a consortium of twelve major European banks including HSBC, Deutsche Bank, and Société Générale. It aimed to digitize trade finance for small and medium enterprises. The platform went live in 2018 and processed real transactions across twelve European countries.
The company went into liquidation in mid-2022.
What went wrong: The consortium struggled with a classic chicken-and-egg problem, SMEs would not adopt the platform without their banks supporting it, and banks could not justify the investment without SME volume. Transaction volumes remained too low to cover operational costs. Additionally, the twelve-bank governance structure made decision-making slow. Each bank had different risk appetites, compliance requirements, and strategic priorities. Achieving consensus on basic operational decisions was painfully difficult.
The lesson: Network effects are the biggest risk in consortium blockchain. If you cannot achieve critical mass of participants and transaction volume, the economics do not work. And large consortiums are harder to steer than small ones, twelve banks with twelve different agendas move slower than three banks with a shared mission.
IBM Blockchain, Strategic Retreat
IBM was the enterprise blockchain evangelist. They contributed heavily to Hyperledger Fabric, built Food Trust with Walmart, partnered with Maersk on TradeLens, and marketed blockchain as a transformative enterprise technology. At its peak, IBM’s blockchain division had over 1,000 employees.
By 2023, IBM had quietly dismantled most of its blockchain team. TradeLens was shut down. The blockchain division was absorbed into other business units. The company shifted its messaging from blockchain-specific solutions to broader “trust and transparency” positioning.
What went wrong: The enterprise blockchain market did not materialize at the scale IBM projected. Most proofs of concept did not convert to production deployments. Revenue from blockchain services was a fraction of what internal projections estimated. The technology worked, but the market adoption timeline was measured in decades, not years, and IBM’s quarterly earnings cycle could not accommodate that patience.
The lesson: Technology readiness does not equal market readiness. Enterprise blockchain adoption depends on industry coordination, regulatory clarity, and organizational change management, factors that technology vendors cannot control. Building a business around ecosystem adoption that requires competitors to cooperate is structurally risky.
Common Patterns in Failures
Blockchain Failure Pattern Analysis:
┌─────────────────────────┬──────────────────────────────────┐
│ Failure Pattern │ Projects Affected │
├─────────────────────────┼──────────────────────────────────┤
│ Governance conflict │ TradeLens, We.trade, R3 exodus │
│ No clear pain point │ ASX CHESS, many PoCs │
│ Network effect failure │ We.trade, TradeLens, IBM general│
│ Scope creep │ ASX CHESS │
│ Competitor distrust │ TradeLens, GSBN shipping │
│ Overestimated timeline │ IBM Blockchain, most PoCs │
│ Technology immaturity │ ASX CHESS (2017-era DLT) │
│ Regulatory uncertainty │ Multiple DeFi-adjacent projects │
└─────────────────────────┴──────────────────────────────────┘
Root cause distribution (observed across 50+ failed projects):
40%, Governance / consortium politics
25%, No genuine problem-solution fit
20%, Failed to achieve network effects
10%, Technical issues
5%, Regulatory blockersThe pattern is stark: technical failure is the rarest cause of enterprise blockchain project failure. Governance, adoption, and problem-solution fit dominate. The technology works. The organizational and market challenges are what kill projects.
What Survivors Do Differently
Projects that succeeded, Walmart Food Trust, De Beers Tracr, JPMorgan Onyx, share common traits. They started with a specific, measurable problem (food traceability, diamond provenance, intraday settlement). They had a dominant entity that could mandate adoption or a small group of tightly aligned participants. They designed governance before technology. And they measured success by operational improvements, not by technology deployment milestones.
The difference between a failed blockchain project and a successful one is rarely the choice of platform, the consensus mechanism, or the smart contract language. It is whether someone asked the hard questions about governance, adoption, and genuine need before writing the first line of code. The projects that skipped those questions are the ones in this article.
Frequently Asked Questions
TradeLens, the Maersk and IBM blockchain platform for global shipping, failed primarily due to consortium politics and adoption resistance. Competing shipping carriers refused to join a platform controlled by their largest competitor. Despite spending over $100 million, TradeLens could not achieve the network effects needed to make the platform valuable. The core lesson is that blockchain requires neutral governance; when one dominant player controls the network, competitors will not participate regardless of the technical benefits.
The Australian Securities Exchange spent over $250 million and seven years attempting to replace their CHESS clearing system with a blockchain solution built on Digital Asset’s DAML platform. The project failed due to scope creep, unrealistic timelines, and the fundamental mismatch between blockchain’s strengths and the requirements of a high-frequency clearing system. ASX ultimately wrote off the entire investment and reverted to a conventional technology approach for the replacement.
The most common causes of enterprise blockchain project failure are governance disputes (35% of failures), inability to achieve network adoption (30%), poor problem-solution fit (20%), technical issues (10%), and regulatory blockers (5%). Technical failure is actually the rarest cause. Most projects fail because organizations skip the hard questions about governance structure, participant incentives, and whether blockchain genuinely solves a problem that existing technology cannot. Projects that succeed typically start with a specific measurable problem and have a dominant entity that can drive adoption.
We.trade was a European banking consortium blockchain platform for trade finance that dissolved after failing to achieve commercial viability. Despite backing from major banks including HSBC, Deutsche Bank, and Societe Generale, the platform could not attract enough SME users to justify operating costs. The consortium structure led to slow decision-making, conflicting priorities among member banks, and inability to iterate quickly. The platform entered liquidation after banks withdrew funding when transaction volumes remained too low to sustain operations.
Successful blockchain projects share common traits: they start with a specific, measurable problem rather than adopting blockchain for its own sake. They design governance structures before writing code. They ensure there is either a dominant entity that can mandate adoption or a small group of tightly aligned participants. They measure success by operational improvements, not technology deployment milestones. Before starting any blockchain project, organizations should verify that the problem requires shared state across trust boundaries, that participants have genuine incentives to join, and that a centralized database cannot solve the same problem more simply.