Ansgar Dietrichs

That's, I think, again, is this guaranteed yet?

No, we don't yet have.

We think we see a path.

We think we see a path.

That's our goal.

And then, of course, beyond that, if you want to be more in sci-fi world, now you can think about native roll-ups.

So maybe the way we then keep scaling beyond that is not through just the single chain.

Maybe then we're back to this kind of sharding type setup of multiple chains synchronously composed.

So, I mean, of course, I think people will be familiar why client diversity is so core to Ethereum and to Ethereum's kind of 100% uptime, right?

Like there's the redundancy factor you get from client diversity.

And so the reason why this is relevant is just that like the nature of clients, the nature of client diversity changes in this world.

And that is because, again, if we think back to how I explained how there's like this basically

most likely RISC-V kind of intermediate target for ZK.

And then you basically, you just run a, of course, heavily modified, but basically like a traditional execution layer client that gets compiled to RISC-V.

And then you take one of those new ZK proving systems that then take the RISC-V code and prove execution over it, right?

So what that means is now basically the Ethereum execution layer nodes

inside of the ZK proofs, right?

Which is of course conceptually like very different from what that used to be before.

And so what it means is that now the actual node architecture is actually quite interesting.

You basically, you run, and that is a little bit still TBD.