Ansgar Dietrichs

It's like, hey, assuming the blockchain was in this state and I apply these transactions, now then the next state is this.

So basically like...

you no longer need to go and load the data from the values from disk.

So you basically, you're saving this IO on the load side naturally.

And then the thing that you normally still have to do is you have to like go and still write the updates, right?

So if you still have the state of Ethereum, so after you verified the block, you still have to go and say, okay, these values change, right?

So you have to go and apply that change.

One, that's no longer in the critical path.

So you can do that after you've already finished verification.

So if you're a validator, you can already vote.

You can like say, ah, this block was valid.

And then afterwards I go and actually apply the update.

So in terms of like, what is the current price of this Uniswap pool or what's the balance of this account, right?

Like I might only go update this on disk after I already know that the block is valid.

So that's a natural benefit you get.

But if you want to push it further,

We have to, and this is what I'm saying, like this is one of those changes that is enabled by ZKVM, but it's its own change.

It's stateless Ethereum or partially stateful Ethereum.

So what does that mean?

Well, instead of like today, any node in Ethereum network basically has to have the full state and that's with re-execution, that is unavoidable, right?