Ethereum’s next big leap might not look like a single “flip the switch” moment—but it could change how the chain verifies everything. In this episode, Ansgar Dietrichs comes back to unpack the ZK EVM: why “re-executing every block” has been Ethereum’s hidden scaling tax, how real-time proofs finally make a different verification model viable, and what it would take to transition safely without sacrificing the verifiability that keeps Ethereum credibly neutral. They explore the three true bottlenecks of blockchain scaling (compute, IO, bandwidth), the roadmap from optional proofs to mandatory proofs, and why client diversity could look radically different in a ZK-native future.
---
📣SPOTIFY PREMIUM RSS FEED | USE CODE: SPOTIFY24
https://bankless.cc/spotify-premium
---
BANKLESS SPONSOR TOOLS:
🔮POLYMARKET | #1 PREDICTION MARKET
https://bankless.cc/polymarket-podcast
🪐GALAXY | INSTITUTIONAL DIGITAL FINANCE
https://bankless.cc/galaxy-podcast
⚡ EUPHORIA | REAL-TIME ONE-TAP TRADING
https://bankless.cc/euphoria
🌐BRIX | EMERGING MARKET YIELD
https://bankless.cc/brix
🏅BITGET TRADFI | TRADE GOLD WITH USDT
https://bankless.cc/bitget
🎯THE DEFI REPORT | ONCHAIN INSIGHTS
https://bankless.cc/TDRpro
---
TIMESTAMPS
0:00 Intro
0:43 Ethereum’s Biggest Upgrade
4:35 The Core Idea: Verify Blocks Without Re-Executing
10:40 From Bitcoin’s “Verify Cheaply” to Verifying Full Execution
16:22 Cryptography 2.0: Proving Arbitrary Computation
22:56 Scaling All 3 Constraints: Compute, IO, Bandwidth
32:33 Why Ethereum Has Been “Slow” by Design
38:29 3× Per Year: Scaling Now, Not Someday
41:28 ZK Isn’t About Faster Blocks (But Speed Still Improves)
46:33 Rollout Plan: Optional Proofs → Mandatory Proofs
49:59 Dependencies: Block-in-Blobs, Repricing, New State Trees
54:14 Security Reality Check: Performance → Security → Production
1:01:24 Client Diversity in a ZK World
1:10:51 Timeline: ZK Ethereum, Around 2030
1:16:31 Second-Order Wins: L2 Bridging and Beyond Crypto
1:20:49 Closing: Build the Boring Infrastructure, Enable the Apps
---
RESOURCES
Ansgar Dietrichs
https://x.com/adietrichs
---
Not financial or tax advice. See our investment disclosures here:
https://www.bankless.com/disclosures
No summary for this episode yet.
ZKVM is this fundamental insight that what you can do is you can basically allow nodes to verify that a block followed all the rules without having to re-execute the block. It's a very non-intuitive thing, right? A blockchain, by its nature, is a very symmetrical thing. Every node basically does the same thing. Of course, you have block producers, but then every node kind of has to download, re-execute, you're duplicating the effort across the network. And now you're jumping to this through this very fancy cryptography, you're jumping to this world where you still have the same effort to build a block, but then verification in a way is effortless.
It has this magical compression element to it. Bangladesh Nation, I'm here with Ansgar D-Tricks. He's a researcher at the Aetherium Foundation. We're going to talk about the ZKVM today on the show Ansgar. Welcome to Bangladesh. Hey, great to be here again. Pretty ambitious subject, Ansgar. Ethereum has had this history of very big forks, hard for hard forks that have upgraded Ethereum from this early primitive proof of concept where it started in 2015 to what it is today, which is fundamental infrastructure, the backbone of internet money and internet finance. We had the merge, which did proof of work to proof of stake.
We had EIP1559 that upgraded Aether economics and transaction user experience. There's also 4844, which just enabled Ethereum's roll up environment to become its best self. With each of these forks, they all represented this rallying cry for the Ethereum community. They were this grand unifying force of attention by the Ethereum community, and it allowed Ethereum itself to command attention from the rest of the world. The rest of the world paid attention to Ethereum when Ethereum had these forks, these incoming forks. Ethereum was just loud. And I think in these kind of represent Ethereum, some of Ethereum's best moments when Ethereum has these kind of cultural shelling points for technological upgrades to what we consider in the Ethereum community to be critical social infrastructure.
Now, I think Ansgar and I want to suss this out, this topic out with you, that there is another fork on the horizon. It's not soon. It's not this years, likely not next year either, but nonetheless, it is there on the horizon, and I think it deserves attention. I think it deserves the achievement that the Ethereum community has given previous forks. And I think in addition to all of the valuable things that we got from the three forks that I just mentioned, this one is actually the biggest upgrade that Ethereum will ever experience because it relates to users more than any of the three forks in the past.
And that is the fork that introduces the ZK EVM to Ethereum. Now, Ansgar, these are the sentiments that I want to start this podcast off with before we get into what is the DK EVM and all the technical details about it. I just want to give those sentiments to you and have you reflect upon them before we kind of dive into the technicals. I personally share your excitement. On this topic, I really think that it's one of those changes that I really Ethereum at its best. It's one of those really ambitious technical projects that I think Ethereum is in a unique position to deliver. It will have a huge impact, primarily through scaling, but in many ways, I'm sure we'll talk about all of this.
And I really think it's something we can look forward for. We can be proud of. And yeah, I'm excited to talk about the details. I will say, by the way, you said, hard fork and the interesting thing here is similar to if you think they got the merge, right? We had first the launch of the beacon chain, which was one moment in time and then we later on had the merge as like two separate moments in time. I think similarly, maybe even to a larger degree with ZK EVM as we'll discuss, it actually, it has this nature of it's an ongoing transition that that will that is basically about to start. Then we will have the main hard fork and then it'll continue after.
So it's much more like a ongoing transition. But yeah, let's let's dive in. So it is the introduction of an era of Ethereum rather than an acute hard fork. And I think the ZK EVM era will be has the potential to be Ethereum's best era because of what the ZK EVM does for Ethereum. So let's stop hyping it up and start to get into the technical details. What do we need to know about what a ZK EV is? What is it? And then we can talk about like why what it is that's so significant to Ethereum. Yeah, so I think you know to understand this, like really kind of you have to start from the problem statement.
So ZK EVM really arose in the context of scaling and basically the fundamental point is that a blockchain, if you run a blockchain, you have these three primary constraints. You have the data, you have to first like any you block you create, it has to get to the user, then you have the IO, you have to like then go to disk, you have to get all the data you need to actually like then then verify the block, and then you have the actual verification, the execution, the compute. So those are like the three main constraints, the bandwidth, the IO and the compute. That's any blockchain or matter of the design, that those are the main constraints.
And so if you want to scale this, you can just do the thing where you take that and you just scale it up. And we'll talk about this in a bit, that's actually to some degree what we're doing in this short term. And that's what many other chains have been doing. That's a very natural thing, but you do run into limits. You do run into tight limits. And so ZKVM is this fundamental, like it's it's it's it's it comes from from the cryptography side, these snacks, your knowledge proofs, and it is this fundamental inside that what you can do is you can basically allow nodes to verify that a block followed all the rules with the out having to re execute the block.
And that's again like that that's something that's that it's it's a very non intuitive thing, right? Normally it's it's a blockchain by its nature. It's a very symmetrical thing every every node basically does the same thing. Of course, you're block producers, but then every node kind of has to download re execute you you're duplicating the effort across the network. And now you're you're jumping to this like through this very fancy cryptography, you're jumping to this world where you still have the same effort to build a block, but then verification in a way is effortless. It it has this this this magical compression element to it.
And then specifically what's what's so important in the in the other one context is the real time element to it. So a ZKVM just allows for this compression. And for example, many listeners, I think, will already be familiar with the concept of ZK roll ups, right? So so those have been around for a while. And that actually was a huge first jump in this technology, which just allowed for this compressed ZK verification in the in the first place. But so far, this is done in an asynchronous way. So you meaning you have your L2 blockchain that you know, it's it's on chain basically and it it keeps progressing.
And then afterwards, but with some, you know, up to several hours of delay, you comment you basically you compute over a long time, these proofs, and then you bring them to the chain. And what now is the second huge jump here is to go from from this very asynchronous delayed process to a a proving a verification loop from from create block creation proving verification that all happens at the same speed of the blockchain synchronously. So like within a single Ethereum slot, right now that's 12 seconds, we'll bring that even further down. You have this entire loop close loop within that short amount of time.
And so basically that's many orders of magnitude of performance improvement. And that really is what emulates all of these huge gains for the other one. Galaxy operates where digital assets and next generation infrastructure come together serving institutions and to end. On the market side, Galaxy is a leading institutional platform providing access to spot, derivatives, structured products, defile ending, investment banking, and financing. With more than 1600 trading counter parties, Galaxy helps institutions navigate every phase of the market cycle. The platform also supports the long term allocators through actively manage strategies and institutional great staking and blockchain infrastructure.
That scale is real. Galaxy has over $12 billion in assets on the platform and average a $1.8 billion loan book in late 2025, reflecting deep trust across the ecosystem. Beyond digital assets, Galaxy is also building infrastructure for an AI-powered future. Its helios data center campus is purpose-built for AI and high performance computing, with more than 1.6 gigawatts of approved power capacity, making it one of the largest sites of its kind. From global markets to AI-ready data centers, Galaxy is serving the digital asset ecosystem end-to-end. Explore Galaxy at galaxy.com-bankless or click the link in the show notes.
Euphoria brings one tap trading to the palm of your hand. Built on mega-eath, Euphoria takes real-time price charts and projects it over a grid of squares. You tap the squares that you think the price will enter in just five to 30 seconds in the future. If the price goes into that quadrant, you can pocket anywhere between two and a hundred x-year trade. No other application helps you trade faster and with more leverage on market-driving events, like FOMC meetings, presidential speeches, or global macro events. Thanks to mega-eaths, real-time blockchain, Euphoria is the way to get real-time price interactions with a market.
On Euphoria, you'll be able to compete with friends using Euphoria's real-time social trading experience, allowing you to go head-to-head with your friends. A great party trick if you project the app on a TV. It'll be like the Mario Party of derivatives. To trade on Euphoria, people can deposit stablecoins from any chain or do direct fiat transfers, and everything gets converted into mega-eaths native stablecoin, USDM, in the background. Check it out at Euphoria.finance and download the app or find it in Telegram as a mini app. In 2024, emerging markets generated over $115 billion in annual yield for investors, with yields ranging between 10 to 40%.
These are some of the highest, most persistent yields on earth. The problem? DeFi can't access them. Bricks changes this. Built on mega-eath, Bricks takes emerging market, money markets, and sovereign carry, and turns them into composable primitives you can access straight from your wallet. While DeFi investors earned 3-6% on stablecoins and T-bills, institutions have been harvesting 10 to 50% yields backed by sovereign monetary policy. Bricks connects these worlds with institutional gray tokenization, local banking rails, compliance across jurisdictions, and real-time stablecoin settlement. Bricks says the heavy lifting, so DeFi can finally access real collateral, and structured products on top of real-world yield.
Even the best carry trades can be within reach. Bricks brings DeFi's promise to the emerging world and brings the emerging market yield to your wallet. Let the yield flow with Bricks. Maybe going back to just like what makes a blockchain a blockchain. Bitcoin had this fundamental insight of the way that we get rid of a leader in a blockchain is that everyone checks the legitimacy, the authenticity, the correctness of everyone else. And so when some Bitcoin miner mines a block, but if it finds the correct hash, and it proposes that block, everyone else at a network doesn't trust that leader. They re-execute all of the same work to verify it for themselves.
And that's the way that Bitcoin discovered the way to have a decentralized network is everyone's checking everyone else. And that re-execute word has just been the status quo for all blockchains. Everyone re-does all of the work. And the way that that impacts blockchains, all blockchains, so this day, is that it kind of is hamstrung by the slowest node in the network. Or at least there is some requirement for computation that every blockchain has that, you know, if you aren't at least this fast, you can't keep up with the network because you can't keep up with executing all the everyone else's work.
And now, you know, some blockchains have different opinions as to like how much requirement you have. Bitcoin is very low. Ethereum has also been a very low requirement because we want to be decentralized. You know, as you said, like, you know, some chains, like Solana or other very fast chains have had a higher opinion as to the computational requirements it takes to do the re-execution. But nonetheless, all blockchains to this day are re-executing all of the same work. And it's redundant. It seems unnecessary. It seems like is there a way where we can not do all of that extra work and still have a blockchain.
And parallel to that, as you said, with like the Ethereum layer 2s, what we understand is that there is a way to not do this and that is with ZK proofs. So in addition to the technological progress of blockchains as a whole, we can make them more efficient. We can, you know, we can juice some of the throughput. But on a parallel path, there are cryptographic algorithms that instead of allowing or forcing everyone to do the re-execution, you can simply verify a cryptographic hash, a cryptographic proof. And that part is trivial. It's easy to verify. It's hard to produce in the same way a block, in a blockchain is hard to produce, but it's trivial to verify the correctness of a cryptographic proof.
And that's kind of the trick. That's where we remove the re-execution. A great Elon Musk quote here is the best part is no part at all. And what a cryptographic proof does is it removes the whole part of re-execution. So it blocks in a blockchain, get executed once, and then no one has to actually re-execute it. They can just trivially verify it, which allows for a lot of redundant work to get removed from the system. And that allows for just work being constrained down to one block producer. And then everyone else is just like thumbs up, that is correct. And we really like take off the brakes off of a of a blockchain system.
Now the reason why Bitcoin wasn't built like this in the first place, the reason why Ethereum wasn't built or any other blockchain wasn't built like this in the first place was, you know, technological progress along cryptographic hashes also needed to mature. Maybe you could like take everything that I just said and run with it, but also talk about just like the technological parallel path of cryptographic proofs as they've been progressing alongside blockchains. Yeah, absolutely. So actually, just to start with where you started with with the Bitcoin example, because some listeners might have heard this and might have been like, hey, actually, isn't there this asymmetry as well where a miner does all this like very expensive work, but then not every other node has to like redo the same mining, right?
Like you indeed in the mining process, there's the same efficiency like asymmetry. And that's actually it's a very common trick in cryptography where basically like you try with mining, you try all these different hashes, you find one hash that has enough of like leading zeros. That's how the difficulty in Bitcoin worked. And then you can just show people and it's very cheap to to verify. So Bitcoin on the consensus mechanism side already uses a similar trick, right? But on the actual content of the block, right? So like what is in a block in a Bitcoin block? It's all the transactions. Each transaction comes with a signature.
So you have to like actually like verify the signatures. You have to say, okay, balance was moved from this account to that account. All of the actual operations of the blockchain, that's the re execution part, right? So so Bitcoin does get has this like again, because this is a very typical trick in cryptography that you have this like asymmetry of generation versus execution. It uses that for mining because that's easy to do with proof of work. It's it's very very hard to do this for the actual operations within a block. And so now this is what basically the main unlock here is that that basically now we're bringing the same efficiencies that people are used to from this like one one miner, everyone can verify easily.
We're bringing that same efficiency to the entire block block in block. And of course on Bitcoin, the actual Bitcoin block is very small. It's a very simple operations on Ethereum because you can run smart smart contracts and you will be massively scaling the throughput. It's it's much more complex. The vast majority of the overhead in processing and following the chain is not the consensus part, not the proof stake part, but it is this digital contents of the block. So what what has changed on cryptography? Actually, my my my friends from from the 0x park team, they are like one of those cryptography research labs.
They always talk about I think they they call it maybe a maybe getting the slightly wrong, but they could they could they call it the first generation of cryptography and the second generation of cryptography. What was the first generation of cryptography? It was basically hand crafted algorithms for very specific use cases. So a signature algorithm or a hash function or anything that basically it fulfills a very specific purpose and you can use it for a very in a very specific context. And and those are amazing, right? And like that's been like the story of cryptography for the last 50 years, right?
It's it's basically more more sophisticated special purpose and mechanisms. And and those were already very mature when say Bitcoin started, right? This is why they were able to just take the concept of hash functions off the shelf and you can you can do amazing things, signature, mechanism, all that kind of stuff. What is like very new? It basically started another decade ago or something like this probably academically a little bit early. I'm not and not actually a cryptography expert myself. So I don't know the exact kind of like early story there, but that's basically like cryptography 2.0 in a sense.
It's it's general purpose cryptography. It is basically now the ability to make cryptographic statements about arbitrary computation instead of having to like handcraft it for a specific use case. You know, you're going to this general purpose world and this is like a huge leap because it means that instead of like just say signing a message and you can you can prove whatever you want and anything during during complete anything that that that you any any execution whatsoever you can now compress. You can make it you can make a cryptographic statement over and and that that that was a giant leap.
It was I think only really it it was pulled from academic theory to feasibility. I think through a lot of funding that came from the blockchain space of course. And and it's it's really incredible progress and that progress I think I would think of it as two several stages. So one was just not just one was what we saw with zk drawlabs and then of course already prior to that special purpose chains like zkash right wasn't just this the just the ability at all you have a protocol and you can make make a proof proof of it you can you can basically you can prove that the block of a blockchain is is valid.
What what we've seen since is like this this this this progression of the tech stack. So for example all of these earlier stages like again zkash early zk zk roll ups that what they all did is they basically they hand drafted the the rules of the of the of the chain that they were trying to verify into like very low level like it's called circuits. It's basically like you basically express it in like very low level constraints that you then makes use it's your knowledge proofs about. And where we've been we've been going from there is now we have this and you can really it's really it parallels the early progression of computers as a whole right we went from you have to specific you have to manually specify every individual system you want to improve yeah yes as like this the set of of constraints of circuits.
It basically went from there to introducing and it's it's such an elegant idea and but it's it's it's it's crazy that it works. It just introducing this intermediate instruction set. So so it's called an isa instruction set architecture and you can think of it like how a processor in a computer has an instruction set so x86 for example right like Intel or or not right basically it's it's it's what instructions does your does your process understand and the way these modern decay systems are now built is you you pick a one of those instruction sets like the one that is actually becoming the standard in a theorem right now is risk 5 risk 5 is is similarly in principle it's just like a list of operations that your processor could could do right like it's often run in a virtualized way so it's not actually run on real risk 5 hardware it's mostly run on in a virtualized kind of way but but basically it's just like a list of instructions and then you then write zero knowledge prove us that can just prove arbitrary risk 5 code so you're just saying like look give me any risk 5 code and I just have this machinery that can make statements cryptographic settings about it and what that now unlocks is instead of having to handcraft like a the early ZK EVMs there were literally handcrafted EVMs inside of the case systems now you can just literally compile you can just take basically basically you can take an Ethereum client instead of compiling it to whatever your local machine has as an instruction set I can instead of compiling it to x86 or something you're now just compiling it to risk 5 and then you just get the ZK proving for free because in in risk 5 like that's just like a typical kind of an endpoint for for compilers right so so basically you're you're modularizing the tooling and toolchain of course that's only possible now with all the efficiency gains in it because you of course you're losing some benefits of handcrafting all the optimizations but this this really it's it's a it's a phase change from how feasible it is to do this for just like big complex projects and so really the way Ethereum does the ZK EVM is again of course the real world is a bit more complex but but in principle you can really think of it we take the existing Ethereum clients and we just compile them to risk 5 and then we just have prove us that specialize in making proofs over risk 5 and that's that's just it's it's it's it's it's really amazing how far the industry there has gone to make that feasible and then the last jump the last big kind of conceptual jump from there to this is becoming feasible for us is the real time element so you we basically we arrived at that world and you could do that within you know an hour and sometimes if the block is actually convenient to prove maybe you can get that down to a few minutes whatever like that's the world that we used to be in and then we basically we have had this this massive industry collaboration effort that started like a year and a half ago with Justin Drake really like pushing super hard on this and these teams this is really mostly driven by pet teams outside of the theme foundation these teams have done an absolutely amazing job and I would say the last year was really the year of performance of real time performance throughout the last year teams just kept pushing this down orders of magnitude and now we're at the point where you can you can we are starting to to achieve the target so like we are actually able to prove consistently reliably prove a full Ethereum block within five seconds something like that and that's that's the basically that the promised land because now we have all the technological building blocks and now we can talk about the wall out and all these things but we have all the like from the cryptography side we now finally for the very first time ever we have all the elements we need to run a general purpose blockchain at real time proving speed and that's something that is never impossible before I really like the idea of there has been this you know three parallel paths of computing first starting with computers where they were first narrow and then we were able to make them generalized and then we were able to make them generalized and fast which is where you know modern computers are now to this day and then we created blockchains you know virtualized ledger based computers in the you know in the sky decentralized systems they started narrow with Bitcoin and then we learned to generalize them with Ethereum and then we learned to generalize them and make them fast with many other others more contract chains and now we are doing the same thing with cryptography started narrow with cryptography learned to make it generalized and now we are making them generalized and fast and that generalize in fast unlock on the computing tech tree of cryptographies now being able to be taken and bestowed into Ethereum which is what we're going to talk about for the rest of this episode so now that we have the zkevm and it's and it's in the Ethereum blockchain and you know it's up and running well what does that actually change with Ethereum when we get to this point how does Ethereum actually change right so of course we're not there yet but that's kind of that's where we're going and so why is this useful so coming back to scaling right I said that there's basically these three main elements of scaling there still depend with the IO and then the digital compute now the amazing thing about real-time zkevm is that it actually is the core of a broad like the way I would say this like it helps us scale all three of these but not just on its own but it's basically it's the unlocking piece that allows that basically enables a broader transition that addresses all of these elements of scaling and so that's why when we talk about zkevm to me it's more like the most exciting element of this broader change and that's why when you said at the top of the of the podcast this might be the biggest change ever I would agree not just the zkevm itself we're talking a second about statusness about a data availability sampling like all these things come together in to to to to to unlock this and so let's take it step by step so the one of those of those three constraints the one immediate impact you get us on the compute site right so because that's the nature of zke proofs right you basically you're able with very little compute effort on the verification to verify arbitrary length execution so no matter how much you fill the block now of course we can talk about constraints they're still block building some node some way needs to do that so it's not doesn't give you literally infinite throughput but basically right like you you can have whatever like length of computation you have you can compress it down into a constant size proof and then you can verify that with with with just very little compute so compute scaling that that's the in a way the easiest one that's the one that you that that you get very easily now you look at the other two and you're saying okay how does it impact IO right so historically traditionally when you execute any theorem block what you do is you start executing you do some compute at some point you want to load some state actually already at the beginning of a transaction you want to you know you need to load your account you need to load the account of that you're calling into that you're sending each two so you basically you immediately need to go to disks right so you have this this in time mixing of sometimes you go to disk you load value sometimes you do some compute then you go to disk again it's like this is in time mixing one actual change the three term that we're already doing before the KVM it's called block level access list so it allows us to it basically it it it it it it adds some annotations to block of like this is the data you'll need so actually what happens now is that you actually go to disk at the very beginning you you bring all the data and then you can you can do the execution but you still have this element of having to go to disk both before the block and then again after the block to go and like be okay but what's you know like we have to update all the values and then we have to also like compute what is the new state route so how does it look with ZKVM well there's a few things that that are fundamentally like improved by ZKVM so the the the important part is that ZKVM is the already takes in as part of the claim it's like hey assuming the the blockchain was in this state and I apply these transactions now then the next state is this so basically like you no longer need to go and load the data from the values from disk so you basically you're saving this IO on the on the load side naturally and then the the thing that you'd normally still have to do is you have to like go and still write that data so if you still have you still have the state of Ethereum so after you after you verify the block you still have to go and say okay these these values change right so you have to go and apply that change one that's no longer in the critical path so you can do that after you've already finished verification so if you have all the data you can already vote you can like say ah this block was valid and then afterwards I go and actually apply the update so in terms of like what is the count price of this unit swap pool or what's the balance of this account right like I might only go update this on disk after I already know that the block is valid so so that's that's a natural benefit you get but if you want to push it further we have to and this is what I was saying like this is one of those changes that is enabled by zkvm but it's its own change it's state stateless Ethereum or partial partially statefully Ethereum so what does that mean well instead of like today any node in Ethereum network is has to have the full state and that's with three execution that is that is unavoidable right because if you want to verify a block you have to go and again load all the data you have to have it all locally once you have zkvm that becomes optional because you don't actually need the data local to to double take the validity of the block right so so what you can do is you can in principle what you could do is you could throw away the entire data right so you can basically just you can only keep like this this root commitment and you can just always update the root commitment and that's it in practice what you'd want is because Ethereum nodes have multiple functions they also operate the Ethereum mempool they they have to understand validity of transactions in flight all these kind of things what you what you what you want to do is you don't want to run fully stateless you want to to run in what we're calling partial statelessness so for example there's this proposal called vops validity only partial statelessness so it means you specifically have a subset of the state and that can be defined by several different rules it can be say the balances of all the accounts or it can be I know if you are specifically interested in some state that belongs to you as the user or something you can you can define what state you're interested in but but basically now you you can you can you can keep a subset of the Ethereum state and that's totally safe because of zkvm right and and you can you can you only have to apply the diff you only have to go to disk you only have to have the IO overhead of updating that subset so that's the second basically like you have zkvm for compute now you have partial statelessness for for more optimized IO and also by the way for keeping your disk size can contain you'll talk about state growth maybe towards the end but but basically you know so you don't you don't have to have like a huge disk and then it leaves the third one which is bandwidth right so and how do you how do you actually like keep scaling the chain now with with with the ck a system while while actually keeping bandwidths were coming it's the same or even reducing them well that's yet another separate trick that that's also again enabled by zkvm but it's separate and that is you know no longer actually need to download the full block and that makes sense right because you kind of you you you get the the zk proof you have to download the proof and the proof tells you hey assuming there is a block with this hash or something once I apply the block this is the result and and that's proven so the only thing you need to know about the block is that it exists and that's a bit of a nuanced thing like why do you even need I mean someone clearly must have created it otherwise they could not have created the zk proof so why do you have to verify that it exists well that's for the nuanced reason that you can otherwise withhold the data like that's also the same for the that's why for example we even have blobs in the first place actually for L2's is the same story you have to publish you have to basically prove that the block was published so anyone can access it and anyone can get access to to the transactions that were applied basically so but what you can do is I mean that's again where like the synergy with the L2's it's it's just a beautiful story we've already built out specialized functionality for verifying the existence of data very efficiently without downloading it all it's called data availability it's called blobs right so what we will do is we'll take the theorem blocks and we'll just we just basically become our own roll-up in a sense we're putting the data into the blobs it's called block and blobs pip and and with that now now all in a theorem note has to do is just sample sample the data and we are being the progress of making that more efficient because we want to provide more data for L2 partners and that now naturally also benefits ourselves because now you can have more like bigger and bigger blocks while keeping the footprint in terms of bandwidth also very consistent so now you're right coming back we have ZKVM and we have partial status and we have block and blobs data 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 of you have state growth we can talk about state growth that we have to separately address and we you have things like being able to efficiently sync an Ethereum client there things like being able to efficiently run a an RPC note you know like what it furies doing these kind of things so there's more to scaling than this but but the the core story is that you have these three constraints and ZKVM directly and indirectly addresses all three you zoomed in on each one of those three and like as you just said you put those three together that's how a blockchain becomes a blockchain and we improve all three of those things I want to zoom out and really focus at that level of advantage when we reconstruct how a blockchain becomes a blockchain on on all three comprehensively the you said you really kind of said it when you said Ethereum uses its own data availability to be a ZK roll up as I understand it the ZKVM when it is up and running an operational and you know fully fleshed out and forked into into Ethereum the Ethereum layer one has the performance of a blockchain that is a ZK that would like be a ZK roll up in fact it maybe even is a ZK roll up it just also is on a the layer one itself and so we get all the performance benefits of roll ups we get all we get to ZK everything which unlocks the breaks undoes takes off the breaks on the Ethereum layer one and we already have the infrastructure needed with the data availability sampling for this to get done and so from a performance perspective the Ethereum layer one which is known to be a slow antiquated you know expensive blockchain to do computation on upgrades itself to have the performance properties of a ZK roll up is that a true statement that I just said yeah I think that's right and I think I think like just I think it's important to understand like why even does Ethereum like why why in what why is Ethereum so slow right like if we ask that for a provocative question the one really important element is that core to Ethereum's design philosophy is this this this guarantee that Ethereum never wants to compromise on which is verify like easy verifiability and auditability so the the the world is serum always wants to be honest that any anyone that want any user of Ethereum can easily if they want to verify or audit that the protocol is following the rules and why this is so important like people are always like ball but in practice many users don't do it and like other chains yes like for example if you if you're trying to to join one of those high performance chains it's actually it's really really hard to run a full node for one of those chains that scale just by increasing hardware requirements rapidly because not only is it you need a heavy machine but often you don't you can't even you're not even allowed to join the peer-to-peer network because it's it's so performance sensitive that they have to like have white lists for who even is allowed which nodes even allowed into the network because otherwise they're just too brittle right and they they just immediately collapse so so basically and why does it matter because I think people people think about proofstake always in this like well there's validators and they they vote on what's the constate of the chain.
In Ethereum validators get basically like get handed the kind rules of the chain by the community right like and any hard fork is basically a social decision of hey it's a social governance act the Ethereum community decides that now they are new rules rules to the chain and the the value is only vote for like okay given those rules like which blocks did I see which blocks follow the it's a it's a very it's a very there's no there's no individual decision that that in a test any theorem that makes right they just they just watch the chain and they just attest to what they see in other proof of state chains while in principle that should be the same thing what what in practice happens is that because any non-validator user of the chain is just a light client because you can't just participate in the chain you basically any any user in those chains just trust the majority of validators so in practice those validators determine what the rules of the chain are right like any in a chain that does not center about verifiability validators the fact to control what the rules of the chain are like the majority of validators want to run a different set of rules they can do that in Ethereum that's not the case validators can't accept or reject the fork they can just make a fork of their own they just get handed the rules by the community and the ultimate power always lies with the community right so like that's why that's why like verifiability so core to to ethereum and that's why we have been historically slow to embrace scaling because that would endanger that that property and now with zkvm we have this magical way of of getting the best of both worlds getting the poor verifiability and the full performance although i will say all of this is a bit too black and white actually what what's been happening so for example i'm not actually like i'm personally a while i'm involved with our zkvm work we have experts we have Justin who's been on the podcast before often many times we have we have kev who's doing absolutely amazing work there we've many people there that that full-time work on this and i'm actually focused much more on short term scaling and so while it is true that with with traditional scaling there's like a limit that you can reach and otherwise you you basically you have this fundamental trait of your kind of escape Ethereum historically has been very much in this mode of well we're we're working towards this eventual and state you know and we know we want to eventually do zk so you know we'll focus on that and as of like say a year year and a half two years ago i think the the mines the the mines that an ethereum has shifted a lot towards saying look we're now in this moment in time it's real about adoption is here right like it's no longer this future thing that we're building towards so so we have to like now and it's actually it's it's it's really it's it's a it's a it's a it's a very like non-trivial thing we have to find the right balance between still working on these like Manhattan project tile type jumps like real-time zkvm i really i think i really like like you said like i think it's the biggest thing in term probably will ever have done but we can't just wait for another three years for this to arrive like we have to do things now and so this is why i think we actually like we're now scaling is this perfect example we have this really good hybrid approach the next like we started last summer we we're saying zkvm is three years out and we will in a second i think talk about more the sequencing of the sector but we don't want to wait three more years right this is what the old ethereum would have done what we're actually doing is we are we are we now we we we we we came up with this with this scaling plan and it's it's a it's a it's a very continuous smooth function so you can our goal is basically we have this this rule of thumb we're saying our goal is 3x scaling every single year so we are we are increasing there we are we are increasing the throughput of the term blockchain by roughly 3x every year this is more of like a goal an ambitious statement it's not clear that everything will be able to hit that but i think we see a path at least it's a possible outcome and in practice the first three years of that scaling with traditional means and then from that point on basically we have the smooth hand over into the zkvm paradigm so it's not all just black and white any terms only doing zkvm where actually now i think i think we have the best of both worlds now we have like the next two three years we are we're doing the zkvm in parallel but we're still doing the traditional scaling and then we jump into the zkvm paradigm and so that means if you're a builder and you're considering building on is your model one you have to like instead of having to like exactly think okay one is this hard fork and what is things like no you can just say 3x every year you look at the throughput today you can and you can just like very simply calculate like you know what throughput do needs do i have is the i want to go fit or not it's it's it's a very simple story but under the hood it has this like these like two synergistic elements to it so that was long had something yeah well the idea is that we're are pressing the gas on stealing scaling on multiple fronts not waiting for the Manhattan project of the zkvm which you know the zkvm has been in the ethereum roadmap since genesis i think like we've understood theoretically of the possibility of turning the evm into a a zk algorithm and that you know we understood that theoretically back in 2015 now in 2026 and like oh no the this is now you know just an engineering challenge and we're like in the last mile of this and like it's basically almost here and in the meantime we are scaling on the more traditional front as well i want to get into the the qualitative nature of the scale of the zkvm so with block times and block sizes those are the two ways that you have throughput you have how big is your block and how frequently do those come you know you know the height times high times length so can we talk about what that the nature of scaling with the zkvm does does it help lower block times does it just increase block size i want on guard both fast and big blocks i like my blocks big and fast it would be great if we could increase the size of blocks but there is also very important element of this like block times is critically important for for trading and finance so how does the zkvm impact both of these variables right so don't say that question directly zkvm indeed it's not a panacea it specifically addresses the the the throughput level so it gives us much much much bigger blocks in the same kind of time constraints it's even to be fully confirmed it is it is a small extra strain on on the the timing just because you have one extra step right you have to like you have to have this proving step that's in between block creation and block verification you have to have proving but that's that's a minor constraint but it in itself does not give us a low latency and this is why when when you set the top like it's the biggest ever change I was actually tempted to say well to me that's true on the execution side of the blockchain right like same as with Bitcoin how we said there's the consensus mechanism proof of work in that case in our case proof of stake and then there's the actual processing of the blocks Bitcoin transaction ethereum transactions that kind of thing for for the extra execution for the transaction bits the the zkvm and the related changes really are the major story for the next you know five years we and in parallel to like now putting together this really really exciting roadmap on the consensus layer side and like the latency that's that's that's that's all a consensus layer story right because that's where basically the heartbeat of the of the blockchain is determined and so we have this this this this separate process and you should probably you know this is maybe setting us up for a separate podcast episode you should have bring someone on that's that specifically focusing on that type of work at the air for and or the the broad ecosystem because I think we have we have this really exciting roadmap there that's that's getting us to a much faster finality so right now finality in ethereum takes two epochs that's 64 slots on average two and a half epochs actually even so it's like long long amount of time we're bringing this down all the way to basically single slot finality to slot finality like it's it's going to come down like orders of magnitude so that's that's super exciting and then even within the single slot instead of 12 seconds we have a story there that's going to gradually get us down from 12 seconds to I don't know 864 much much much faster and then there's separate work streams around can you get even faster inclusion guarantee right like so that's the heartbeat at which the chain actually progresses and you get get guarantees about that's the result of of of your transaction but can you maybe get in principle like speed off light you know like how just round trip time confirmation that your transaction will be included right like ideally I want to click a button and before I can even like you know with a within the hundred milliseconds it even takes me to realize something happened boom I have to I have the confirmation like my my trade will be included and then within like say four seconds I know at which price right like I think that's the world we ideally want to be in and we have a really really exciting roadmap there as well but it is a separate roadmap from ZKVM okay understood understood so the ZKVM massively increases block sizes I don't know if you can put numbers around that and then it has a marginal increase in block times can that block speed come down in the future or what does it take for block times to get faster and is that something that we are aspiring to in the roadmap yeah so that's that's what I was was talking about like we are aspiring to that that's that's not not just aspiring that seems so indeterminate indeterminate optimism we actually have a plan that will come down it will come down as early as towards the end of this year that's not quite certain yet but basically like it's we're starting to make this approach as well and it will rapidly then become a major priority again maybe maybe in a part that I was wasn't sure of is like maybe the block speeds don't necessarily come down but transaction assurances come down very very fast and you're kind of saying well that's what people want anyways is that correct well it's it's basically you have three things you have the time to inclusion confirmation you have the time the actual time to the next block and you have the time to finality all three of these will come down the the heartbeat of the chain the time to next block will actually be the one that's only going to come down maybe by effect of three something like that from 12 seconds maybe to four seconds eventually maybe we can go lower but I don't wouldn't necessarily want to promise this I think the other two actually the more exciting ones finality will come down massively and and time to inclusion that's a bit more of an exploratory and process still but that also will come down massively so I think I think basically like yeah but block times as well will come down but none of this will be through ZKVM although of course it will be part of an integrated system right okay understood okay so you're saying there's a variety of ways in which ethereum speeds up broadly and then there's like zooming into what speeding up means you know has nuances which you just went into and as at least when it comes from a user experience perspective we have ways of providing essentially instant speeds from this perspective of a user okay let's talk about the the roll out plan for the ZKVM we are in phase of ethereum where there is no ZKVM in the future we will be a phase of ethereum where it is all ZKVM but it is not an acute moment as I understand it how do we go from A to B what does that what does that road map and of course because this is like a multi-year process it's it's as typical there's like very concrete steps as say for the next 12 months and then as you go further further into the future I can will point out that's the current plan these are maybe the open question these are the directions right so that's how that these things always work the interesting thing as I said top of a podcast is that it's not just a one-time hard fork there will be a one-time hard fork and that is about the eventual switch from what will come first which is optional ZKVM's for for those valid those nodes in the term network that want to consume proofs instead of re executing then at some point there will be this moment in time where we say okay now ethereum just runs on proofs of course you can still run a node optionally in in in re execution mode if you want to but by default like the network now guarantees that there will always be proofs basically and then from this point where this 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 like you're just still allowed to run a full re execution node and you're allowed to be slow and the network will hear you exactly 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 and 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 in 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 were all at that point then switch over to zk now again as I was saying before then is this phase of optional proofs so that that has not started yet like there's there's not right now we're in the proof of concept phase so like I think Justin presented at in Buenos Aires there's this proof concept of hey see my validator kind of principle already run on zk but that's not yet like if you're validator 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 to put this out there in a early production ready state where the idea is that we we will of course we will give very clear guidance of like these are this is the specific nuance level of confidence we have yet in the 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 them after that work run on this yet right because like if there is some budget with it or something like very much still want to have the backbone of all the major validators run run on this but if you are just a full node just for hobby purposes or maybe you're a very a validator on a on a very weak machine you might be tempted to just to at that point transition over so that will be the first step and and then one thing we haven't really touched on yet is that like well I guess a little bit is that there's actually quite a few technical requirements that that we need to to hit before we can move them the bulk of validators over and I can briefly go over those so one we already touched on for example is the block in blobs which will come at some point where we basically say look for the we now put the block into the data so there's also the sampling aspect to it if you are a re execution node you still download all of it but if you now are a ZK node you can start only sampling it but this will come after the initial optional proofs roll out so before then a validator basically has to download the proof but also has to download the full block still that's so it means they don't yet gain any bandwidth benefits they only get the the IO and the the compute benefits so so basically like we have the the block in blobs that will have to come we have to have in general networking improvements that that that are in the works we have the pricing meaning we have to actually make sure that the parts of the Ethereum chain that are especially hard to ZK verify we make a bit more expensive we basically rebalance the cost and then the most important technical dependence dependency for the for the mandatory proofs the the the full transition basically is actually it's related to the statusness element and that's specifically that we need to transition the Ethereum state tree over to new format like a long term listeners might be familiar with this like elusive verkl tree idea right and so verkl trees where this early Ethereum idea of like hey we can we we can't they have a mercury so like any account in Ethereum is part of this huge tree structure and every every block the entire tree is updated and you know at the roots you have a balance and you have your you know all these all these individual elements about your account the original idea was that transition is over to a more efficient format it's called verkl trees and that was the unfortunate fate that verkl trees had is that they they were just never really necessary they were always like one of those nice to have features back then back when we were not sure like how how aggressive we want to scale the chain how quickly will state growth become a problem there was there was some words in which it would have been a more urgent topic but because it we never went down those routes and it was always like right beyond the edge of urgent enough to ever do so we never ended up shipping verkl trees but the nice thing is we now already have a lot of prior work and now instead in now we can actually go directly to the next generation of cryptographic structures here and so instead of a verkl tree we're going to something that's basically called a unified binary tree it's somewhat similar the main difference is that it has a very different kind of like it instead of like a verkl tree is a very white tree a binary tree is a very narrow tree and the main I guess simple set the main difference is that the the binary tree is uses a post quantum secure hash function that is also very efficient to prove so it's already basically like fitting into this like future world that Ethereum is going to erase the verkl trees were basically the standard on piece that doesn't quite fit but the nice thing is we have a lot of prior expertise we have Guillaume who has been the champion of verkl trees and he's frustrated to know and that we never ended up shipping it and now his timers has come so like he's been he's been very excited he's now working towards this binary tree upgrade beyond the scenes already and doing an amazing job there with his team and and so actually over the next two years I would say the biggest the biggest kind of individual story that we'll have in Ethereum will be this upgrade to binary trees so that will that will probably over the coming months start to become a bigger topic people will start hearing about it and that will then enable very efficient stateless operations or partially stateless operations for now so to recap basically starting a year so from now we will roll out optional proofs those optional proofs will initially only be immediately effective for compressing computation and helping somewhat with IO load because but you still have to run in stateful node in mod mode and and then we will bit by bit start bringing these pieces into the protocol that unlock the full potential of zkvm and in parallel keep hardening the zkvm security properties so that by the time we are running out of conventional scaling means which is that's that's why all of this is so beautiful like we basically have exactly like three years of scaling like two and a half more years of scaling ahead of us of traditional scaling and at that point we will be ready to just seamlessly move over to zkvm so one year from now optional proofs two and a half years from now is plus minus this full transition to mandatory proofs and then we'll have all the pieces ready to then immediately keep keep scaling based on zkvm after that so that's that's the like the full out right so so as I understand it the way that it happens is that in a year we will introduce optional proofs the ethereum enthusiasts of the world who just you know love a theorem tinker with the theorem run nodes or theorem out of just pure passion will start to do these optional zk proofs they will be the pioneers of the transition of ethereum to be a you know a classical blockchain transitioning into a zk blockchain and that will give you know Ethereum researchers like you the the EF a lot of data of what it looks like to be in production because of these enthusiasts that are running this optionally because they just you know love Ethereum so much that will give you guys the information you need to do the prerequisite upgrades that are needed to actually get a full mandatory zkvm fork and as you alluded to it will also give us just insight into you know in production use of the zkvm maybe there are bugs if there are bugs we need to find them before we make the mandatory and so you know all the different clients will have their own version of the zkvm and we'll be stress testing all of those by using them into production basically there's a whole era of demo Ethereum zkvm and that that will take I think you said you know somewhere two to three years as we read out of classical scaling that will have we will have the hardened data and the information we will do the prerequisite work to unlock mandatory the zkvm around two and a two and a half three years from now the mandatory zkvm hard fork will happen and then if you're able to make the transition to this is now a zkvm blockchain the story doesn't end there though what happens after the mandatory zkvm fork how does the story continue beyond that point and just by the way to clarify a little bit for like for people that maybe think oh yeah now gung ho starting to release optional proofs for anyone who wants to be like a experimental you know like guinea pig here i think once when we when we are ready to start releasing this like they will be very explicit guidance around like what is like what is this for like a like what kind of production grade readiness does this have for which use cases i think it's more you can imagine more like it's about like how many nines after the zero after the after the comma right like if you remain it must never go down right like like we have we have we have 100 set up time and we're not willing to risk this so we are basically willing to to take to take extra precaution there but importantly if you're for example at some point running zkvm data and you actually there's a bug or something right the worst that happens like no one will get slashed right like it what what happens is just you briefly kicked off the chain and then you're you're automatically flipping over back to normal re execution mode and then worst case if we already in this partial status world you might have to first rethink some of the state right so worst case you're offline for couple hours and then you're back to back online back on the chain so so none of this we do it very responsibly just because you know just just to clarify this on breath and but yeah so and and basically i think the way that the these again absolutely amazing ecosystems k teams are talking about this i think last year was all about i would say it's was the year of performance getting to real real time zkvm this year is the year of security getting to like absolutely hardened there's also like the spits of security measure right like getting to level where we we are very confident in the security level then next year i think we'll be the year of productionizing the zkvm's and then the year after will be the the year of like transition to mandatory so like that's basically the performance security production and then manage like full transition that that's how we think about it is like one year at a time in terms of what comes after the transition well it's just i think and that's why we're saying earlier like with the further you go out the 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 state partial statusness we have the the the block and blobs and we have the zkvm to make advantage take advantage for scaling but we don't expect that once we get closer that it's like a one-time switch and now you can run it a thousand times faster instead we basically like right now conservatively quote unquote 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 ways notes sync or maybe you have to restructure the way so basically we're saying 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 a thousand x so basically the first the first three years of that we get traditionally then the next three years so these zkvm so in six years roughly a thousand x of where we started last year that's i think the again is this guaranteed yet no we don't yet we don't yet have we just we think we see a path we think we see a path that's our goal and then of course beyond that you could if you want to be like more inside that world like now you can think about nature for all apps so maybe the way we then keep scaling beyond that is not through just the single chain you know maybe then we're back to this kind of sharding type setup of multiple chains synchronously composed yeah we have to see but that's that's the plan what if you could trade gold 4x and global markets with the same tools and speed that you use for crypto that's exactly what bit get tradfi unlocks after strong beta demand including over a hundred million dollars in single day gold trading volume bit get tradfi is now live for all users inside of your existing bit get account you can trade 79 instruments across 4x precious metals indices and commodities all settled directly in us dt no platform switching and no fiat conversions this is bit gets universal exchange vision in action crypto and traditional finance side by side you get deep liquidity low slippage and leverage up to 500 x letting you apply crypto strategies to macro markets new to tradfi start with gold the gold usd pair is liquid macro driven in a familiar natural bridge between crypto and traditional markets try trading gold on bit get now at bit get calm click the link in the show notes for more information this is not financial advice few people in crypto put real skin in the game when they make public top or bottom calls the defi report is one of them the week before the october 10th flash crash michael from the defi report emailed his entire newsletter saying he's going aggressively risk off and sold the majority of his book from crypto into cash this is when ethos about four thousand dollars and bitcoin was 110 michael runs the defi report an industry leading research platform built on data cycle awareness risk management transparency and most importantly skin in the game we like michael at bankless we like his analysis and that's why you hear him on the bankless podcast about once a month and the defi report is giving bankless listeners one free month of access to the defi report so if you're looking for some sharp data driven analysis to make better informed decisions around your portfolio you can learn why and how michael called the top and what he's doing next all in the defi report pro check it out there is a link in the show notes on guard as i understand it client diversity is a big topic here why why is client diversity relevant to the zk evm and how does the zk evm impact it so i mean of course i think people will be familiar why client diversity is so core to ethereum and to ethereum's kind of 100% uptime right like the the redundancy factor you get you get from client diversity and so the the reason why this is relevant is just that like the nature of clients the nature of client diversity changes in this world and that is because again if we think back to how i explained how there's like this basically most most likely risk five kind of intermediate target for zk and then you basically just run a of course heavily modified but basically like a traditional execution layer client that gets compiled to risk five and then you take one of those new zk proving systems that then take the risk five code and prove proof execution over it right so what that means is now basically the ethereum execution layer notes live inside of the zk proves right which is of course conceptually like very different from what that used to be before and so what what it means is that now the actual node architecture is actually quite interesting you basically you run and that that is a little bit still tbd like it might be that you're still running this explicit split of of two clients like the consensus layer client and the execution client but the execution client's role is very different now it basically just verifies the proofs that were the one that you run locally right they just verifies the proofs and does some maybe like mempool networking that kind of stuff statement management but inside of the proof lives the this this this this the zk program that was also derived from an execution layer client so if you think about the roles of clients now basically it means that the the the the the the the the main question is like what about the diversity within those proofs right because the the outer the outer system we are we are familiar with but what about the diversity within those proofs and so the the nice thing is that in principle you kind of you get a very comparable very parallel type of mapping where you can just you know you don't just take a single execution client and and compile it into risk 5 you take multiple so you know you basically you take kind of you know the existing ones you know or like also there's the few ones that will be specially written for that use case you compile all those and then to to make sure that the redundancy is full stack not just the first half of the stack you also have multiple of these proving systems that take risk 5 because of course they could also be back in that part of the stack right like that take the risk 5 and prove over it so you say you have like as an example 5 of each right you have 5 execution layers that can be compiled into into this risk 5 and then you have 5 different proving systems and what you can do is you can basically build pairs of those so you can say and just as this really nice idea where you can even you can principle even like say performance match them so maybe the fastest execution client is paired with the slowest proving system so you basically so the pairs kind of balance each other out but that's just an idea but basically the point is you then have these these these combinations of like okay this execution client with this proving system and then in the end you're basically you're again in this example of 5 you you'd be in the world again where you have like 5 different types of proofs that could all and they're all kind of redundant they all have different they you know they're full stack different from each other the generally novel thing here is that today you run one execution client right like there's multiple of course and there's multiple consensus like that but you choose one one of each in this new world what you can do is you can just verify multiple proofs so for example and there's this idea and again just to use example numbers but they seem roughly ballpark right you could have a system where you say I only accept the block if I saw at least three different valid proofs words so I know that there's these five different ones and I have to have to have seen at least three of them otherwise I don't accept the proof so accept the block and so that actually gives you better redundancy because it's kind of almost as if every every if your 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 notes not within a node so actually it's a better story but it's also one way actually I have to be intentional so that you don't accidentally collapse any layer of the stack and there's just a site node there is this experimental idea and of course in the age of AI all the timelines collapse so who knows you know like maybe that's actually even short time viable but this experimental idea of a fully formally verified client and you could imagine right like an EVM implementation in risk five that is fully formally verified to be correct in that world that could basically then you would no longer need redundancy at that layer of the stack but again this is as I said like the forgot items have some uncertainty this is like one of those theoretical out there approaches but that of course would be would be also really nice to have anything some of that vacation in the age of AI will become a much bigger deal anyway so this might be really nice synergy yeah as I understand the clients are where all of the risk is with the ZK EVM and why where we have to be have like an extreme level of caution with the transition from a classical blockchain to a ZK blockchain and like if if something is going to go wrong it's going to go wrong at the client level I mean I suppose that's always where it would but when we you know we have you know Ethereum has over a decade of uptime because of client diversity because of how hard in these clients are and we are kind of resetting that to kind of go back to you know zero Lindy with the ZK EVM you know we have some properties that will be carried over but nonetheless there will it's it's risky in the sense that like we have all this great hard and infrastructure and we're kind of rebuilding it to be ZK and so we have to have this like extra levels of redundancy as you said like three proofs three correct proofs to make sure that you know not just two proofs because two proofs might have the same bugs we might prove the same bug twice so three things like this and so you know what what's your level of fear about this part of the the the transition for Ethereum from like the classical blockchain which is so hard and 100% uptime to go where we go here like how how scary is this oh it's it's a really good question right because I think the promise here is so huge that we're all very very excited about this but it is also generally like a huge a very very big challenge and this is why I think it's not at all natural that we are even doing this two-step rule out with the optional proofs and in the mandatory proofs in principle we could switch over at the end of this year right and we we already plan with this extra 18 months period specifically because of that like that level of certainty that we want and that that we project like that will always take some more time again it also gives us the extra time to roll out these other dependencies to really make use of CK proofs so it's actually quite synergistic but but still right like this extra 18 months delay is specifically for that reason and to be clear like we would always be responsible with it so like if it turns out 18 months are not enough of course we would like delay this false transition to mandatory proofs maybe we even find some more gains we can get on the classical scaling site until then right so like maybe we wouldn't need meta but basically we would always wait until we're like really really confident and it's it's not in principle harder but it's just as you said right like it's a it's a bit of a reset so like a lot of say our internal expertise both inside of the EF and across the client teams around security work testing work a lot of this is currently actively being restructured for this very new domain for this very new type of operations with CK understanding like what even are the weak points here like also say on the cryptography site like how we have we have absolutely world class cryptographers inside of the theme foundation and and in the ecosystem and and they are like very thoroughly like really turning around every single stone here in this in this overall like stack and really making making us understand like what are the critical points and again like how far are we from from being being willing to actually trust this and it is actually so for example there's to take take take a related example I'm not sure if you already hadn't maybe an episode on post quantum but that's also a big topic on Ethereum we were sure yeah yes mostly unrelated but of course of course there's there's synergies here and and it has a similar nature where I talked about the binary trees and part of the binary trees is this choice of hash function that you need in the tree and there for example we also like can't be not blocked but like the the the longest piece of the timeline there is talking with our cryptographers we have a candidate like a set of kind of a family of candidate hash functions but getting to this point where we're saying look they are actually robust enough they have been around long enough that we actually trust that they are secure right like especially something a cash function so quickly you can't really prove security you're just it's it's basically like a lindiness to it right like how long has it been around how many people have tried to find vulnerabilities as there's been anything found right this kind of thing and so some of these things you could just can't accelerate right like how many years of academics having looked into this heads there been right that's just like a hard constraint and so both in this post quantum but also then binary trees we also using for making use of CKVM so it's not directly CKVM but making use of them there's just some some elements of the timeline there that are dictated by the security needs that we have and and we just can't cut corners so it's a bit concerned but I think we have everything responsible about it yeah yeah yeah which is why it's taking you know not a short amount of time so just to maybe conclude this podcast the timeline it is now the start of 2026 by the time we hit 2030 is a good guess for when we think we will have the full power the full properties of the ZKEVM you're not in your head is that sound right that sounds right and I think we will be still probably in the process of making full use of it for scaling so we will be hopefully 2030 will be another three X year maybe more than three X because we have AI and the hard for time ends are compressing but basically another three X year in 2031 will look like another three X years so we will be on this continuous scanning path but already squarely in the ZKEVM backed side of that scanning path right right I guess one point you made earlier and I guess it's worth re-emphasizing here is we are the the aspiration of Ethereum is to do a 3X scaling increase every single year not just for the next three years next three years for classical scaling and then the next three years after that for ZKEVM scaling so you know while I am excited about the ZKEVM and I think it's incredible and why I want to like rally the Ethereum community around it acutely there won't be a ZKEVM moment as felt by the trans actors users of Ethereum because we are doing a three three X scaling per year for the next six years first with classical then with ZKEVM and so you know while the merge you know acutely transitioned us from proof of work to proof of stake EIP1559 acutely transitioned us from you know to have the burn and better transaction UX and like same thing with 4844 is an acute transition this won't be that because we are scaling anyways but nonetheless I think it is important to know that like only Ethereum will actually be able to access you know then the final you know years three through six of scaling in that capacity because this this is if you're a Manhattan project like we said only Ethereum has been working on this it's been working on this since Genesis and while Ethereum makes this transition from a classical blockchain to a ZKEVM blockchain it will be leaving every other blockchain behind in the in the previous classical era and so maybe that's why I'm so excited about it is like Ethereum is making the the generational leap to the next gen blockchain and no other blockchain will have these properties that we've been discussing about on this podcast well and I think this is this is what I wear said earlier like it's not it's not just that like it's not an accident that you won't notice this this transition like it's actually by design like we're trying we're like I think in this in this in this moment time we're really trying to balance this continue the strength of Ethereum of being able to make these like leaps these these these paradigm jumps that I think are like like other projects really struggle to be able to follow I think again that's why we also just naturally have the post quantum properties I think many chains will actually like struggle quite a bit with with actually getting there and at the same time realize that now we're no longer in the sandbox mode we can't just like say I just wait just wait for three more years like how you know like what don't be some patient like no no no I mean people are coming on chain agents AI is like coming on chain like today right so like I think it's important that we basically just like we we we are a continuously scaling blockchain and it is it's our responsibility to under the hood make that happen and like use whatever like both traditional and magical future decay means necessary to make that happen I will say because you said like no one else will be able to do that I think I actually think it's one of those areas where there's again natural synergy between Ethereum and like the EVM L2 ecosystem I think one thing that for example we didn't talk about it all but then I'm very excited about is that like again similar to how the initial jump to non real time the KVM came mostly driven by the R2's I think now that we are driving from the one side this this move to real time the KVM's the R2's will also be huge beneficiaries of this because they will also just just become the like like and gain the ability of real time settlement so that means also say all the like bridging pain in the across the R2 ecosystem right like oh in principle it takes either I use a mint and burn bridge or it takes like seven days for my asset to move across chains all of us will disappear right it's going to be a few seconds for any asset to move from any or two to any other and any real time ZK EVM proven out to to any other real time ZK EVM proven out to is through the Ethereum L1 or of course into or out of the Ethereum L1 so I think it's yet one of these cases where the fact that if you're part of the Ethereum family we like this is kind of this is the ecosystem that really has this principle approach to things you get all of these these benefits for free you're basically you are you are on the on the on the principle architectural path and I think that has always been our competitive advantage and I think while doubling down on the competitive advantage I think we really are already trying very hard I think we have to keep trying even harder to close where maybe we've had the competitive disadvantage which is I think that Ethereum in the past has sometimes been a bit more too much in this pure research mode and like maybe discounting the type of activity that already existed and saying ah that's just sandbox whatever like the real real world adoption will come later and then then we'll start focusing on it real world adoption is clearly here and so finding the right balance I think is the ongoing challenge it's what for example to and shallway in there in the time at the third foundation have like really put a lot of focus on and I think that that's how it would like narrate the future of Ethereum the both the Manhattan projects and the short term focus and ownership of of the protocol as a useful thing today one theme that I've picked up on a handful of your answers throughout this conversation on scars that there seems to be a significant number of second order positive effects of the ZK EVM that are not related directly to the main quest line of the ZK EVM which is just straight you know layer one scaling but solves a bunch of second order problems you know you know layer two scalability and composability being the one that you just said how how big is that second order effect like am I correctly identifying that it's actually like somewhat large in the positive second order effect number yeah I mean I think there's the immediate second order like the is your set like the the things that like just that the benefits to the broader EVM ecosystem and especially EVM or two ecosystem because again and well I guess maybe I didn't mention this so much like I think I think it's much easier to adopt or to to to benefit from the technology for tools for EVM tools where it's like other EVM ones I think while I think that's actually it's also very exciting for them I do think basically you'd have to re architect your entire chain right similar to how I was saying like the theorem I won it's the ZKVM is the core piece but there's like many elements to it right whereas because their tools already have this this this architecture where they are just like naturally settling on the one they just have to compress the timeline like the settling time like for them it's like it's almost like a trivial and upgrade to follow us to this world and like so I think I really think that's the unique synergy for the Ethereum I won and then the Ethereum EVM tools I think longer term if I'm talking beyond blockchains here for a second I think we've already seen how in the world outside of crypto we are starting to see this like second generation of cryptography really impact and it become very impactful it took a while it took a couple years for people to start taking it seriously and so I think you can start to see it with all kinds of things like Microsoft is you know doing things like a lot of governments are doing like I know ZKID type of type of systems you're starting to really see use cases that go beyond just blockchains blockchains are like the most valuable so that's why we always we always see the technology there but you can you can imagine a world and especially once you have this real-time element unlocked you can you can imagine a world where like I know just to you know to to be futuristic here like AI agents might use real-time ZK proofs to make provable verify statements for trustless interactions with each other right like some of that might be on chain for like you know for direct asset tech detections but some other things might just be literally just I'm just proving that I've access to this data and this data as the structure and that I or you know all these kind of statements you can just down trivially real-time proof that you just couldn't before so I think that's a five year down the road maybe kind of thing but five to ten years but that will come and that I think will be really exciting and then for example I don't know if you've seen there's like more and more countries starting to introduce I don't know social media bands for like miners and that kind of stuff and I usually that's implemented in the super dumb way you have to like just they use a service you have to upload your ID to the service right and if we can replace that with like a ZK ID system where you really don't leak anything other than I own an ID and my birth date is about this level this threshold it like obviously that's a much preferable world so I think we are currently like I think blockchains and especially the theorem ecosystem is currently like funding this massive leap of the cryptography toolkit that we have and with some delay five to ten years delay it will also hit the non blockchain space and I think it will be super impactful yeah one you know idea I've had is that you know Ethereum and all the research that we have invested in over the years hopefully is one big contributing factor to like kind of restoring the brand of crypto by helping the world overcome some like generational challenges as you've as you've correctly identified you know you know crypto certainly have the best brand at this present moment hopefully with some of these you know sci-fi tech advance advancements this Manhattan project that Ethereum has been working on we don't just you know improve the nature of our own blockchains but we improve the nature of the world around us and the second order effects upon Ethereum as a brand as an ecosystem eth price is benefited a downstream of all of that on scar this has been a super educational episode I really appreciate you coming on here and giving me and the bank list nation the time about the ZK EVM I think you know broadly the crypto industry is looking for reasons to get bullish about something I think this is a very valid thing to be excited about and to be bullish on and so I'm trying to rally the troops around the ZK EVM fork just in mind sharing education and I think you you've done the job I've I've hoped we could do here on the episode today so I thank you for that sir sounds good and one last caveat just to repeat this right like I'm not personally a ZK expert I mean obviously I'm in the loop on a lot of these things but I'm more like our broader scaling experts so this is part of part of my job but but really we have we have absolutely amazing people so I'm sure I did I got like some of the minute minute details a little bit wrong and and the people will scream at their at their monitors but I hope I got the the broader picture roughly right and I agree it's very exciting I think both the execution layer side the ZKVM scaling story and then on the consensus layer like these these next generation upgrades we're planning there very very exciting I do think we need we should we should understand though in this moment in time also I think we should try to become more the boring infrastructure layer and I think we should really like ready the stage for the applications and so I'm personally like incredibly excited for like the like the actual real world application side of crypto we're really starting to see this come online a agentic payments real world assets stable compayments all this is incredibly exciting I think it's a great moment to be in crypto and yeah and of course one last shout out there maybe actually if anyone listening to this was actually interested excited by these technical details of everything we talked about though and which it wants to help on the infrastructure side do reach out to me I don't know either on a twitter DM or unskated theorem dog we also always in principle are hiring if if any smart kid out there like really would want to to join us here on the infrastructure side it's not the only exciting thing in crypto but it is still very very exciting and please come join us we'll put yeah let me make sure your Twitter is in the show notes on on YouTube or Twitter or wherever for people are listening to this podcast on guard thank you so much thank you very much bank location you guys know the deal crypto is risky you can lose what you put in but nonetheless we are headed into the future we're going to zk the future to not with the help of the the zk evm that's not for everyone but we are glad you're with us on the bank with journey thanks a lot