Ansgar Dietrichs

It's called data availability.

It's called blobs, right?

So what we will do is we'll take the Ethereum blocks and we'll just basically become our own roll-up in a sense.

We're putting the data into the blobs.

It's called block and blobs, BIP.

And with that, now all an Ethereum node has to do is just sample.

Sample the data and we'll be in the progress of making that more and more efficient because we want to provide more and more data for our L2 partners.

And that now naturally also benefits ourselves because now you can have bigger and bigger blocks while keeping the footprint in terms of bandwidth also very consistent.

So now...

Coming back, we have ZKVM and we have partial statelessness and we have block and blob state availability sampling.

Together, they scale bandwidth, they scale IO and they scale compute.

And that is how you basically like use all of these elements to scale the blockchain.

And then there's some nuances.

You don't get everything for free.

You have state growth.

We can talk about state growth that we have to separately address.

And you have things like being able to efficiently sync an Ethereum client.

There are things like being able to efficiently run an RPC node, you know, like what Infura is doing, these kind of things.

So there's more to scaling than this.

But the core story is that you have these three constraints and ZKVM directly and indirectly addresses all three.