Ansgar Dietrichs

What kind of production grade readiness does this have for which use cases?

I think it's more, you can imagine more, it's about how many nines after the comma, right?

Ethereum mainnet must never go down, right?

We have 100% uptime and we're not willing to risk this.

So we're basically willing to take extra precaution there.

But importantly, if you're, for example, at some point running a ZK validator and you actually, there's a bug or something, right?

The worst that happens, like no one will get slashed, right?

Like what happens is just you're briefly kicked off the chain and then you're automatically flipping over back to normal re-execution mode.

And then worst case, if we're already in this partial status world, you might have to first re-sync some of the state, right?

So worst case, you're offline for a couple hours and then you're back online, back on the chain.

So none of this, we do it very responsibly, just because, you know, just to clarify this.

On brand.

But yeah, so, and basically, I think the way that these, again, absolutely amazing ecosystem ZK teams are talking about this.

I think last year was all about, I would say it was the year of performance, getting to real-time ZK ABM.

This year is the year of security, getting to like absolutely hardened.

There's also like this bit of security measure, right?

Like getting to a level where we are very confident in the security level.

Then next year, I think will be the year of

productionizing the ZKVMs.

And then the year after will be the year of transition to mandatory.