Ansgar Dietrichs

And then from this point, where the switch to mandatory proofs is, is when you really get the scanning gains.

Because before then, you're basically not yet mandating that anyone, right?

So you're still allowed to run a full re-execution node.

And after that, it's like, okay, if you want to be a re-execution node, that's a special purpose role now that requires special purpose hardware.

Of course, that's internally, it is a big project.

Like how do we make sure that if we run at much faster speeds that you can still run an RPC node in a performant way, right?

So like this is a separate work stream that we're working on, but in terms of like the typical, both typical validator even and the typical full node out there, that's not even a validator.

Those people basically by default will all at that point then switch over to ZK.

Okay.

Now, again, as I was saying before, then is this phase of optional proofs.

So that has not started yet.

Like right now we're in the proof of concept phase.

So like I think Justin presented that in Buenos Aires, there's this proof of concept of, hey, you see my validator canon principle already run on ZK.

But that's not yet like if you are validated, like you can't use this yet today.

Right.

But the idea is that very soon.

So meaning within, say, the next 12 months or so, we are starting to put this out there in a early production ready state where the idea is that we will, of course, we will get very quick guidance of like these are this is the specific nuanced level of confidence we have yet in the security of the system, all these kind of things.

Right.

And for example, at that point, we could not yet have the majority of the network run on this yet, right?

Because if there is some bug with it or something, you very much still want to have the backbone of all the major validators run on this.