Yuval Rooz

And I think that a lot of the L2s will say they are a good thing for Ethereum.

I personally think that they were a bad thing for Ethereum.

Because in my opinion, if you are an asset on one L2, you are not composable with another asset of another L2.

You have to use solvers, you have to use bridges.

And let's just hopefully agree that solvers and bridges are not the value proposition of blockchain composability.

And as a result of that, rather than creating like a really nice model of a global composable world, which is, in my opinion, the whole value proposition of blockchain, you have effectively bifurcated an incredible ecosystem, which in my opinion is not a good outcome.

So, by the way, the reason for the name Canton is really this idea that the world is, first of all, not homogeneous.

It's actually heterogeneous.

Different applications, different geographies, different use cases have different requirements.

So if you think of a lot of our R&D, most of our R&D is in Switzerland.

If you think about the Swiss federated system, they all have their different cantons.

They don't even spell canton the same way in every place.

They have tax rates, have different rules.

But when you take a train, you don't feel like I'm going from one country to another.

I'm still in Switzerland, right?

So the idea was, can I actually create

something not to be mistaken with L2s, but looks similar, this idea that I can create all of these different cantons that have different requirements when it comes to privacy, when it comes to accessibility, when it comes, like I can, I can have very, very open configuration and all of those different things.

But at every given point of time, if I wanted to compose a transaction that

across different cantons, I can do that atomically.

No bridges, no solvers.