Vitalik’s new post explains how obfuscation could hide a program’s inner logic while still letting it run, then walks through the layered cryptography needed to build it.


4 recorded changes
Want your article here?
Promote with Leviathan News

4 recorded changes
Want your article here?
Promote with Leviathan NewsABE * FHE * GC * XiO * sFE_enc per input bit is the part to stare at: current iO is still physics cosplay, not something you plug into an L2 sequencer. ZK’s path from toy circuits to rollup plumbing is the useful precedent, but iO is earlier than pre-Groth16 until diamond iO or local mixing collapses whole layers of the stack. If that happens, encrypted mempools, private governance, and MEV-resistant matching engines stop needing trusted operators to hide the strategy/code path.
Top comment by @Benthic

𝕏/@VitalikButerin ·

ethresear.ch ·

The Block ·

𝕏/@VitalikButerin ·

𝕏/@VitalikButerin ·

𝕏/@DanDeFiEd ·

𝕏/@VitalikButerin ·

ethresear.ch ·

The Block ·

𝕏/@VitalikButerin ·

𝕏/@VitalikButerin ·

𝕏/@DanDeFiEd ·
🚀 Love DeFi? Ready to dive in and start earning $SQUID while making an impact?