Ryan Sean Adams

In the future, we will be a phase of Ethereum where it is all ZK EVM, but it is not an acute moment as I understand it.

How do we go from A to B?

What does that roadmap look like?

You're allowed to be slow, and the network will hear you.

Exactly.

Right.

So as I understand it, the way that it happens is that in a year, we will introduce optional proofs.

The Ethereum enthusiasts of the world who just love Ethereum, tinker with Ethereum, run nodes for Ethereum out of just pure passion will start to do these optional ZK proofs.

They will be the pioneers of

of the transition of Ethereum to be a classical blockchain transitioning into a ZK blockchain.

And that will give Ethereum researchers like you, the EF, a lot of data of what it looks like to be in production because of these enthusiasts that are running this optionally because they just love Ethereum so much.

That will give you guys the information you need to do the prerequisite upgrades that are needed to actually get a full mandatory ZK EVM fork.

And as you alluded to, it will also give us just insight into, you know, in production use of the ZK EVM.

Maybe there are bugs.

If there are bugs, we need to find them before we make them mandatory.

And so, you know, all the different clients will have their own version of the ZK EVM and we'll be stress testing all of those by using them into production.

Basically, there's a whole era of

demo Ethereum ZK EVM.

And that will take, I think you said, you know, somewhere two to three years as we run out of classical scaling that we will have the hardened data and the information and we will do the prerequisite work to unlock mandatory ZK EVM

around two and a half, three years from now, the mandatory ZK EVM hard fork will happen.