The House committee's subpoena of Larry Ellison wasn't about a database glitch. It was about a $10 billion promise that dissolved into a decade of delays. Congress doesn't summon CEOs for paperwork errors. They summon them when the narrative of progress collides with the reality of structural decay.
This isn't a story about Oracle's stock price. It's a story about the architecture of trust in digital infrastructure—a theme that echoes far beyond the Beltway and into the very foundations of our industry. We build systems that claim to eliminate intermediaries, yet here we witness the ultimate intermediary—the state itself—failing to manage its own digital backbone. The irony is thick enough to choke on.
Let's call this what it is: a referendum on centralized digitization. When the Department of Veterans Affairs signed a contract with Cerner in 2018 for a new Electronic Health Record (EHR) system, the goal was modernization. Replace the aging VistA system, built in the 1990s, with a commercial product that promised interoperability and efficiency. The contract was worth billions. The timeline was ambitious. The execution, as we now know, was catastrophic.
By 2023, the VA had paused new site go-lives. The full deployment, originally slated for 2024, is now a distant mirage. Costs have ballooned. Clinical errors have been reported. Doctors are frustrated. Veterans are caught in the crossfire. And now, Larry Ellison, the architect of Oracle's acquisition of Cerner, is being called to account.
The core insight here is not about Oracle's technical failure. It's about the failure of a specific governance model—one that relies on a single, monolithic vendor to deliver a mission-critical system for millions of people. This is the same governance model that underpins much of traditional finance and government IT. It's a model built on trust in institutions, not on verifiable code. And when that trust is broken, the consequences are not abstract. They are measured in patient safety, in delayed care, in the erosion of public confidence.
Having spent years in the digital asset space, I've seen this pattern before. In 2020, I traced over $50 million in liquidity flows into early Compound Finance deployments. The rewards weren't organic demand; they were printed incentives. The system looked vibrant until you audited the underlying structure. The same principle applies here. The EHRM project looked like progress on paper—a roadmap, a timeline, a vendor with a big name. But the underlying structure was brittle. The incentives were misaligned. The checks and balances were insufficient.
What does this have to do with cryptocurrency? Everything. The crypto narrative has long been built on the promise of transparency, on the idea that 'code is law.' Yet, we are watching a $10 billion centralized IT project fail precisely because it lacked the transparency and verifiability that blockchain technology offers. The failure of the VA EHRM project is a case study in what happens when you have opacity, centralized control, and a single point of failure. It's the antithesis of the decentralized ethos.
Consider the governance architecture. The VA contract is governed by the Federal Acquisition Regulation (FAR), the Health Insurance Portability and Accountability Act (HIPAA), and the Federal Information Security Management Act (FISMA). These are robust frameworks on paper. But they are enforced through audits and oversight—processes that are reactive, slow, and often captured by the very entities they are meant to regulate. In contrast, a blockchain-based system would have an immutable audit trail. Every change, every update, every access to patient data would be recorded on a distributed ledger, visible to all authorized parties. The 'proof of work' wouldn't be a buzzword; it would be a literal record of system integrity.
The contrast between the centralized failure and the decentralized promise is stark. What looks like a niche government IT story is actually a macro-level argument for the adoption of verifiable, decentralized infrastructure. The skeptics will say that healthcare data is too sensitive for a public blockchain. They are right. But the answer isn't to retreat to centralized opacity. The answer is to build permissioned blockchains, zero-knowledge proofs, and distributed identity solutions that provide the auditability of a public ledger while maintaining the privacy required by HIPAA. The technology exists. The political will is what's lacking.
My contrarian take, however, is this: decentralization is not a silver bullet. The failure of the EHRM project is not solely a failure of centralization; it is a failure of accountability and governance. A DAO could easily run a healthcare system into the ground if its incentives are misaligned. In 2025, I advised a startup on a $30 million token launch that wanted to exploit regulatory gray areas for cross-border liquidity. I refused to approve the structure, citing ethical concerns about regulatory arbitrage and consumer harm. That decision cost me a client but it affirmed a principle: the structure must serve the human outcome, not the other way around. Technology is just a tool. The governance architecture, the incentive design, and the culture of accountability are what determine success or failure.
The same applies to Oracle. Blockchain or no blockchain, the fundamental issue is that we need systems where failure is visible, where accountability is enforced, and where the users—in this case, veterans and clinicians—are prioritized over vendor profits. The silence between the project milestones, the quiet months where nothing gets reported, that is where the illusion of progress dissolves. What looks like noise—the delays, the cost overruns, the reports of clinical errors—is often a pattern. And the pattern here is a systemic failure of oversight.
So, where do we go from here? The House committee's scrutiny is a step, but it's a step within a broken paradigm. We need to fundamentally rethink how we procure and manage mission-critical digital infrastructure. We need to move from a model of 'trust but verify' to a model of 'verify, then trust.' The bridge stands only when foundations are sound. And the foundation of any digital system is not its code, but its governance.
The crypto industry has an opportunity here. We can step out of our echo chamber and offer solutions to these real-world problems. We can show that the principles of transparency, decentralization, and incentive alignment aren't just for speculative assets—they are solutions for the most pressing challenges in the public sector. Structure survives where sentiment fades. The sentiment in Washington is that Larry Ellison must answer for his company's failures. The structural question is whether we will learn the deeper lesson about the fragility of centralized systems.
This hearing is not the end. It's the beginning of a longer conversation about who is responsible when digital infrastructure fails. Will we hold the individuals accountable—the CEOs, the project managers, the government officials who signed off on bad decisions? Or will we finally address the systemic architecture that allows these failures to occur?
As I watch this unfold, I'm reminded of a principle I've learned in my years auditing both DeFi protocols and traditional financial systems: the illusion of liquidity dissolves in silence. The illusion of progress is similar. It persists only when no one is asking the hard questions. The House committee is asking them now. It's our job, as builders and observers, to ensure the answers lead to structural change, not just a temporary scapegoat. The bridge between capital and conviction is built on trust. And trust, in the end, is the only asset that truly matters.