Ansgar Dietrichs

All three of these will come down.

The heartbeat of the chain, the time to next block, will actually be the one that's only going to come down maybe by a factor of three, something like that, from 12 seconds maybe to four seconds eventually.

Maybe we can go lower, but I wouldn't necessarily want to promise this.

I think the other two are actually the more exciting ones.

Finality will come down massively.

And time to inclusion, that's a bit more of an exploratory process still, but that also will come down massively.

So I think basically, yeah, but block times as well will come down.

But none of this will be through ZKVM, although, of course, it will be part of an integrated system.

Of course, because this is like a multi-year process, it's as typical.

There's like very concrete steps as typical.

say for the next 12 months.

And then as you go further into the future, I can point out that's the current plan.

These are maybe the open question.

These are the directions, right?

So that's how these things always work.

The interesting thing, as I said, top of a podcast is that it's not just a one-time hard fork.

There will be a one-time hard fork.

And that is about the eventual switch from what will come first, which is optional ZK EVMs for those nodes in the Ethereum network that want to consume proofs instead of re-executing.

Then at some point, there will be this moment in time where we say, okay, now Ethereum just runs on proofs.

Of course, you can still run a node optionally in re-execution mode if you want to, but by default, the network now guarantees that there will always be proofs, basically.