Three words carried the speech. Not "computing network." The words were may, beginning, and eventually.
I went back through the transcript after the headlines settled. Multiple outlets led with the same phrase โ blockchain has evolved from a simple ledger into a cryptographically secure computing network โ and none of them kept the conditional tense attached where it mattered. The claim that zero-knowledge proofs are already stitched into production protocol logic is stated flatly. The claim about fully homomorphic encryption is hedged once. The claim about indistinguishability obfuscation is hedged twice, and lands inside a sentence that opens with "in the future."
That is the entire article. A vaulted frame is announced at the top, and by the bottom of the same talk, its three pillars sit at three different distances from reality. Two of them have no timeline. One of them has an EIP number.
Markets do not price distance. They price the frame. Volatility is just liquidity leaving the room, and liquidity did not leave this room โ it never entered it. There was nothing to trade. What moved wasn't price. What moved was vocabulary.
I want to be precise about what this piece is and is not. This is not a verdict on the speech. It is a teardown of the gap between what was said and what a certain class of reader will hear. Trust is a variable I refuse to define โ so I read transcripts, not tone. I read the EIP tracker, not the applause.
***
The Frame and Its Venue
Context first, because the frame only makes sense against the timeline that produced it.
Ethereum's public self-description has moved through distinct phases, and each phase was a compression of a longer internal debate. Phase one: world computer. Phase two: the settlement layer for a rollup-centric roadmap. Phase three โ the current one โ the settlement layer that is also a verifiable computation network, with cryptographic privacy bolted on as a first-class property rather than an afterthought.
The shift from phase two to phase three is not cosmetic. It is a repositioning of the value claim. A ledger transfers value and records state. A network computes and proves. The first is a bookkeeping primitive. The second is a general-purpose substrate. If you accept the upgrade, Ethereum stops competing on transaction throughput and starts competing on cryptographic capability.
That distinction is doing more work in this speech than any single technical claim in it. Hold onto it.
The timing is not accidental. The rollup-centric roadmap is now mature enough to be boring, which is the highest compliment infrastructure can receive. Blob data landed. Fee markets for data availability exist and function. The scaling argument โ the one that consumed a decade of developer attention โ is transitioning from "unsolved" to "engineering." When a narrative goes from existential to settled, the people who live on narrative need a new leg to stand on.
Privacy and verifiability are the new legs. AI-adjacent tooling is the third.
I have watched this relay pattern for fourteen years of industry observation. Every mature infrastructure layer eventually runs out of scaling stories and reaches for capability stories. It is not deception. It is how technical communities sustain attention across multi-year build cycles. The problem is never the internal logic. The problem is the translation layer between a research agenda and a price signal.
There was no code release. No audit. No TVL figure. No token metric. No governance proposal. This was a directional address by an individual โ Vitalik Buterin, whose identity as co-founder gives his framing real roadmap gravity, but whose statements travel through the EIP process and core developer calls before they become protocol. Individual vision is not community consensus. Those are different machines with different latencies.
So what follows is a classification exercise. Not "is Vitalik right." Vitalik is mostly careful. The interesting question is what the framing intends, what the evidence supports, and where the reader is most likely to slip.
***
Three Distances from Reality
The speech presents a clean temporal gradient, and that gradient is honest. It is also the most useful thing in the whole talk once you see it.
Tier one โ zero-knowledge proofs. Described as already integrated into production protocol logic through actual EIPs. This is the strongest claim in the speech, because it is the only one with a paper trail.
Tier two โ fully homomorphic encryption. Described as "beginning to be applied." No performance figure. No project name. No hardware specification. One verb carrying the entire load.
Tier three โ indistinguishability obfuscation. Described as something that "may" find application in the future. This is not a roadmap item. It is a research aspiration with a philosophical tag attached.
Three tiers. One verb tense per tier. The verb tenses are the data.
I have spent enough time in audit rooms to recognize the pattern. When an engineer says "deployed," they can show you the commit. When they say "beginning to be applied," they are describing a laboratory that occasionally produces output. When they say "may," they are describing a paper they admire.
None of that makes the framing wrong. It makes the framing incomplete in a specific, measurable way. A reader who collapses the three tiers into one โ who hears "blockchain is now a cryptographically secure computing network" without separating the tiers โ has been sold a timeline that does not exist. And the collapse is easy, because the sentence structure does the collapsing for you.
I have seen this before, in the 2017 wallet breach I traced as an undergraduate. The marketing said "secure multi-signature storage." The transaction data said something else. Two compromised keys on a shared derivation path, and the whole architecture of promised security dissolved into an arithmetic fact on a block explorer. That was the week I stopped reading claims and started reading state. The habit never left.
A claim is not a capability. A capability is a deployed function with a track record. The distance between them is where most crypto losses live.
***
What "ZK in the EIPs" Actually Means
This is where the speech is strongest, and where it is most misread. Both things are true at once.
Zero-knowledge proofs have a genuine production footprint. But the phrase covers a family of things that are not equivalent, and the blur between them is where retail analysis goes wrong first.
The most concrete artifact is KZG commitments, deployed as part of blob-carrying transactions. When Ethereum shipped EIP-4844, it introduced a data availability mechanism where blobs of transaction data are committed to via polynomial commitments. The commitment scheme allows the network to verify that the data exists and is available without requiring every node to store it forever. This is a real, running, verifiable cryptographic construction. It is in production. It is not marketing.
But here is the part that gets lost. KZG commitments are not zero-knowledge privacy. They are data availability commitments built on polynomial machinery. The math family overlaps. The function does not. A KZG commitment proves something about a polynomial. It does not hide your transaction from anyone.
When a reader hears "ZK is already in the protocol" and concludes "private transactions are here," they have jumped from tier one to a tier that does not exist. Private transfers are a different construction with different costs and different trust assumptions. They exist in research and in application-specific circuits. They are not a base-layer default, and nothing in a blob commitment creates one.
This conflation is not exotic. I have watched it in my own work. In 2024 I ran a deliberate test: I attempted to inject an obfuscated logic flaw into a protocol during its fundraising window, to see whether automated analysis pipelines would flag it. The scanners read surface patterns. The flaw lived one layer down, inside a routing branch that only activated under a specific state combination. Automated tools missed it. It took a manual pass, tracing variable state across four functions, to surface the condition.
The same failure mode applies to narrative tooling. Automated reading catches the phrase and misses the construction. "ZK is in the roadmap" is a phrase. "KZG commitment for blob availability" is a construction. They are not the same object, and only one of them is verifiable today.
The genuinely progressive part of the speech is here, and it deserves recognition. Zero-knowledge systems have crossed from research into engineering. Proving costs are falling. Verifier gas costs are tractable. zkEVM designs are in production on multiple L2s. Recursive proofs have collapsed verification overhead. This tier is real, and the trajectory is honest.
The honest reading is narrower than the headline. The protocol adopted a zero-knowledge-family construction for data availability. It did not adopt zero-knowledge privacy as a default. Those are two different claims separated by about three years of engineering and several EIP cycles.
Zero-knowledge is the one leg of this stool that touches the floor. Remember which one it is.
***
The FHE Gap Is Not a Gap, It's a Canyon
Fully homomorphic encryption allows computation on encrypted data. The user encrypts, the server computes without ever seeing plaintext, the user decrypts the result. It is the closest thing cryptography has to a holy grail for privacy-preserving computation.
The speech says it is "beginning to be applied." I want to take that verb seriously, because the engineering reality behind it is a canyon, not a gap.
FHE schemes โ TFHE, BFV, BGV, CKKS, and their descendants โ all share one structural property: ciphertext operations are dramatically more expensive than plaintext operations. The overhead is not a constant factor. It is orders of magnitude, and it varies by operation type, by circuit depth, and by security parameter. Additive operations are cheap relative to multiplication. Multiplicative depth drives bootstrapping. Bootstrapping โ the operation that refreshes noise in a ciphertext so you can keep computing โ is the cost center, and it is not free by any measure.
Ciphertext expansion compounds the problem. A single encrypted value can occupy kilobytes where the plaintext occupied bytes. Storage and bandwidth costs scale with that expansion. Inter-node communication inside a computation graph scales with it too.
The practical consequence: FHE today is viable for specific, bounded, latency-tolerant workloads. Private inference on a small model. Aggregation over a modest dataset. Encrypted voting-style tallying. These are real. They exist.
What FHE is not, today, is a general-purpose execution environment for a high-throughput blockchain. The gap between "we can do this on a small circuit" and "this can be a base-layer primitive" is not two years. It is a research program with an unknown horizon, punctuated by hardware advances that may or may not arrive on schedule.
I have a specific reason to distrust the blur here. During the FTX reconciliation in 2022, I spent three weeks matching public wallet addresses against claimed reserves. The reported holdings and the on-chain assets did not reconcile โ the discrepancy was large and structural, not a rounding artifact. Nobody in the news cycle had done the matching. The claims were repeated, and the state was never checked. When I finally published the gap, the response was not "we disagree with your numbers." It was silence, followed by a much larger number arriving from the bankruptcy process.
That experience taught me one thing about "beginning to be applied": it is a claim about a laboratory. It is not a claim about your chain. The word "applied" carries no throughput figure, no cost per operation, no security parameter, no deployment target. Strip those four things and you have not described a technology. You have described an intention.
The correct response to "beginning to be applied" is not skepticism. It is a request for a benchmark. Cost per operation, latency per operation, circuit depth supported, security parameter used. Four numbers. Absent them, the phrase is a mood, not a measurement.
***
iO Is Not a Roadmap Item. It's a Research Program.
Indistinguishability obfuscation occupies a strange position in cryptography. It is the theoretical master primitive. If you have iO, you can build almost anything else โ functional encryption, witness encryption, deniable encryption, and a long tail of constructions that currently require bespoke assumptions. It is often described as the closest thing to a universal tool in the cryptographer's kit.
It is also, practically, nowhere.
The theoretical landscape has advanced. Real constructions of iO from well-founded assumptions emerged from serious research in the early 2020s, which is an achievement worth respecting. But the distance between "a construction exists in a paper" and "a construction runs at production cost on commodity hardware" is enormous in this field, and it is a distance the literature itself does not shy away from.
When the speech says iO may find application in the future, that is not hedging for legal reasons. That is an accurate statement of where the primitive sits. It is an aspiration with a mathematical foundation and no engineering timeline.
Why does this matter for a reader trying to allocate attention? Because iO and FHE are the two highest-complexity items in the entire framing, and they are the two items most likely to get packaged into a tradeable theme by people who have never read a scheme specification.
The pattern is predictable, and I have watched it three times in three cycles. A technically serious speech introduces a family of forward-looking primitives with appropriate hedging. A percentage of the audience hears "this is where the smart money is going." A subset of that subset builds a narrative. A subset of that builds a token. By the time the narrative reaches a chart, the hedging has evaporated and the primitive has become a promised product.
The obfuscation primitive is at maximum risk of this treatment precisely because the name is exotic and the explanation is expensive. Nobody builds a scam around "polynomial commitments for data availability sampling." Too boring. Everybody builds one around "the cryptographic tool that hides everything from everyone."
The more impressive a primitive sounds to a reader who cannot evaluate it, the more aggressively that reader should demand a benchmark before believing anything about it.
***
Parallel Proving and the PBS You Already Have
The speech references parallel block construction and proving. This is presented as a direction of travel. It is worth locating precisely on the map, because part of it is already a conversation the core developers have been having for years, and part of it is a genuine engineering frontier.
Block construction already is, in practice, a separated function from block proposal on much of the network. Builder-proposer separation emerged as an out-of-protocol market structure to mitigate extractable value concentration. The enshrined version โ moving that separation into the protocol itself โ is an active design problem with EIP-adjacent work behind it. Parallel block building is the natural extension: instead of a sequential pipeline from transaction selection to block assembly to proof generation, you run the stages concurrently and reconcile.
Proving is where the frontier actually is. Zero-knowledge proving is computationally heavy. Parallel proving means splitting the circuit or the trace across machines and aggregating the results. This is real engineering with real costs, and the costs are the story. Proving latency determines whether a zero-knowledge rollup can offer competitive finality. Proving cost determines whether the security improvement is worth it relative to optimistic alternatives.
I have done the arithmetic on this class of tradeoff before. The tension is structural, not incidental: the stronger your trust assumption โ the more you eliminate the honest-majority requirement โ the more proving you must do, and the more hardware you must pay for. There is no version of verifiable computation that runs for free. The cost moves. It does not vanish.
This is where the framing's real ambition becomes visible. If the protocol wants to become a verifiable computation network, the proving layer becomes as economically important as the execution layer. That has downstream consequences nobody in the speech mentions. Proving capacity becomes a market. Prover hardware becomes a competitive input. Aggregation services become infrastructure. The trust-minimized future has a hardware bill, and the bill lands on a different set of participants than the current one.
That is not a flaw in the vision. It is the vision's actual content, and it is more interesting than the phrase "parallel proving" suggests. When I listen to infrastructure talks, I listen for where the cost moves, because that is where the money moves next. Cost migration is the most reliable directional signal in this industry. Narratives are cheap. Hardware is not.
***
Formal Verification and the Human in the Loop
The final leg is AI-assisted formal verification โ using automated reasoning to prove properties about smart contract logic, or about cryptographic circuits, more rigorously than testing can.
Formal verification is genuinely one of the highest-leverage practices in contract security. Testing shows the presence of bugs. Verification, done correctly, can show the absence of specific classes of bugs relative to a specification. The specification is where the honest work lives, and it is also where the field quietly collapses.
I want to bring in a specific experience here, because it bears directly on the claim. In 2024 I tested whether AI tooling could bypass a manual audit protocol. The setup was deliberate: a live fundraising phase, a fifty-million-dollar window, an obfuscated logic flaw inserted one layer below the surface pattern. Automated scanners, including AI-assisted ones, produced clean reports. The flaw required a human to trace state across function boundaries and notice a branch that only triggered under a narrow conjunction of conditions.
The lesson is not that AI does not help. It does. It accelerates pattern matching, documentation cross-referencing, and invariant candidate generation. The lesson is that the failure mode of automated verification is not the bugs it misses on the surface. It is the bugs it certifies as absent. A clean report from a system that cannot reason about your specific specification is more dangerous than no report, because it converts uncertainty into false confidence.
This is why the formal verification leg of the speech is the weakest in operational terms. "AI provides rules for automated formal verification of cryptographic systems" is a direction. It is not a deployed discipline. Formal verification of cryptographic circuits is a specialty practice performed by a small number of very serious people. It does not scale by adding a model. It scales by training humans and building specification languages that machines can consume without hallucinating.
I have watched the AI-security intersection get oversold once already. Every cycle brings a new class of tool claiming to eliminate human review. Every cycle, the largest losses come from protocol logic that a human would have caught and a scanner structurally cannot. The exploits that matter are not pattern violations. They are economic assumptions breaking under conditions the designer did not imagine.
You cannot specify a condition you did not imagine. That is the limit. That limit is human, and it is not going anywhere on any timeline this speech provides.
***
The Expansion Paradox: Success Weakens the Burn
Now the economic layer, which the speech does not touch and which the framing nonetheless collides with.
Ethereum's monetary narrative rested, for a period, on fee burning. Under the burn mechanism, transaction fees are destroyed rather than paid to validators, which reduces net issuance. Layer in proof-of-stake issuance and you get a supply curve that can turn negative under sufficient demand. The "ultrasound money" framing grew from that mechanic.
Scaling attacks the mechanic directly. The entire purpose of a rollup-centric roadmap is to move execution off the base layer and compress the base layer's data footprint. Blob space does this efficiently. When it works, base-layer fees fall. When base-layer fees fall, the burn falls. When the burn falls, net issuance rises.
This is the expansion paradox, and it is not a bug in the roadmap. It is a structural consequence of succeeding at it. The more efficiently the network processes activity, the less revenue the monetary layer captures from generic throughput.
I ran into a version of this thinking during the NFT period, analyzing royalty mechanics under the ERC-721 standard. Creators expected enforcement. The standard did not provide it. Secondary markets routed around the expectation, and the gap between the intended economics and the realized economics was measurable โ millions of dollars weekly, converting a social promise into a technical absence. The pattern generalizes. A protocol's economics are defined by what the code enforces, not by what the community intends.
Apply that to the computing-network framing. Verifiable computation, if it becomes a real product category, generates fees somewhere. But where? If proving happens off the base layer, the base layer captures the verification. If verification is cheap โ which is the whole point of succinct proofs โ then the base layer captures very little per unit of computation proven. Succinctness is the feature. Succinctness is also the reason the fee capture may be thin.
The counter-argument is that volume compensates for thin per-unit capture. That is possible. But it is a volume bet on a product category that does not exist yet, and the speech provides no volume estimate, no pricing model, and no fee-capture analysis. A narrative upgrade does not come with a revenue model. Those are separate documents, and only one of them was delivered.
I do not present this as a refutation. I present it as the missing section. The speech is a technical vision with zero economic modeling attached, and the readers most excited about it are the readers least likely to ask where the fees accrue.
***
Privacy Breaks the Assumptions DeFi Runs On
The speech treats privacy as a neutral technical property โ encryption as a capability, not a policy. The engineering is neutral. The interaction with existing systems is not.
Modern DeFi runs on transparency. Liquidations require participants to see collateral positions. Oracles require price data to be public and manipulable in known ways. Arbitrage requires mempool visibility. Extractable value โ the entire economic layer that professionalized around ordering โ depends on someone being able to see pending transactions and act on them.
Add strong privacy to the base layer and you do not just add a feature. You invalidate a set of assumptions the current economic layer is built on. Some of those invalidations are good. Front-running as a business model depends on visibility, and removing visibility removes the business model. Some of those invalidations are not obviously good. A protocol that cannot see positions cannot liquidate them, and a protocol that cannot liquidate cannot offer undercollateralized credit with confidence.
The tension is real and it is under-discussed in vision-level talks. My read is that the industry will end up with privacy as an opt-in layer with selective disclosure โ encryption by default, decryption by consent, with zero-knowledge proofs doing the work of proving compliance without revealing state. That is the only architecture that serves both the privacy goal and the systemic requirements.
That architecture is significantly harder than either "everything public" or "everything private." Selective disclosure requires proving statements about hidden data. Those proofs are more expensive than the plain versions. They are being built. They are not built.
I said it earlier and I will say it precisely: trust is a variable I refuse to define. Privacy is the same kind of variable. It is not a binary. It is a disclosure policy with a cost, and the cost is where the engineering argument lives. Any presentation that treats privacy as a switch is describing a product that cannot exist, because a fully private chain cannot liquidate, and a fully transparent chain cannot protect a user's position size from anyone willing to pay for the information.
Privacy is not a feature you add. It is a set of assumptions you replace, and every replacement has a counterparty in the existing system who will notice.
***
The Regulation That Doesn't Read Intent
Here is the tail risk nobody in the speech addressed, and it is the one I weight most heavily.
Privacy-enhancing technology sits directly against anti-money-laundering enforcement frameworks. The precedent is established and recent: sanctions targeting a mixing service, delistings of privacy-oriented assets by major venues, and enforcement actions that treated the tool as the actor. I am not relitigating the merits. I am recording the pattern, because the pattern is what a risk model reads.
Regulators do not generally evaluate cryptographic intent. They evaluate capability. A primitive that produces untraceable value transfer is, from an enforcement standpoint, an untraceable value transfer. Whether the use case is a dissident protecting a donation trail or an illicit actor moving proceeds is a distinction the tool does not make and the enforcement framework does not reliably make either.
This produces an asymmetry that is easy to underprice. The technical work is public. The regulatory response is discrete and can arrive without warning. A single enforcement action can delist an entire category, cut liquidity, and reprice a decade of research in a single session. That is a low-probability, high-impact event class, and it does not appear anywhere in a vision talk because a vision talk is not the venue for it.
The speech's position โ that privacy is a technical property and technology is neutral โ is philosophically defensible. It is operationally incomplete. Neutrality is a claim the builder makes. It is not a defense the builder gets to use.
I have covered one side of this asymmetry before. My core holding has not changed: when a technology's value proposition is indistinguishable from its enforcement risk, the engineering roadmap and the regulatory calendar become the same document read from opposite ends.
Anyone allocating to privacy infrastructure should be modeling a sanctions event with the same seriousness they model a smart contract bug. The bug is smaller. The blast radius is larger.
***
Contrarian: What the Bulls Got Right
I have spent most of this piece separating claims from capabilities. Now the part where the skeptics are wrong, because there are two of them and both are instructive.
The first thing the bulls got right is that Vitalik is not hyping. Read the verbs again. "Beginning." "May." "Eventually." "Future." A promoter does not hedge. A promoter states. The careful conditional language in the forward-looking sections is not weakness or evasion โ it is an accurate self-assessment by someone who understands exactly how far from deployment those primitives are. If you have ever watched a founder describe a testnet as "live," you know what the alternative looks like. This speech is the opposite of that.
Restraint is a quality signal. When a speaker hedges the dreams and flattens the facts, the hedging is the information, and the market systematically discards it in favor of the headline.
The second thing the bulls got right is subtler and more important. The real content of the speech is not the technology list. It is the reframing of the competitive axis.
For a decade, the public argument between Ethereum and its rivals was throughput. Transactions per second, finality time, cost per transfer. That is a fight Ethereum does not comfortably win, and has not won, and will not win against monolithic designs that trade decentralization for performance. On the throughput axis, the competitive position is defensive.
Now move the axis. "Cryptographically secure computing network" is a competition over cryptographic capability. Over verifiability. Over proof systems. Over the depth of a research community that has been publishing in this space for years. On that axis, the position is offensive and the lead is substantial.
That is the speech's actual function. It is not a product announcement. It is a terrain shift โ moving the argument from a dimension where the competitor is stronger to a dimension where you are. Frameworks are chosen for many reasons. One of them is that a well-chosen framework makes the scoreboard measure the right things.
Both bulls and bears missed this because both were busy pricing the technology list. The technology list was a prop. The frame was the product, and the frame is a competitive maneuver dressed as a philosophy.
Whether the maneuver works depends on whether the cryptographic capability translates into anything a user can feel. Which is the only question left.
***
Takeaway
The EIP tracker is the only source of truth here. Conference stages produce frames. Trackers produce numbers. Watch the former for direction and the latter for evidence, and never let one substitute for the other.
The frame is coherent. One leg touches the floor. Two legs are in the air on unknown timelines. The economic model that would make it investable was not in the room.
So here is the question worth carrying into the next cycle. When a roadmap is honest enough to hedge, and the audience is loud enough to unhedge it, who ends up holding the distance between what was said and what was bought?