In 2020, Ripple's board voted to dissolve the company. The plan was to distribute its massive XRP holdings to shareholders and walk away—effectively killing the protocol's primary steward. It almost happened. For those of us who have spent years auditing the intersection of code and governance, this revelation is not just a historical footnote; it is a stress test of the very principles we claim to champion. We assume that decentralized protocols, once launched, become immune to the whims of their creators. But XRP's fate hung on a single board decision, made behind closed doors, far from any consensus mechanism.
Let me rewind the context. In December 2020, the U.S. Securities and Exchange Commission (SEC) filed a lawsuit against Ripple Labs and its two top executives, Brad Garlinghouse and Chris Larsen, alleging that XRP was an unregistered security. The market reacted with panic: exchanges delisted XRP, liquidity dried up, and the price collapsed. For two and a half years, the entire XRP ecosystem existed in a state of legal paralysis. During that time, I was in Copenhagen, watching from a distance as friends and colleagues debated whether the project could survive. What few appreciated was that behind the legal maneuvering, a far more fundamental battle was being fought—one that pitted the very survival of a company against the long-term health of a protocol.
Truth is not what is seen, but what is trusted. This was the first lesson I internalized during my years working on privacy-focused payments in Berlin, where we integrated ZK-SNARKs for transaction verification. We thought the technology alone would earn trust, but we quickly learned that trust is built through demonstrated resilience in the face of existential threats. The Ripple board's near-decision to dissolve is a perfect case study of that principle. The protocol's code was secure, its consensus algorithm was battle-tested, but the trust that sustained the ecosystem depended on the judgment of a few individuals who had the courage to say, 'We will not let this kill us.'
To understand why the dissolution was even considered, you must appreciate the pressure Ripple faced. The SEC was not just suing the company; it was personally suing Garlinghouse and Larsen, demanding millions in penalties and threatening to bar them from serving as officers of any public company. Legal fees had already exceeded $200 million. The company had received legal advice that it could lose the case entirely. In that dark moment, the board had a fiduciary duty to consider the worst-case scenario. The dissolution plan—return all XRP to shareholders and let the network fend for itself—was a rational, if cold, business decision. It would have preserved value for investors while severing Ripple's liability. But it would have also left the XRP Ledger (XRPL) without its primary developer, its institutional sales channel, and its roadmap for upgrades like the Automated Market Maker (AMM) and EVM-compatible sidechains.
This is where the decentralization paradox emerges. XRP has long been criticized for its centralization—the company holds a significant portion of the token supply, and Ripple's validators have historically exerted disproportionate influence. Yet it is precisely this centralization that allowed a small group to make a swift, decisive choice. A fully decentralized DAO, with thousands of token holders squabbling over proposals, might have debated for months while the SEC drained its treasury. The existential threat demanded a single throat to choke, and Ripple's leadership—flawed as any human institution—was that throat. In the 2022 DeFi collapse, I witnessed similar moments. When lending protocols faced insolvency, the ones that survived were often those with a strong core team willing to make unilateral emergency decisions, not the ones that deferred to slow governance processes. This is an uncomfortable truth for the purist decentralization narrative: sometimes, centralized governance is the most resilient structure in a crisis.
Truth is not what is seen, but what is trusted. Consider the irony: Ripple's near-death experience was caused by a regulator claiming to protect investors, but the most significant harm would have come not from a court ruling, but from a corporate dissolution. The SEC's strategy was to make the personal cost so high that the founders would rather shut down than fight. It almost worked. The fact that Garlinghouse and Larsen chose to fight—despite personal risk and financial strain—reveals something deeper about the relationship between founders and their creations. I saw this same tension when I worked on decentralized identity protocols integrated with AI reputation scoring. The ethical board I helped convene had to decide whether to override algorithmic outputs to prevent bias. That was not a question of code; it was a question of stewardship. The founders of Ripple, whatever their faults, ultimately saw themselves as stewards of a vision larger than their own balance sheets.
The partial victory in July 2023—when Judge Analisa Torres ruled that XRP is not a security in programmatic sales—was a watershed moment. The market celebrated, but the real victory was that Ripple chose to survive. The ruling provided a legal foundation for XRP to continue trading on U.S. exchanges, but it also exposed the vulnerability of the entire industry. How many other projects are one lawsuit away from their board deciding to dissolve? When I was building a custody solution for a Nordic fintech firm, the executives kept asking: 'What happens to the asset if your company goes bankrupt?' That question is now central to every institutional due diligence. Ripple's survival offered an answer: 'This company faced the worst-case scenario and chose to fight, not flee.' That is the kind of trust that cannot be encoded into a smart contract.
Now, let me introduce the contrarian angle, which I have learned to embrace as a realist. The near-death experience might have made Ripple stronger, but it also exposed a dangerous illusion. The idea that XRP is 'decentralized enough' to survive without its company is demonstrably false. The protocol is inextricably linked to Ripple's business relationships, its custody solutions, its integration with banks and central banks. Without Ripple, the XRP Ledger would become a ghost chain, slowly deteriorating as validators lost incentives and developers migrated to more active ecosystems. This is not a critique of XRP alone; it applies to virtually every Layer-1 protocol that has a single dominant corporate sponsor. We celebrate Bitcoin for its anarchic resilience, but that came at the cost of slow innovation. For networks like XRP, where institutional adoption is the core value proposition, the company is the protocol's immune system. When that immune system is attacked, the entire organism is at risk.
Moreover, the 'ETHGate' controversy—the suspicion that the SEC treated Ethereum favorably due to political connections—reveals a deeper systemic rot. Even if the theory is unproven, the belief that regulatory outcomes depend on who you know rather than what you build erodes the foundation of trust that decentralized systems require. I have seen this firsthand in conversations with regulators in Europe and the U.S. They are often well-intentioned, but they operate under conflicting mandates and political pressures. The Ripple case should not be seen as a victory for the industry; it should be seen as a warning that the regulatory landscape is inherently unstable. The next SEC chair could reverse course, target other tokens, and force more boards to consider dissolution. Until we have clear legislation that defines the boundaries of securities law for digital assets, every project operates on a knife's edge.
Truth is not what is seen, but what is trusted. This brings me to the forward-looking takeaway. The XRP story is not about triumph; it is about the cost of survival. It forces us to reconsider our assumptions about protocol independence. The next generation of decentralized systems must design governance that can withstand regulatory assault without resorting to dissolution. This means embedding legal resilience into the code itself—not just through smart contracts, but through structures like decentralized legal entities (e.g., Swiss associations or Wyoming DAO LLCs) that separate corporate liability from protocol governance. It means building treasury management strategies that can fund multi-year legal battles without diverting resources from development. It means cultivating a culture where founders are willing to take personal risks, but also have the support of a community that will stand with them.
When I organized the Copenhagen Consensus summit in 2026, bringing together regulators, developers, and civil society, the one lesson that everyone agreed on was this: the future of decentralized systems depends on our ability to write not just code, but constitutions. Constitutions that define how power is distributed, how crises are managed, and how the line between human judgment and algorithmic rule is drawn. Ripple's near-death experience provides a living example of what happens when that constitution is missing. The board room vote to dissolve was a failure of governance architecture as much as a failure of regulatory clarity.
So, what do we do? We stop pretending that decentralization is a binary state. We stop demonizing central coordination as inherently corrupt. We start designing systems that acknowledge the need for resilient human institutions to protect fragile digital ones. The XRP story is a blueprint for how to survive a regulatory existential threat, but it is also a cautionary tale about the cost of starting with a governance void. As I wrote in my manifesto on Ethical Yield, 'Real value emerges from real trust.' And trust, as Ripple's board discovered, is not a feature you can ship in a patch. It is earned through years of calm and through moments of crisis. The day XRP almost died, it lived to teach us a lesson. I, for one, am listening.