Ansgar Dietrichs

So that's basically the performance, security, production, and then full transition.

That's how I think about it.

It's like one year at a time.

In terms of what comes after the transition, well, it's just, I think,

And that's why I was saying earlier, like with the further you go out, the more unknown unknowns there are.

It's just about saying at that point, we will have all of the ingredients.

Like, you know, we have the partial statusness, we have the block and blobs, and we have the ZKVM to take advantage for scaling.

But we don't expect that once we get closer, that it's like a one-time switch and now we can run it a thousand times faster.

Instead, we basically, like right now, conservatively, quote unquote, are projecting this three times per year because we expect that there will be individual remaining challenges we have to address, right?

Maybe we have to restructure the way nodes sync, or maybe you have to restructure the way RPC nodes, again, operate.

So you're confident that the chain is still usable at higher rates, right?

So this is just expressing that

while we have the main architectural ingredients, there will still be a lot of like detail work.

And so we expect instead of making use of it all at once, it's going to be this continuous process.

And again, the nice thing about this rough 3x number is if you just say, look, every two years you get a rough 10x, 9x, 10x.

So basically we're thinking we have like a path for maybe,

five or six years of this.

So six years at 10X every two years means 1,000X.

So basically the first three years of that we get traditionally, then the next three years, so this is EKVM.

So in six years, roughly 1,000X of where we started last year