The Ethereum Foundation has had a rough year. Or three. High-profile departures, budget cuts, internal arguments about whether the EF should be more commercially minded, more boosterish, more willing to act like a normal company rather than a research collective with a mission statement.
Versions of these arguments have been circulating for years. And the EF, for all its success in building Ethereum, has often struggled to square all these circles. Vitalik, in particular, has often found himself in the middle of an intractable trilemma that no amount of reorganizations will probably solve.
Still, Ethereum’s intellectual leader, ploughs on. As the community argues about Ethereum’s best interests, Vitalik keeps producing highly original papers across technical and operational issues.
On Monday, Vitalik Buterin published what may be the most ambitious piece of technical writing in crypto this year: a 10,000-word deep dive into something called obfuscation. The word normally carries a negative charge. Obfuscation means hiding, obscuring, muddying the waters.
In Vitalik's hands, it becomes something else entirely.
Obfuscation, in the cryptographic sense, lets you convert a program into an "encrypted program" such that you can run it on cleartext inputs and get the same cleartext outputs -- but the internal workings of the program are completely hidden. It's hiding the code, not the data.
Think about what that means in practice. Today, zero-knowledge proofs let you prove something is true without revealing why it's true. Encryption lets you send a message only the recipient can read. Obfuscation would let you run a program -- any program -- without anyone being able to see how it works. Vitalik describes it as coming very close to the theoretical ideal of a "trustless trusted third party." Combined with a blockchain, you could build a secure, private, collusion-resistant voting system with almost no trust assumption at all, he says.
The catch, as always, is engineering reality. Making a provably secure form of obfuscation is genuinely hard -- the current best approaches have runtimes described as "literally galactic," technically polynomial but so computationally expensive as to be practically unusable today. Vitalik is honest about this. He draws the comparison to where SNARKs were in 2010 -- theoretically sound, practically absurd -- and notes that once the cryptographic community knew something was possible, it found ways to make it work.
That's the bet. And it's not a small one.
For those of us building in the ZK and privacy space, this matters beyond the mathematics. Vitalik publishing a 10,000-word technical treatise on obfuscation -- on the same day that Miden is shipping Guardian operators, that institutions are asking serious questions about private stablecoins and private treasury operations -- is a signal about where the frontier of this technology is heading.
Privacy as a feature is already here. Privacy as infrastructure is being built. Privacy as a fundamental property of computation itself -- where even the logic of a program can be hidden from the people running it -- is what Vitalik is pointing toward.
That's not obfuscation in the pejorative sense. It's the whole point.
Privacy Roundup
Unlink, a privacy layer for EVM chains, went live on Monad, letting institutions and teams hold and move funds without exposing balances, counterparties, or positions.
Confidential Balances returned to Solana, encrypting account balances and transfer amounts while senders, receivers, and the token remain public.
Starknet added confidential capabilities for USDC, letting users shield, transfer, and privately swap USDC.
Thanks for reading this edition of Privacy Dispatch. Please subscribe to receive this newsletter every Tuesday.
Till next time.