Menu
Sign In Search Podcasts Libraries Charts People & Topics Add Podcast API Blog Pricing

Ansgar Dietrichs

πŸ‘€ Speaker
736 total appearances

Appearances Over Time

Podcast Appearances

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

But basically the point is you then have these combinations of like, okay, this execution client with this proving system

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

And then in the end, you basically, again, in this example of five, you'd be in a world again where you have like five different types of proofs that could all, and they're all kind of redundant.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

They all have different, you know, they're full stack different from each other.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

The generally novel thing here is that today you run one execution client, right?

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

Like there's multiple, of course, and there's multiple consensus client, but you choose one of each.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

In this new world, what you can do is you can just verify multiple proofs.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

So for example, there's this idea, and again, just to use example numbers, but they seem roughly ballpark right.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

You could have a system where you say, I only accept a block if I saw at least three different valid proofs for it.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

So I know that there are these five different ones, and I have to have seen at least three of them.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

Otherwise, I don't accept the proof.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

Except the block.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

And so that actually gives you better redundancy because it's kind of almost as if every Ethereum node today would run three different client setups and would basically only accept blocks if they all agree, which of course gives you much better properties than right now we only have the redundancy across nodes, not within a node.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

So it's actually, it's a better story, but it's also one we actually have to be intentional so that you don't accidentally collapse any layer of the stack.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

Yeah.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

And as just a side note, there is this experimental idea.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

And of course, in the age of AI, all the timelines collapse.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

So who knows, you know, like maybe that's actually even short-term viable.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

But this experimental idea of a fully formally verified client.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

And you could imagine, right, like an EVM implementation in RISC-V that is fully formally verified to be correct.

Bankless
Ethereum's Last Big Upgrade: The zkEVM | Ansgar Dietrichs

In that world, that could basically then, you would no longer need redundancy at that layer of the stack.