The $51.8 Billion Line Item: Reading Anthropic's IPO Prospectus Like a Smart Contract Auditor

CryptoCred
Video

The number is $51.8 billion. That is the figure a circulated summary of Anthropic's IPO prospectus attributes to the company's "future cloud, compute, and infrastructure commitments" over the coming year. I read it three times. Then I did the arithmetic any smart-contract auditor runs before signing off on a treasury module: commitment divided by revenue. Fifty-one point eight billion against 4.59 billion in annual revenue. A ratio of 11.3.

For a company that has raised something in the neighborhood of $30 billion cumulatively, that line item is not a strategy. It is a solvency question. And solvency questions are the work I do. I do not trade AI equities. I do not cover IPOs. I spend my days inside proving systems β€” Groth16 circuits, elliptic-curve pairings, the specific discipline of a zkSNARK where one wrong constraint voids the entire proof. But when a financial document makes a claim that cannot be independently verified, it stops being a financial document and becomes a trust assumption. Trust assumptions are the thing blockchains were invented to remove, and the thing most blockchains quietly reintroduced the moment it became convenient.

So I read the Anthropic prospectus summary the way I read an unaudited protocol. Not as an investor. As a skeptic with a calculator in one hand and a threat model in the other. What follows is not investment advice. It is a forensic read of a document that describes the largest compute commitment in the history of private capital, in a market where the people paying for that compute have no on-chain way to check whether the number is real.

Context: what the document actually says, and what it refuses to say

Anthropic is heading toward a public listing. The prospectus summary that reached me β€” through a secondary outlet, which I will flag immediately β€” reports audited-looking figures for the fiscal year ending December 31, 2025: revenue of $4.59 billion, up 1,088% year over year; an operating loss exceeding $8 billion; a concentration where two customers account for roughly 25% of revenue; and that $51.8 billion infrastructure commitment. It is a three-handed document. No prospectus link. No disclosed valuation. No named underwriters.

That last set of omissions matters more than any single number. In an S-1, the underwriters are named because their reputations are on the line for the accuracy of the financials. A summary that strips the underwriters, strips the valuation, and strips the source link is, structurally, an unverified claim. An unverified claim in a capital document is not a disclosure. It is marketing wearing a disclosure's clothes. I want to be careful here, because the substance underneath may still be accurate. But accuracy and verifiability are different properties, and only one of them can be checked. Math doesn't negotiate on this point: either you can recompute the number from primary data, or you are trusting whoever wrote the summary.

Before going further, I have to do what I would do to any protocol before analyzing its economics β€” triage the data quality. Because every conclusion downstream inherits the defects upstream. I found three anomalies that do not survive contact with public knowledge.

The first is the revenue growth. A 1,088% increase implies a 2024 base of approximately $386 million. Public reporting around Anthropic through 2024 put revenue closer to $1 billion. The gap is roughly 2.6x. That is not rounding. It is a different number. The most likely explanation is a basis mismatch β€” the figure may represent a specific business line, an annualized run-rate at a particular moment, or a revenue definition that excludes something the public numbers include. When a growth rate implies a base that contradicts every other public source, the rate is telling you about the reporting convention, not about the business.

The second is the infrastructure commitment. Five hundred eighteen billion dollars in forward commitments, against a company that has raised tens of billions and earns single-digit-billion revenue, exceeds its capacity to pay by an order of magnitude. That does not mean the number is fake. It means the number is not what it appears to be. It is probably a multi-year cumulative maximum, a set of option-laden agreements where the headline figure assumes every option is exercised, or a mistranslation of a much smaller annual obligation. In a smart contract, this distinction is the entire game. A function that commits maxAmount and a function that commits amount are different functions, and the first one can drain a treasury that the second one cannot.

The third is the loss figure. An $8 billion-plus operating loss on $4.59 billion of revenue implies an expense ratio above 270%. That is far beyond the known burn profile of frontier AI labs unless it includes enormous stock-based compensation, one-time write-downs, or depreciation on hardware that the company does not yet own outright. Loss structure matters because it separates cash burn β€” the thing that kills companies β€” from accounting burn, which is painful but survivable.

I flag all three because the rest of this analysis assumes the numbers are directionally accurate. If they are not, the conclusions soften but the structural warnings do not. The pattern is legible even when the digits are suspect.

Now, why does a zero-knowledge researcher care about any of this? Because the shape of Anthropic's disclosures is the shape of a system that has no verifiable state. Every claim in it β€” revenue, commitments, losses β€” is asserted by a central party and checked by an auditor whose work product is not public. That is the exact architecture that blockchains replaced, and it is the exact architecture that the AI compute boom is now rebuilding at trillion-dollar scale. I have spent the last year building circuits to verify off-chain AI model outputs precisely because "the model said so" is not an acceptable trust assumption. Anthropic's prospectus is the same problem one layer up: "the company said so" is not an acceptable trust assumption either. And unlike a smart contract, no one can fork the prospectus.

Core: the four structural facts that survive the noise

Strip the digit-level uncertainty and what remains are four structural facts. They are the ones I would write into a risk memo. They are also the ones a public market will have to price, whether or not it understands them yet.

Fact one is customer concentration with a twist. Two customers account for roughly 25% of revenue. On its face that is a standard concentration risk. But the identity of the customers is the real story. The most reasonable inference β€” and I will show why it is more than an inference β€” is that these are the hyperscalers that both invest in Anthropic and distribute its models: Amazon through AWS Bedrock, Google through Vertex AI. If that holds, then a quarter of Anthropic's revenue is not customer revenue. It is channel revenue. It is money that flows because the company's own shareholders are also its resellers.

I have seen this pattern before. In 2022 I audited a DeFi lending protocol whose largest "depositor" was its own treasury, routed through a separate contract. The balance sheet showed deposits and the deposits were real, but the deposit was circular. It was the protocol lending to itself and booking the interest as organic growth. When the incentive program ended, the deposit left in a single block. Channel-bound revenue is circular revenue, and circular revenue unwinds the moment the player that closes the loop changes its incentive.

Fact two is the absence of long-term contracts. The prospectus reportedly warns that many of the largest customers have not signed long-term agreements. This is the single most important sentence in the document, and it is buried. It means Anthropic's revenue β€” the thing the growth rate is computed on β€” has near-zero visibility. Compare it to a SaaS business, which typically reports 80% or more of revenue as recurring and contractually committed. Anthropic's revenue can be reduced by a competitor's pricing move or a partner's strategic pivot, and there is no contractual mechanism to stop it. In an on-chain treasury, I would model this as a position with no time-lock and no vesting. You do not extrapolate it forward. You haircut it to the quarter.

Fact three is the infrastructure commitmentε€’ζŒ‚ β€” the inversion I opened with. If a company commits $51.8 billion and earns $4.59 billion, the commitment is the dominant fact of the business, not the revenue. Every dollar of that commitment has to be financed, and financing it means either dilution, debt, or a bet that revenue grows fast enough to service it. In a smart contract, an outsize commitment against thin reserves is a liquidation risk. The liquidator does not care about the growth story. The liquidator only cares that reserves are insufficient at the moment of demand. A commitment is a liability the instant it is signed. Revenue is a hope until it is collected.

Fact four is what the document refuses to say about the technology itself. There is no architecture detail. No model version. No parameter count. No context window. No alignment methodology. The only technical language is "transformative artificial intelligence" β€” a phrase that could describe a paper clip optimizer or a chatbot, and does not distinguish between them. This is deliberate. An S-1 is a legal document, and companies keep competitive secrets out of legal documents. But it means the entire investment case rests on the ability to turn a technical capability into a commercial moat, and the document discloses nothing about the moat. For a company valued at the frontier of AI, the near-total absence of technical disclosure is itself a disclosure: it tells you that the differentiation is either not technical, not durable, or not yet real.

Let me connect this to something concrete I built. In 2026 I designed a circuit to prove that a specific AI model output came from a specific model, trained on a specific dataset, with weights that had not been tampered with. The point of the exercise was to eliminate the very trust assumption the Anthropic document relies on. If you can prove an inference was run correctly β€” input authentic, weights authentic, execution authentic β€” then the output is verifiable, and you do not need to trust the model operator. But the frontier labs are moving in the opposite direction. They are building systems whose internal state is proprietary, whose training data is undisclosed, and whose outputs are asserted rather than proven. An industry that asks for capital on the basis of unverifiable claims should not be surprised when the market eventually asks it to prove them.

And here is the part that ties to my own field's worst habits. The crypto industry spent a decade marketing verifiability and then abandoned it wherever it was inconvenient. LayerZero's cross-chain messaging still leans on an oracle and a relayer β€” two trusted parties whose honesty is the entire security model, dressed up as decentralization. Dozens of Layer2s launch with the same small user base, slicing scarce liquidity into ever-smaller fragments and calling it scaling. And the AI industry, arriving late to the capital markets, is importing the same pathology at a larger scale: commitments without collateral, revenue without contracts, capability claims without proof. The two industries are converging on the same failure mode, from opposite directions. One abandoned verifiability for speed. The other never had it to begin with.

The verifiability gap: why the numbers cannot be checked

I want to be precise about what is actually wrong here, because it is easy to mistake a data-quality complaint for a systemic critique. The systemic critique is this: the modern AI company has no verifiable financial state, and it has no verifiable technical state, and both gaps are structural rather than incidental.

Start with the financial side. When a public company reports revenue, it does so under accounting standards enforced by an auditor and a regulator. When a private AI company pre-IPO describes its numbers in a leaked summary, none of that enforcement is visible to the reader. You cannot recompute the revenue. You cannot inspect the commitments. You cannot reconcile the loss. You are, functionally, reading a dashboard that the operator assembled and screenshotted. That is not a criticism of Anthropic specifically. It is a description of the information asymmetry between a company and its prospective investors, and that asymmetry is largest exactly where the numbers are most exciting.

Now the technical side, which is the part that should worry anyone who thinks the AI compute boom is an infrastructure story. The boom is financed by the assumption that these models will keep getting better and that the demand for them will keep growing. That assumption is not verifiable from the outside. There is no proof that a given training run produced a given capability. There is no attestation that a model's weights are what its deployer claims. There is no public record of how much compute went into a benchmark result that a research team published to win a customer. The entire investment thesis rests on claims that cannot be independently checked, and the industry's own participants are the only ones who can check them.

I built the primitive that would close part of this gap. A zero-knowledge proof of inference. The idea is old in cryptography and new in AI: prove that y = f(x; w) for a committed function f, a committed input x, and committed weights w, without revealing x or w. If you can do that at scale, then a model operator can prove that a claimed output is genuine, and a customer or regulator can verify it without trusting the operator. That is the difference between a pinky promise and a proof. It collapses the trust assumption to mathematics. Math doesn't negotiate. A proof either verifies or it does not.

We are not there yet at frontier scale. Proof generation for large models is expensive, and the industry has optimized for capability rather than provability for a decade. But the direction is unambiguous, and the direction is the point. The first AI company that publishes a verifiable inference standard β€” a way for any counterparty to check its outputs β€” will not just have better compliance. It will have a moat that no competitor can copy without publishing their own weights. The trust assumption becomes the product.

Here is the contrarian turn I want to make explicit, because it is the one that will annoy both camps. The crypto industry loves to criticize AI for centralization. That criticism is correct and it is also hollow, because crypto solved verifiability for money and then threw it away everywhere else. The industry that should have the most credibility on trust-minimized systems is the industry that runs on the most trusted systems in practice. Bridges are trusted. Oracles are trusted. Stablecoin reserves were trusted until they weren't, and when they weren't, the entire market learned in a weekend what an unaudited promise is worth. Code is law, but bugs are reality β€” and so is a bank run.

So when I look at Anthropic's prospectus and see an $8 billion loss sitting next to a $51.8 billion commitment, I do not see an AI problem or a crypto problem. I see the same problem both industries have: a claim that is cheaper to make than to prove, made by an operator who benefits from the reader not checking. The reader who checks is the only one who survives the unwind.

How to actually read the document (a working threat model)

I do not want to leave this as abstraction. Here is the working model I used, and the questions I would ask if I were on the other side of the table. I lay them out the way I lay out a contract audit β€” threat first, then control, then residual risk.

Threat: the revenue is not owned, it is routed. Control: find the contract. Ask whether the top two customers have usage commitments with minimum spend and termination penalties. If the answer is no, treat the revenue as variable. Residual risk: high, because the customers are also shareholders, and shareholders can be patient in a way customers cannot β€” until they are not.

Threat: the infrastructure commitment is a maximum, not a floor. Control: find the actual obligation. Distinguish maxAmount from amount. Ask what happens if the company exercises less than the maximum. If the penalty is a take-or-pay clause, the commitment is real and the solvency question is real. If it is an option, the headline is inflated and the actual risk is smaller than it looks. Residual risk: unknown until the clause is read, which means the summary is useless for this purpose.

Threat: the loss is accounting, not cash. Control: separate stock-based compensation from operating cash burn. Stock comp is a transfer from future shareholders to current employees. It is real in the sense that it dilutes, and it is not real in the sense that it does not leave the bank account. If most of the loss is comp, the company is a talent-burn story, not a cash-burn story. If most of it is cash, the runway question is live. Residual risk: this single distinction determines whether the company is a decade-long bet or a two-year emergency.

Threat: the technical moat is asserted, not shown. Control: there is no control. The document does not disclose the means by which the company intends to remain differentiated. That is the residual risk the investor cannot price, because the prospectus does not give the inputs to price it. When a valuation is dominated by an intangible the document will not describe, the market is pricing a narrative, not a business.

I want to dwell on that last point, because it is the one that generalizes. In 2024 I audited the custodial wallet architecture behind an institutional Bitcoin product. The public marketing described multi-signature security and institutional-grade custody. The actual key-share distribution had a single point of reconstruction β€” a threshold that could be met by a correlated group. I reported three attack vectors privately. None of them were in the marketing. The gap between the claim and the implementation was the entire security surface. I learned then that the most dangerous part of any product is the part that is described rather than demonstrated. Anthropic's prospectus is the same phenomenon at equity scale. The differentiation is described. It is not demonstrated.

There is a further angle that only a privacy person would flag. The document's omissions are not just competitive; they are structural. A company that refuses to disclose its model architecture, its training data, and its alignment method is, in effect, asking investors to buy a black box. Black boxes are fine when you control the key. They are catastrophic when you are the counterparty. This is the mirror image of the compliance problem I worked on in 2025 β€” building zero-knowledge proofs that let a DeFi protocol verify creditworthiness without exposing personal data. Privacy is a feature, not a bug, in that context, because the proof lets you have both. But privacy without verification is just opacity. Anthropic has the opacity and not the proof. That is the asymmetry the market has not yet priced.

The contrarian read: this is a crypto document wearing an AI label

Here is the part that will get me in trouble with both the AI crowd and the crypto crowd, so let me say it plainly. The Anthropic prospectus, as summarized, is structurally identical to a token launch in a bear market. Let me count the similarities, because the pattern is not a coincidence β€” it is a template.

A token launch raises capital against a narrative. An AI IPO raises capital against a narrative. The token's revenue is often routed through the issuer's own ecosystem. The AI company's revenue is partly routed through its own investors' clouds. The token's largest holders are also its largest users. The AI company's largest shareholders are also its largest customers. The token's commitment to "future development" is a maximum that rarely gets spent. The AI company's "infrastructure commitment" is a maximum that may not be a floor. The token's valuation is set by the last marginal buyer. The AI company's valuation is set by the last marginal round. And in both cases, the retail participant reads a summary written by someone who benefits from the summary being believed.

I spent three weeks in 2021 dissecting Anchor Protocol's contracts after the LUNA collapse. I traced the withdraw function logic and found the integer overflow in the redemption oracle that amplified the death spiral. The lesson was not that the mechanism was evil. The lesson was that a financial model is only as secure as the code underneath it, and the people reading the marketing were not reading the code. The same discipline applies here. The number in the leaked summary is the marketing. The clause in the actual prospectus is the code. If you cannot read the code, you are not investing. You are guessing.

Now the deeper contrarian point, the one that matters beyond Anthropic. The AI industry is converging on crypto's worst habits precisely as crypto is trying to shed them. Crypto learned, expensively, that promises without proofs get liquidated. Bridges got hacked because trust assumptions were hidden in the architecture. Stablecoins got run because reserves were not attested. Lending markets froze because collateral was rehypothecated off-chain. Each of those failures produced a verifiability upgrade: attestations, proofs of reserves, on-chain collateral accounting. The AI industry is now building the same fragile architecture β€” unverifiable compute commitments, circular revenue, opaquely defined moats β€” at a scale that dwarfs the DeFi crisis by an order of magnitude. And unlike DeFi, there is no liquidation engine that clears the position cleanly. There is just a stock that gaps down and a set of private commitments that someone has to eat.

I do not say this to be dramatic. I say it because the pattern is legible to anyone who has watched a leveraged system unwind. Liquidity fragmentation isn't a real problem β€” it is a narrative VCs use to sell the next product. The AI compute buildout is the same move at a larger scale: the narrative of inevitable demand is used to justify commitments that the demand has not yet proven it can service. When the demand arrives, the commitments are vindicated. When it does not, the commitments are the mechanism of the unwind. There is no third outcome. Math doesn't negotiate.

And the crypto parallel is not just analogy. It is structural. Layer2s fragmented liquidity and called it scaling. AI labs are fragmenting compute commitments and calling it infrastructure. Both moves convert a scarcity problem into a marketing problem, and both defer the bill to a counterparty who cannot see it coming. The LayerZero model β€” two trusted parties underwriting the entire security of a "trustless" bridge β€” has a direct analogue in an AI company's reliance on two customers underwriting a quarter of its revenue while also owning its equity. Trust is computed, not given, and it is not computed by the parties who profit from it.

What a verifiable AI infrastructure would look like

I want to end the analysis with the constructive version, because criticism without a blueprint is just noise, and I am not in the business of noise.

A verifiable AI company would publish a commitment to its model weights β€” a hash on a public ledger β€” so that any inference can be checked against the committed weights. It would run inference inside a verifiable compute environment β€” a TEE, a ZK circuit, or a threshold MPC arrangement β€” so that the output is provably the result of the committed model on the committed input. It would attest its compute usage on-chain, so that the infrastructure commitment is a measured fact rather than a headline number. It would structure its revenue contracts with minimum spend and public, hash-committed terms, so that concentration is visible to anyone, not just to the underwriter. And it would submit to periodic proofs of reserves for its compute obligations, the same way an exchange proves its Bitcoin holdings.

None of this is science fiction. Every component exists. ZK proofs of inference are in prototype. TEE-based attestation is in production. On-chain commitments are a solved problem. The reason it is not standard is not technical. It is that the companies benefiting from opacity have no incentive to adopt it, and the companies buying their equity have no leverage to demand it. That is a market failure, and market failures of this kind are corrected by the same thing that corrected them in crypto: a blow-up, followed by a mandate.

I have audited enough of these systems to know the sequence. The claim gets made. The claim gets believed. The claim gets leveraged. The claim gets tested. The claim fails, and the failure is disproportionately expensive because it was unverified for so long. Then a standard emerges, and everyone pretends they always wanted it. I have seen this in stablecoin reserves, in bridge security, in custodial key management. I have no reason to believe AI equity will be different. The only question is timing, and timing is the one variable that cannot be audited in advance.

Takeaway: the vulnerability forecast

So here is my forward-looking read, offered with the caveat that I am not an investor and this is a threat model, not a forecast.

The Anthropic prospectus summary, whatever its numerical defects, describes a class of company that will define the next market cycle: high growth on thin, concentrated, uncommitted revenue; massive forward commitments against modest reserves; undifferentiated technical disclosure; and no verifiable state at any layer. That company can work, if the demand arrives and the commitments get serviced. It can also fail catastrophically, if the two customers that supply a quarter of revenue decide to build the model themselves, which they are already positioned to do. The document does not tell you which outcome is coming. It only tells you that no one outside the company can check.

That is the vulnerability. Not the loss, not the commitment, not the concentration individually. The vulnerability is the absence of a verification layer over all of them. When the number cannot be recomputed, the risk cannot be priced, and when the risk cannot be priced, it is allocated to whoever reads the summary last. That is not a market. That is a queue.

And so the question I will leave on the table, the one I will be asking every AI founder and every exchange listing the next AI token: if you are going to ask the public to believe your numbers, why are you not proving them? Code is law, but bugs are reality β€” and an unverified claim is the oldest bug there is. Silicon is patient. The market is not.