There is a specific kind of silence that a non-disclosure agreement buys. It is not the silence of secrecy — that would be too crude, too legible. It is the silence of negotiated forgetting: the property tax abatement that never surfaces in a press release, the electricity rate approved by a utility board at eleven o'clock at night, the water rights transferred without a single line in the local paper. When reports surfaced that AWS moved to terminate a set of non-disclosure agreements with government agencies amid a widening push for data center transparency, the headline read like a corporate conscience clearing its throat. I read it differently. In a world of ledgers, who holds the memory? For a decade, the physical substrate of the cloud — the most consequential infrastructure of the modern economy — was governed by documents designed to be unreadable. And the industry that built its entire moral identity on radical transparency did not notice, because it was too busy refreshing its own charts.
Let me be precise about what we do and do not know, because the discipline of the audit begins with admitting the gaps. The report is thin: a handful of claims, no disclosed count of terminated agreements, no named agencies, no confirmation of whether the arrangements involved financial terms at all. That thinness is itself a data point. An event this consequential should not arrive as a paragraph. But the signal survives the noise, and the signal is this: the cloud is being forced, by environmental scrutiny and community pressure, to become legible.
To understand why a company would voluntarily surrender a legal instrument, you have to understand what the instrument was protecting. A hyperscale data center is not a building; it is a twenty-to-thirty-year financial commitment that lives or dies on its input costs. Power typically accounts for somewhere between thirty and fifty percent of operating expense at scale. Land, water for cooling, and local tax treatment shape the internal rate of return more than any engineering decision the company will ever make. That is the soil in which the NDA grows. Municipalities compete for these facilities with packages — abatements, favorable utility rates, expedited permits, water allocations — and companies negotiate them under confidentiality because disclosure invites competitors to demand the same terms, and voters to ask why the deal was struck in the dark. The NDA is not a privacy tool. It is a pricing tool.
Then came AI. The training and inference boom converted data centers from a mature, utility-like business into the most aggressive land-and-power grab in modern industrial history. When demand for compute outruns the supply of megawatts, the negotiating leverage tilts — but so does the scrutiny. Communities that once welcomed a tax base now organize against substation noise, aquifer draw, and diesel backup generators. This is the push the report gestures at, and it is not coming from Washington. It is coming from county boards and neighborhood associations, the most local and least negotiable form of regulation there is. Social license — the informal consent of the people who live next to your infrastructure — has become a hard constraint on cloud growth, and hard constraints are precisely what NDA structures are built to hide.
Here is where the crypto reader should stop scrolling.
For fifteen years, this industry has told a story about transparency. We put state transitions on a public ledger. We published whitepapers. We open-sourced clients. We built block explorers so that any user could verify any transfer. The story is true, and it is also, in the way that matters most, incomplete. Proof is binary; meaning is fluid. A block explorer shows you that a transaction occurred. It does not show you who decided it should occur, who held the multisig, which foundation signed the side letter, or what the validator set agreed to over a private call before the vote was staged on-chain. The chain is transparent. The governance is not. We built an architecture of radical legibility and then wrapped it in an organizational opacity that would make a hyperscaler blush.
I have spent time inside that gap. In 2017, during the peak of the ICO mania, I declined paid advisory roles to conduct an unpaid audit of a DAO governance framework. I found three reentrancy vulnerabilities in the governance contracts — the kind that would have let an attacker drain the treasury through a callback loop no dashboard would have flagged. Preventing that loss was not a technical triumph. It was a reminder that the exploitable surface is rarely where the marketing points. The dangerous code is almost always in the governance layer, in the upgrade keys, in the pause functions — the parts that are, by convention, undocumented. We code the trust, but we must audit the soul.
The AWS story is that same lesson, scaled to the size of a continent. What AWS was hiding behind its NDAs was not product data or customer secrets. It was the terms of its own existence: how much power it consumes, at what price, drawn from which grid, cooled by which watershed, subsidized by which taxpayers. Those are the protocol parameters of the physical cloud. And the crypto industry, which demands that every DeFi protocol publish its fee switches and every rollup publish its sequencer policy, has been conspicuously quiet about the fact that the compute beneath its own applications is governed by contracts no one can read.
Consider the oracle problem, which I have written about for years. Chainlink solves decentralization by distributing data feeds across nodes whose operator identities and incentives are, in practice, far more concentrated than the branding suggests. The lesson is not that the design is fraudulent; the lesson is that decentralization is a spectrum, and most of the industry lives comfortably in the middle of it while claiming the far end. The same critique applies to transparency. On-chain transparency is real but shallow. Off-chain transparency — the kind AWS is now being pressured to provide — is the deeper and more difficult layer, and it is the layer crypto has largely declined to build.
Now examine the decentralized compute narrative through this lens. DePIN projects — distributed storage, GPU marketplaces, wireless networks — sell themselves as the transparent alternative to the hyperscaler. The pitch is compelling: instead of a black-box data center, you get thousands of independent operators contributing hardware to a permissionless network, their contributions verifiable on-chain. But ask a harder question. Where do the largest DePIN operators get their power? Increasingly, from the same grids, under the same utility agreements, negotiated under the same confidentiality. A decentralized network can be transparent about its token emissions while being entirely opaque about its physical footprint. The protocol is neutral, but the user is human — and so is the substation.
This is why the AWS move deserves attention beyond the cloud-watcher crowd. If a centralized giant can be dragged toward disclosure by local pressure, then the decentralized infrastructure that aspires to replace it should be held to a higher standard, not a lower one. Yet the industry's own transparency practices are frequently theatrical. Foundations publish transparency reports that disclose token unlocks but not contributor contracts. DAOs stage votes after the outcome has been decided in a private governance call. Treasury multisigs are controlled by the same three people who wrote the proposal. None of this is visible on-chain, because the chain records the execution, not the deliberation. Transparency, in crypto, has become a performance of legibility rather than its substance.
There is a reason this matters beyond the balance sheet. In 2026, I helped lead a consortium of five stakeholders to design a decentralized identity framework for autonomous AI agents — a system meant to keep machine-to-machine interactions accountable to a public record. The hardest question we faced was not cryptographic; it was philosophical. If an AI agent transacts on behalf of a human, who is liable when it errs, and where is the record of the deliberation that produced the decision? We could build the identity layer. We could not build the accountability without a disclosure regime underneath it. The AWS case is the same problem in a different costume: the infrastructure that runs AI is exactly the infrastructure whose terms are least visible. If we cannot see the compute, we cannot audit the intelligence it produces. Transparency at the data-center layer is not a side issue for the AI era. It is the precondition for everything we claim to want to build on top of it.
I want to be careful here, because there is a contrarian reading that is easy to miss.
The instinct is to celebrate AWS's NDA retreat as a moral awakening. I do not buy it, and neither should you. Transparency, in concentrated markets, is a competitive instrument, not a virtue. Only a company with AWS's scale, switching costs, and government-customer stickiness can afford to volunteer for disclosure. Its public-sector clients cannot easily migrate — compliance certifications, data gravity, and security reviews make switching a multi-year project — so AWS can bear the cost of openness while smaller competitors cannot. And once regulators adopt AWS's disclosure posture as the industry standard, that standard becomes a barrier: a mid-tier cloud or a young AI-compute provider suddenly faces compliance costs it never budgeted for. The leader raises the bar and then clears it, leaving the field to stumble.
The crypto market has the same asymmetry, and the bear market is exposing it. Large protocols can afford the audits, the legal counsel, the disclosure frameworks. Small ones cannot, so they either stay opaque or they die. Transparency, in other words, is not distributed evenly; it is a function of runway. Survival, in a drawdown, is the precondition for accountability. A protocol that cannot fund a security review is not going to fund a governance one.
There is a deeper trap. On-chain data is abundant and nearly useless without interpretation. A wallet holds a token; a block explorer shows a transfer; a dashboard charts total value locked. But none of these tells you whether the number is real, whether the TVL is double-counted across recursive lending loops, whether the organic volume is wash-traded by the team's own market makers, whether the treasury is solvent after the next unlock. The transparency maximalists solved for data availability and never solved for legibility. We drowned the user in light and called it honesty. The AWS episode suggests the opposite discipline: the hard part is not publishing information, it is publishing the information that actually constrains power. That is what the NDAs were hiding, and that is what a genuine transparency regime would require the crypto industry to reveal about itself.
If I were running diligence on this story — and I would, before writing anything stronger — here is what I would track. First, whether AWS publishes an official statement naming the scope of the terminations, because the difference between several and all is the difference between symbolism and restructuring. Second, whether Azure and Google Cloud follow, because if they do not, AWS has handed its competitors a cost advantage in every future site negotiation. Third, whether state or local governments convert the voluntary gesture into mandatory disclosure law, which would turn a marketing move into an industry-wide cost floor. Fourth, whether any terminated agreement touched security-sensitive infrastructure, because that boundary is where transparency and national interest collide.
So watch the follow-through, not the announcement. If the NDA terminations are real and durable, they will show up in the boring places: county tax rolls, utility commission filings, water district minutes. That is where the truth about infrastructure always lives. The question for our industry is not whether AWS deserves credit. It is whether we will hold ourselves to the standard we demand of it. If the most centralized infrastructure company on earth is being forced to become legible, what possible excuse does a decentralized one have for staying dark? We are not moving money; we are moving belief. And belief, unlike a block, cannot be verified after the fact — only earned in advance.
