Ryan Sean Adams

As I understand it, the clients are where all of the risk is with the ZK EVM and where we have to be, have like an extreme level of caution with the transition from a classical blockchain to a ZK blockchain.

And like if something is going to go wrong, it's going to go wrong at the client level.

I mean, I suppose that's always where it would go wrong.

But when we, you know, we have, you know, Ethereum has over a decade of uptime because of client diversity, because of how hardened these clients are.

And we are kind of resetting that to kind of go back to, you know, zero Lindy with the ZK EVM.

You know, we have some properties that will be carried over, but nonetheless, there will, it's risky in the sense that like we have all this great hardened infrastructure and we're kind of rebuilding it to be ZK.

And so we have to have this like extra levels of redundancy, as you said, like three proofs, three correct proofs to make sure that, you know, not just two proofs because two proofs might have the same bug.

So we might prove the same bug twice.

So three things like this.

And so, you know, what's your level of redundancy?

fear about this part of the transition for Ethereum from the classical blockchain, which is so hard and 100% uptime, to go where we go here?

How scary is this?

Yeah, yeah, yeah, yeah.

Which is why it's taking not a short amount of time.

So just to maybe conclude this podcast, the timeline, it is now the start of 2026.

By the time we hit 2030 is a good guess for when we think we will have the full...

power, the full properties of the ZK EVM.

You're nodding your head.

Does that sound right?

Right, right.