Why did Vitalik Buterin build Ethereum?
When Blizzard Entertainment changed the rules of World of Warcraft, it exposed a fundamental truth:
If a system controls the rules, it controls reality.
Ethereum fixed this—at the execution layer.
-
execution is deterministic
-
state transitions are verifiable
-
consensus is distributed
That problem was solved.
The Problem That Wasn’t
Ethereum guarantees:
execution follows the rules
But it does not guarantee:
that independent parties can verify claims about what happened using a standard, system-independent method
The Verification Stack
Verification today is not a primitive.
It emerges from a stack of interpretations layered on top of raw chain data:
-
RPCs
-
indexers
-
decoding logic
-
proof formats
-
transaction references
-
verification implementations
These are not broken.
But they are:
non-standardized and environment-dependent
The Result
Verification is not portable—the same claim cannot be independently reproduced across systems without shared assumptions.
Yes—you can run your own node.
But that does not solve:
how different systems agree on what to verify—and how to verify it
A Simple Example
Three systems attempt to verify the same claim:
-
one extracts a hash from calldata
-
one extracts from logs
-
one relies on an indexer
They can return different answers based on:
-
encoding assumptions
-
extraction rules
-
parsing logic
The chain didn’t disagree.
The verification process did.
What This Means
To answer:
“Was this data committed on-chain?”
you typically depend on:
-
a specific node or RPC
-
a particular indexing model
-
application-defined decoding
-
custom verification logic
So while Ethereum removed centralized control over execution:
it never standardized verification
The Shift in Power
Blizzard controlled outcomes by controlling rules.
Ethereum removed that.
But today, systems still control understanding by controlling:
-
how data is encoded
-
how it is extracted
-
how it is interpreted
-
how it is verified
Which leads to a new dependency:
If verification depends on the system that produced the claim, the system still mediates truth.
The Missing Property
Ethereum standardizes:
-
execution
-
consensus
-
state
But it does not standardize:
a portable, implementation-independent verification artifact
There is no shared invariant for:
“this exact byte sequence corresponds to this on-chain commitment”
The Claim
A system is not fully decentralized if verification is not independently reproducible across implementations.
Why This Matters
As Ethereum moves toward:
-
rollups
-
proofs
-
data minimization
we are increasingly:
verifying correctness without preserving a portable reference to what was verified
This is:
verification without referenceability
Open Question
Is verification today actually portable across implementations?
Or:
are we still depending on the systems we claim to have removed?
Closing
Ethereum removed Blizzard from execution.
But if verifying what happened still depends on the client, the indexer, or the application—
control didn’t disappear. It moved to the layer that defines what counts as truth.