Ethereum's next hard fork is here and we're joined by Tim Beiko from the Ethereum foundation to walk us through and explain what it all means.
He shares a comprehensive guide on each and every EIP along with what comes next, Dencun, Pectra, and beyond. If you want to be up to date with the state of all things Ethereum this is the episode for you. ------ 🏹 USE PODCAST24 FOR 10% OFF https://bankless.cc/Citizen2024 ------ 🎧 Listen On Your Favorite Podcast Player: https://bankless.cc/Podcast ------ BANKLESS SPONSOR TOOLS:
🐙KRAKEN | MOST-TRUSTED CRYPTO EXCHANGE https://k.xyz/bankless-pod-q2
🦄UNISWAP | SWAP SMARTER https://bankless.cc/uniswap
🔗CELO | CEL2 COMING SOON https://bankless.cc/Celo
🗣️TOKU | CRYPTO EMPLOYMENT SOLUTION https://bankless.cc/toku
🛞MANTLE | MODULAR LAYER 2 NETWORK https://bankless.cc/Mantle
⚖️ARBITRUM | SCALING ETHEREUM https://bankless.cc/Arbitrum
------ TIMESTAMPS 00:00 Start 04:44 Naming "Dencun" 08:40 Overview on Blobs 11:31 EIP-7514 (Epoch Churn Limit) 14:42 EIP-6780 (Self Destruct) 19:27 EIP-7044 (Signed Voulentary Exits) 20:49 EIP-7045 (Max Attestation Inclusion) 21:49 EIP-4788 (Beacon Block Route) 25:31 Opcode Changes 29:58 What's Next 37:53 Future EIPs 41:37 Max Effective Balance 45:22 Inclusion Lists 50:40 Additional Noteworthy EIPs
------ RESOURCES Tim: https://twitter.com/TimBeiko
ETH Magicians: https://ethereum-magicians.org/u/timbeiko/summary ------ Not financial or tax advice. See our investment disclosures here: https://www.bankless.com/disclosures
No summary for this episode yet.
The way that I've been explaining this is like, we are getting Stone Age blobs with Dankoon4844, but then the blobs can evolve into like sci-fi blobs independently of any sort of heart fork. And so the blobs are going to be able, is that true? Welcome to Bankless, where we explore the frontiers of Ethereum. Today on the show, I brought on Tim Baker. It is Heart Fork Day. It's either today or tomorrow, depending on when we release this episode. Dankoon is here. The blobs have arrived. We unpack what is beyond the blobs in this episode with Tim Baker, however, because there are other EIPs after EIP4844 that are going into Dankoon.
And then there are all some EIPs that did not make it into Dankoon that will come in the next Heart Fork, which is Petra. And then after Petra, there are going to be further EIPs. And so Tim Baker on the episode today walks us through all the EIPs that are coming now, coming soon, and coming later. So if you want to really dive into the 300 level, 400 level, decently technical future of Ethereum, this episode is for you. Emphasis on this being a pretty technical nerdy episode, really for the people who are like, you know, listeners of the daily-gway Ethereum core devs, you know, people who have been, I want to explore the bottom depths of the Ethereum Robblehold.
This episode is for you. Banklessation, we're going to get to our conversation with Tim Baker right now. The first thing we want to talk about is some of these fantastic sponsors that make this show possible. If you want a crypto trading experience backed by world-class security and award-winning support teams, then head over to Kraken, one of the longest standing and most secure crypto platforms in the world. Kraken is on a journey to build a more accessible, inclusive and fair financial system, making it simple and secure for everyone, everywhere, to trade crypto. Kraken's intuitive trading tools are designed to grow with you, empowering you to make your first or your hundredth trade in just a few clicks.
And there's an award-winning client support team available 24-7 to help you along the way, along with a whole range of educational guides, articles, and videos. With products and features like Kraken Pro and Kraken NFT Marketplace and a seamless app to bring it all together, it's really the perfect place to get your complete crypto experience. So check out the simple, secure, and powerful way for everyone to trade crypto, whether you're a complete beginner or a seasoned pro. Go to Kraken.com slash banklists to see what crypto can be. Not investment advice, crypto trading involves risk of loss.
Cello is the mobile first EVM compatible carbon negative blockchain built for the real world. Driving real-world use cases like mobile payments and mobile defi, and with opera mini-pay as one of the fastest growing Web 3 wallets, Cello is seeing a meteoric rise with over 300 million transactions and 1.5 million monthly active addresses. And now, Cello is looking to come home to Ethereum as a layer 2. Optimism, Polygon, Matterlabs, and Arbitrum have all thrown their hats in their ring for the Cello layer 2 to build upon their stacks. Why the competition? Cello layer 2 will bring huge advantages, like a decentralized sequencer, off-chain data availability, secured by Ethereum validators, and one block finality.
What does that all mean for you? With Cello layer 2, gaspies will stay low and you can even pay for gas natively using ERC20 tokens, sending crypto to phone numbers across wallets using social connect. But Cello is a community-governed protocol. This means that Cello needs you to weigh in and make your voice heard. Join the conversation in the Cello forums. Follow Cello on Twitter and visit sellow.org to shape the future of Ethereum. Are you launching a token? Is it already live? How are you managing the legal and tax obligations for providing token grants to your team? It's no secret that token management gets complicated.
Between learning all the legal language and tax obligations in every country that your team is in, token grant management can feel like an obstacle course. But it doesn't have to. That's where Toku steps in. Toku provides practical tools to handle token grants, allowing for effective oversight of token distributions and payroll tax compliance for employees, contractors, advisors, and investors. Also, handle tax withholdings through their real-time tax calculations that can be done by Toku or integrated into any payroll EOR providers in any jurisdiction. Toku is a trusted provider of protocol labs, dydx foundation, mean of protocol, and many more.
Get started for free and make token compensation simple at toku.com slash bankless. Bankless Nation, I'm here with Tim Baker, the coordinator at the Ethereum Foundation leads the All-Core Dev calls. Tim, how you doing? Good. Thanks for having me. Yeah. Exciting times in Ethereum. We are the week before the hard fork rule. Actually, error this either the day before or the day of the hard fork. So happy hard fork day for everyone listening. Tim, I want to go through Dankun and the high-level EIPs will just talk about, we'll just run through all of them just to really unpack what's going on in Dankun.
And then we'll talk about what didn't make it into Dankun, which is, which means like, what are the EIPs still in the All-Core Dev's mempool that we know we want? So included just didn't make it into this particular hard fork. Sounds good? Yeah. Cool. But before we do that, can we actually talk about the whole naming convention thing? Dankun is a weird word. I don't think it's a word. The next one after this is Petra or Electra maybe. Can we talk about how the naming convention works on these hard forks? Like, what does Dankun mean? How did it come to be? Yeah. Yeah, that's a good place to start.
So on Ethereum, you know, before it emerged, we had both the proof of stake chain and the proof of work chain sort of updating independently. And both of those sides had like a different naming scheme, you know, the name upgrades. So on the proof of work side, we started, we had, you know, like, Frontier, Homestead, Metropolis. And then for a couple of years, we just used variations of Istanbul city names. So Byzantium, Constantinople and Istanbul. And then we sort of ran out. So we started using DevCon city names. And we had the Berlin hard for our Berlin hard for London, just following the DevCon city orders.
And so now we're up to Cancun, just following DevCon city names. And we had a little actually exception there. We called the Merge Paris as a shout out to ETC, which was the big first big community hosted conference. So we use those to specify the names for the execution layer upgrades. On the consensus, they like using stars instead. So they use the name of stars and they go alphabetically. So the first one was called Altair. Then it was Bellatrix and then Capella and now the Neb. But in practice, if you're just like an Ethereum user, the execution and consensus layer upgrade happens at the same time.
And there's like different code on both sides. So we need like different name to refer to like the actual changes to the proof of stake side of thing, the actual changes to the EVM. So we use like Cancun and the Neb to refer to those, you know, subchanges. But because the upgrade all activates at the same time, we decide to match those names together. So we have Dencun, which is a mash of the Neb and Cancun. And then the previous fork, yeah, Capella was a match of Shanghai and Capella. So yeah, we've been using these. And in the future, if we had a fork that was like just one side of the chain, then we probably just use like a city name or a star name, but when they happen together, yeah, we couple the names.
Okay. So it is actually possible to fork the consensus layer and not the execution layer. Yeah. And in practice, the fork basically happened independently. So we tell the consensus layer at this epoch, you know, fork, we tell the execution layer at this timestamp fork and the timestamp just happens to be the same as, you know, the epoch start time. But there's no, there's no, you know, like reason for them to like have to fork and lock step. And we want to preserve this because imagine there's just like a bug in the EVM that we find tomorrow. We can just ship a hard fork on the EVM and the consensus layer doesn't need to know about it.
And vice versa. Yeah. Okay. But the people who are running this CL and the EL, the consensus layer and the execution layer are the same people for the most part. Yes. Yeah, correct. So they'd run a node like you have to run both, but it's just and in this hard fork, you need to upgrade both, but there's no, there's no, there's nothing that forces both to have to be upgraded. So if say we had an emergency hard fork on the consensus layer, we could have an update just saying, like look, upgrade your consensus layer node, your execution layer node is fine. Beautiful. Okay. All right. So that gets the naming out of the way.
We have the CL and the EL combined. We have earthly cities and astral stars being portman towed into the same word. And so that's how we came up with Denkune. And then Petra is the next one. Yes. So Prague and Elektra have been merged into the Petra. Yeah. Okay. Beautiful. All right. So Denkune is known as the blob hard fork, the hard fork that we get the blobs, EIP4844. It's a cool one that gives it the area of my zone and trying data availability layer. We've talked about blobs on bank lists. We've had entire episodes dedicated to blobs. Listen to our episode with Domathy about blobs if you want, really want to dive into blobs specifically.
I don't think we really need to dive into that one because we've covered it so extensively before. But Tim, like, since we're so close to the hard fork day, like what do you want to elevate about blobs? People are like speculating about like gas fee reductions on layer 2s, but I know we don't really know. Is there anything before we move beyond blobs that you want to talk about? Yeah. We did talk about them. I think the one thing I'll say is what's neat about this upgrade is it sort of sets the stage for full bank sharding after. So you can think of this upgrade as like almost the front end to blobs where we have all of the new sort of infrastructure and scaffolding that the network needs to use them.
So we have like a new transaction types which L2s can like migrate to to use it. And then in the future, when we have more scaling capabilities with stuff like full bank sharding, we can just do that in the background and L2s will not have to like upgrade. They'll just be like more blob space that they can access on the network. So I think that's like a really cool thing where all the L2s have to like do work to support this now and they've all like done it and are in like the final stages of testing. But hopefully, they never have to do anything again that like support blobs and they just ends up being more blob space coming on.
So I think that's something that's like not not discussed enough where yeah, we really set like the entire architecture now and we can just keep it expanding in the background. Right. The way I've been explaining this is like we are getting Stone Age blobs with 10 Koon for a 4 4, but then the blobs can evolve into like sci-fi blobs independently of any sort of hard fork. And so the blobs are going to be able, is that true? Depending on how you approach it, you might need a hard fork, but it's more that even if there is a hard fork, the L2s won't have to do anything like so for now, they post their data and call data so they have to switch the type of transactions that they make.
But in the future when we have more blob space, the blob transactions of like next week will still be valid and will like integrate with all that automatically. Right. Okay. So the future call data, which we call blobs, is just going to be able to fit more stuff without, and the L2s won't really care about like how big they are. They will be able to leverage them all the same. Correct. Yeah. Okay. All right. So that's blobs. We'll talk actually talk about peer dash, which didn't make it into Dankoon. We'll talk about that towards the end of the show, but this is like one of these like a blob evolutions, blob blutions, max ad max epoch churn limit.
SEP 7514, that's also coming into Dankoon. What should we know about that? Yes. So right now on the beacon chain, when validators come in, the amount of new validators that can start validating per block is a function of how many validators are already there. So as more and more validators come in, we accept more and more each block. And the reason, you know, for that change originally was just you don't want to like overwhelm the validator sets with new validators in case of like an attack or something, but as you have a bigger and bigger validator set, you can sort of bring more people in quicker.
That said, just to say, just to state that really simply, the size of the rate of change of validators is a function of the total size, total supply of validators. Correct. Yeah. Correct. Yeah. So basically since the launch of the beacon chain has been like up only because there's been more and more validators and we've like, so there's more and more validators and we've therefore accelerated the rate at which we add new validators. And recently, I don't know, in the past year or so, there's been a lot of like discussion and debate around, you know, should there be a max amount of validators on the network?
And does even at the current rates of growth is the amount of validators going to end up being too much in terms of like the amount of messages that they gossip on the network and sort of the requirements that that implies in terms of bandwidth. So the idea with this proposal is that instead of making the number of validators each block a function of how many validators are there, we simply cap it at eight per block. So we have that as a ceiling. And this basically slows the rate of growth and it one lets client teams deal with like the increase in validator set size so that they can, you know, have a bunch of performance improvements and what knocks the deal with that.
And two, it sort of lets the entire community have a discussion around like, okay, what's like the right share of validators that we'd want to have on the network and ideally not end up having that discussion in a world where like, I don't know, say we decided we never want more than 50% of eat to be steak for whatever reason, but then there's already two thirds of the eat steak that's kind of an awkward place to be in. So this just gives us a bit more breathing room to figure out the right path forward. Okay, so there is going to be a cap. So on the rate of change, and when is that cap hit? So we're already, I don't know if we're past it already, but we will be at, like at the hard fork, the cap will be eight basically.
Okay. Okay. So eight validators per block, eight times 32 East per block is the constraint. And the idea is that just we just want to, we want to buy ourselves some time before Ethereum discovers it's long-term equilibrium with the eat steak. Yeah. Correct. Awesome. Self-destruct only in the same transaction, EIP6780. What does this do? Self-destruct has always been one of these like weird words that I see every now and then. People have like strong feelings about it. What's self-destruct and why? What is this EIP doing? Yes. So self-destruct is pretty straightforward. It's how you can delete the contract for Ethereum.
So you have to specify this in advance, but like if you want your contract to destruct, there's this upcode which will delete it. And the rationale for this upcode was that if we want people to like clean up after themselves, you know, it's nice to give them a mechanism to do it. In practice though, it hasn't been used much for that. It's been used in a bunch of like really weird funky ways, but it's not something that's like keeps Ethereum state size, you know, smaller than it should be. So the value of the upcode is not like what sort of we expected in terms of the protocol. And the biggest problem with self-destruct is it's the only upcode where when you call it, you don't know how much computation you're going to run.
So if you call self-destruct on like a tiny contract, self-destruct gets the address passed in as a parameter and then it sort of finds this address and deletes everything that's there. If it's a small contract that's super quick, but if it's like a huge contract, imagine you called it on like some massive NFT contract with like millions of balances, then it's like in that same amount of time, you now have to delete all of this. And maybe in analogies, you know, on your computer, when you move a file to the trash, it's sort of instant, but if you delete like a thousand pictures, you know, it says like moving them to the trash and it's like loading.
So self-destruct has like that behavior. And that's bad for Ethereum because we want like the gas that we charge for upcodes to reflect the cost of computation. And for this one, we sort of camp. And now it's kind of bad, but not the end of the world because of how Ethereum is structured. But we have this long term goal to move towards stateless clients and this requires changing how we store data on Ethereum. By virtue of like how we change that, self-destruct that becomes like insanely long to run every single time. We just can't like afford that. Yeah. Yeah. So basically removing it is the first step towards that.
And so what this EIP does is when you call self-destruct, it will not destroy the contract anymore, but it'll still send the money back to like the address you specify. So this is the other thing that self-destruct does. If you delete a contract, you get to say where to send the money. Obviously, we don't want anybody's funds to be trapped. So when you call self-destruct after the fork, all it does is it transfers the eth in that contract, but it doesn't actually destroy the contract. And that said, there are people who use self-destruct in a bunch of really weird ways. And one of those edge cases is sometimes people will like create a contract and destroy it in the same transaction.
Sometimes they do that to burn some eth. I believe that's how optimism goes like withdrawal bridge works. It'll like create a contract with some ethernet and then self-destruct it and send it up to zero address zero or something and that's like they're weird trick to make it work. And those cases, we can still support because you don't actually have to write this contract to this because it's all in the same transaction that it's happening. So this is why the EIP has like a super long name. It's like, okay, we managed to get the functionality that we want. We like deactivate it, but then we get to preserve this edge case, which was relied upon in a lot of like critical flows, so no contracts breaks.
Yeah. Interesting. I sometimes when I talk to people like you about this, I'm like, once again, realize how deep some of these like technical like EIP rabbit holes go. Yeah. And we've been trying to do this for years. So it's nice to actually see a chip and the note is like, okay, we found like the sort of edge cases that we can handle and not break things. And this is the final equilibrium of self-destruct. This is the last EIP that self-destruct will be relevant or? Yeah, I think so. I mean, it's hard to predict the future, but I think it does everything we want at this point. Okay. Cool. So we're confidently putting it on the shelf.
Maybe we pull it off. Hopefully not. Yeah. Yeah. So we always have to preserve this property of like sending people as money back because if imagine you had a contract that you thought you were going to self-destruct in a year and there's a tons of eat in it, like we can never stop you from getting that beat back. So like that functionality will always stay there. Okay. So this is minimum viable self-destruct. Yeah. We've discovered ourselves. Yeah. Cool. All right. Moving on. Perpetually valid signed voluntary exits. I'll say that again. Perpetually valid signed of voluntary exits EIP 7044. What's this?
Yeah. So on the beacon chain, you can pre-sign an exit message. And up to now, I don't know why I wasn't involved in that design, but like these messages were only valid for like the next two hard forts, I think. And this is, and I guess, you know, again, I'm not sure why they made that decision at first. But in practice, it turns out like people use these messages today to build like trustless staking constructs where imagine I'm like a staking operator for you and you want to always be able to withdraw your funds. What I can do is I can sign an exit message with your validator, give it to you.
And then if I start doing something badly, you can just go and publish that message and your validator gets exited. And you don't need me to like do that for you. The problem with that with the current messages is only last two hard forks. So you need to like trust that I sort of give you a new one every hard fork or something so it doesn't expire. So this EIP just makes a small change to make those messages valid forever. And it can allow you, it can allow you to have like a one time sign message where, okay, you receive this. You know, you can always exit your validator, even if you're not the one operating yet.
Okay. Seems pretty straightforward. Yeah. Yeah. All right. EIP 7045 increase max attestation inclusion slot. Oh, boy. This is like the most technical BKJ DIP, you know, you shot Danny Ryan on the show and he can tell you all about it, but TLDR is it just increases effectively the max distance that you can include an attestation for in your in your block. There is some security rationale for this, which again, proof of stake researchers can get into as a user, as a validator, this all just up and automatically it just changes like how far you go when you're looking at including at the stations.
So if you're an attestor, you just have more time. You have more space to attest. Yeah. Correct. No, sorry. So if you're collecting attestations, collect an attestation, you can collect them farther. So it means that the like first attestation of an epoch basically gets like twice as long of a valid period it can be included for. Yeah. Okay. All right. This one's pretty cool. EIP 4788 beacon block root in the EVM. So beacon block, that means we're talking about the beacon chain. The root of that block is going into the Ethereum virtual machine. So this one is spanning the consensus and the execution layer, correct?
Correct. What's going on over here? Yeah. So today we have, you know, ever since the merge, both chains run alongside each other, but there's no ways to make proofs about the state of the beacon chain on the execution layer. So in a smart contract without an external oracle. So if you want to say like, you know, this was the state of the beacon chain at like slot X, you have to rely on the external oracle, which is not great. So what this does is it creates a new contract on Ethereum where every block, we just store the latest block hash for the for the beacon chain blocks and have the header there so that you can trustlessly make proofs against it.
So this is really helpful for like a bunch of say, staking pools that want to make proofs about like the current state of the beacon chain and whatnot and not have to rely on an external oracle. So it just makes, yeah, a bunch of like, yeah, constructions more trustless. Yeah. So this make this connects this is actually, I think one of the one of the big I'm going to make this the second biggest EIP inside of this hard fork after four or four, mainly just because like it connects DeFi, Ethereum's DeFi application layer to the Ethereum consensus proof of stake staking layer. Yeah. You said like, staking pools like this affects the rocket pool odout node.
Like there's this small doubt inside of the rocket pool system that connects basically this information, the state of the Ethereum consensus layer and the ETH and the staking contract to rocket pool. This also, it's helpful for eigenlayer and AVS is because they need to know the state of ETH on the beacon chain so that, you know, when AVS is make a slashing event and the slashing event occurs, other AVSs can, can know about it. Yeah. Yeah. Yeah. Yeah. Basically it removes any sort of oracle risks around that information, whereas now all of those projects have to trust some oracle to tell them what's up on the beacon chain.
Yeah. Yeah. Vitalik actually put out a recent tweet about how he was like having a change, not like a whole hearted like 180 pivot change of mind, but like a change of mind about like complexity at the layer one where he's saying like, oh, I used to be like a layer one complexity, complexity minimalist, and now I've become like a little bit more into the idea of complexity inside of the layer one because it reduces complexity at the layer two. And I see this as an example of it. What we are doing with the Ethereum layer one is doing here is enshrining an oracle. It's producing an oracle inside of itself that gets taking on more roles so that less roles can happen at the execution layer.
Yeah, and yeah, a hundred percent. And I think this one is nice because it's not very complex because it already the one already has this information. It's just like on the wrong side of the chain and then we every block the beacon chain already passes information to the execution layer like every time you get a new block, your validator asks your execution engine like is this a valid block? And so they're already talking every block. So it's just like adding one more bit of data and then having the execution layer like save a copy. And then yeah, that has a huge impact in terms of like creating like a more trustless source of information on chain.
Yeah, really, I just like the idea of just like a stronger bridge between this state of the consensus layer and the state of the execution layer. Yeah, beautiful. Okay. There's three minor ones that we're just going to burn through really, really quickly. One, one, one, one, one, five, three transient storage, up codes, five, six, five, six, one copy, memory, copy instruction, and then seven, five, one, six, blob, base, fee, up code. What's going on here? Yeah, maybe to start from the last one, because it's simplest, so blob, base, fee. We have this up code on chain to get the base fee for gas and it's useful.
If you want to do things like imagine an L2 that wants to reimburse people's gas when they submit a fraud proof, they can just say, you know, send them blob, base, fee times, you know, like the gas that they spent. So they can have that all trustless on chain. Now that we have blobs, you want to have an up code to get the blob, base, fee. So pretty straightforward to expose that. Mcopy is just a memory copying up code within the EVM. So if you're very much into like language design or EVM optimization, it gives you a bit more, a bit more options. And then 1153 has two new up codes, T store and T load, which are storage up codes that disappear at the end of a transaction.
So right now, when you save data on Ethereum or read data from Ethereum, it sort of is there forever and you have to read the disk, which is more expensive. So with the transient storage, you just keep those in memory, delete them at the end of the transaction. And so it's cheaper, yeah, cheaper to execute than, therefore, the gas prices lower. Mantle, formerly known as bit down, is the first Dowled Web 3 ecosystem, all built on top of Mantle's first core product, the Mantle Network, a brand new, high performance Ethereum layer 2 built using the OP stack, but uses Eigenlayer's data availability solution instead of the expensive Ethereum layer 1.
Not only does this reduce Mantle Network's gas fees by 80%, but it also reduces gas fee volatility, providing a more stable foundation for Mantle's applications. The Mantle Treasury is one of the biggest Dow owned treasuries, which is seeding an ecosystem of projects from all around the Web 3 space for Mantle. Mantle already has subcommunities from around Web 3 onboarded like game 7 for Web 3 gaming and buy a bit for TVL and liquidity and on-rats. So if you want to build on the Mantle Network, Mantle is offering a grants program that provides milestone-based funding to promising projects that help expand, secure, and decentralize Mantle.
If you want to get started working with the first Dowled layer 2 ecosystem, check out Mantle at Mantle.xyz and follow them on Twitter at 0xMantle. Arbitrum is the leading Ethereum scaling solution that is home to hundreds of decentralized applications. Arbitrum's technology allows you to interact with Ethereum at scale with low fees and faster transactions. Arbitrum has the leading DeFi ecosystem, strong infrastructure options, flourishing NFTs, and is quickly becoming the Web 3 gaming hub. Explore the ecosystem at portal.arbitrum.io. Are you looking to permissionlessly launch your own Arbitrum orbit chain?
Arbitrum orbit allows anyone to utilize Arbitrum's secure scaling technology to build your own orbit chain, giving you access to interoperable, customizable permissions with dedicated throughput. Whether you are a developer, an enterprise, or a user, Arbitrum orbit lets you take your project to new heights. All of these technologies leverage the security and decentralization of Ethereum. Experience Web 3 development the way it was always meant to be. Secure, fast, cheap, and friction-free. Visit Arbitrum.io and get your journey started in one of the largest Ethereum communities. Uniswap is revolutionizing the DeFi space, not just by enabling swaps, but by empowering you to swap smarter, with a comprehensive suite of products for faster, safer, and more informed swapping.
Say goodbye to pop-up wallet extensions. The Uniswap extension is coming soon, and this extension is not a pop-up. It is a sidebar in your browser that persists no matter where you are on the Web. This means you can swap, sign, or send, and receive crypto anytime, anywhere without obstructing your browser window. But that's not all. The Uniswap Web app now features limit orders, so you can buy and sell any token at your price on your terms without having to watch the market. In the best part, limit orders are built on Uniswap X, which means no gas fees. Also new to the Web app is the data and insights pages, with real-time candlestick charts, price data, transaction logs, and detailed pool data all integrated into the Uniswap Web app.
All of these new releases come together to create one platform to help you swap smarter, every time, no matter where you are, on Web, mobile, or on the extension. Click the link in the show notes to sign up for the extension waitlist and download the mobile app. Start swapping smarter with Uniswap. All right. Well, round of applause for all of our EIP finalists that made it into Dankoon. Congratulations for all the EIPs that made it in there. There are some EIPs that did not make it in there, which are the ones that got rejected, which are the ones that didn't make it into the gate that are, like, worthy of note.
So there's a lot to be clear. We have a whole Ethereum magicians strategy with people who proposed them. There's probably, like, 20-30 proposals, and, you know, we can include maybe something like eight. And then, this is, like, the EIP mempool. And so, like, Dankoon is, like, the block that was formed, which is going to be merged into Ethereum. Yes. And so, like, we have, like, seven or eight or nine EIPs transactions that are being merged. Yes. But the rest are still in the mempool. And so the next hard fork is going to be Electra. What are the names for it? What are the two names for Electra again?
I have Prague in the Electra. So, Prague and Electra. Prague and Electra. Pactra is the merged name. Yeah. Pactra is the merged name. Yeah. We're still, kind of, like, finding its identity, right? Like, we don't... Right now, zero EIPs are formally in the market. No, we have a few... Oh, really? Yeah. Okay. So, and maybe, yeah, to zoom out a bit, so over the past couple of years, we've sort of moved to this cadence where we have one big fork and one small fork. So we... We have the merge, which was obviously, like, a huge fork, and then we had withdrawals right after, which is a bit of a smaller one, and now we have four and four four.
And so... Big one. So, for Pactra, we're planning to do a bit of a smaller fork and to start working on the next larger fork in parallel, kind of like we've done with this one. So we've been working on four and four for, like, probably two years at this point. And then in parallel, we were able to ship withdrawals as well. So, Pactra is going to be a smaller fork, but we already have, like, a decent idea of what the bigger forks after that will be. Okay. So, for the execution layer, we'll be up to Osaka at this point. We have this transition to vertical trees, which we've talked about a lot, which changes all of Ethereum's, like, storage layout for the state.
So that's the thing that we're going to do, like, two forks from now, and we're starting to work on right now, but because there's, like, so much work on it, there is, like, and you can't have everybody just working on the exact same pieces of code. We do have some extra bandwidth to do another fork before. And then similarly, on the consensus layer, they're working on effectively, like, full dank sharding and there's a bunch of proposals around how they get there. Again, that's going to take some time. So they also have the bandwidth to do, like, a smaller fork in the meantime. And so this is what Pactra will be.
And it seems, like, maybe the forks after Pactra will actually be separate because it seems like the big thing we're doing on the execution layer of vertical trees is pretty independent from the big thing they're doing on the consensus layer. Maybe we'll end up with an EIP that we add as well that forces both to be together. But we sort of moving to this regime where, like, we have, like, these two big initiatives happening in parallel. And then in the meantime, we're also trying to ship a bunch of, like, smaller, but still useful things. So for Pactra, we actually have four EIPs included already.
So the BLS 12381 precompile, so this is something people have asked for us since, I think, 2017, 2018, which is just using the same curve as the beacon chain as a precompile on the execution layer, enables a bunch of use cases. So we're going to do that. And then that's what that means is like the signing curve. So when we say the message, yeah, and it is from what I understand, there are particular signing curves inside of, like, the enclave in your phone. Is this? No, that's not. Yeah. No, that's not the one. Okay. What BLS is very good for, and the reason we use it on the beacon chain is, like, aggregating a bunch of different signatures.
So any use cases where, like, you have a bunch of different signature and you want to make a proof about, like, all of them and verify all of them, BLS is very efficient for that. And then if you want to verify signatures from validators, basically, you'll be able to do that. This is the dress and drake innovation that brought the minimum ETHs date from 1500 down to 32. Yes. And so now we're just taking that innovation down to the execution layer. And we propose, when we proposed, when it was first proposed in 2018, there was still kind of a new curve. There wasn't great library support for it.
So people were a bit reluctant to, like, add it to the proof of work chain. But now, you know, the entire beacon chain depends on it. Like, if there's a bug in this, you know, Ethereum already depends on it. Yeah. So it makes sense to just add it. So that's the first one we've included. Then the other big change that we're going to do is execution layer, triggerable exits. So having a smart contract initiate, having a smart contract effectively initiate a withdrawal on the beacon chain. And again, this is valuable for a ton of, like, staking pools and whatnot where you'd want, like, any case where you want, like, a non-chain action to trigger a withdrawal, you can imagine like a dial voting on it or, you know, stuff like that.
And I will just say that all categorize that as further strong linkages between the DeFi layer and the consensus layer. Yeah. And that's like the theme. So another thing we're doing is basically removing this sort of delay period. So like right now, when you make a deposit, when you make a deposit to the deposit contract, you still have to wait. I think it's like 2,000 blocks for the deposits to be seen by the beacon chain. And this in proof of work, like before the merger was to avoid any reorgs. So we, you know, we were pretty confident there wouldn't be like a 2,000 block reorg. And so the beacon chain, you know, once it saw 2,000 blocks in the past that your deposit was in, it would credit you.
But today, they're like talking every block. So it's kind of useless to have this 2,000 block. So we're removing that in in Petra as well. So it'll be just like the next block. And then there's another small proof of stake change that's been included 7, 5, 4, 9. I'm actually not too sure what that does. It's around like committee, committee at the stations. So that's on the proof of stake side. So we already have these 4 EIPs that are all quite small, but like, you know, pretty useful that are included. Then we have these two big ones that are sort of, vertical trees is pretty much confirmed on the execution there side.
And I think how to approach day charting is still being like debated on a consensus there side. And, you know, what's the right focus to have there. But we have like these two big things set for like the fork after that, a couple of small things now. And then there's also a bunch of other proposals, which we can get into that we're trying to think through and figure out should be in the next four of the fork after and stuff like that. Okay. So we get to dankoon like now, Electra call it a year, maybe less. Yeah, actually timing, timing on Electra nine months, 12 months. Look, it's really hard to predict these things, but I think you'd do it like Tim.
Give me a day. Give me a day. I think people would like to see us before the end of the year. Okay. It's always nice to fork before DevCon and you feel like you're, you know, you've been your job. Right. And yeah. So we'll see. I mean, it depends on what we end up including in it, but like, the idea is to not spend like several years on that fork. It should be relevant. Of course. Okay. And so then once we get past Petra, then all of the e-theds on Twitter are going to be like the verge is coming, the verge is coming because that's going to be like the next four. So we had, you know, EIP one five five nine, the merge, now we have blobs, which we're getting.
And then after that, we're all going to be stoked for the verge. And for those who didn't listen to our episode with Mike Norder and Domathy, the verge kind of like increases the scalability of the Ethereum layer one by about like three extra modest, but like modest, but like, you know, healthy increase. But really it brings in statelessness, which makes Ethereum just like super prolific, I'll call it like packets going between more devices relevant to Ethereum all over the internet. Yep. Cool. But then there's also three EIPs that I know that are out there that I think are pretty damn meaningful that I want to get to before we wrap up this episode, Tim, inclusionless max effective balance in peer deaths.
Where are these in the EIP member pool? So again, I'll start from the last. So peer deaths is like one of the proposals for how we get the full dank sharding. So this is starting to be prototypes right now. And the idea there is we have these, so these, these blobs give us like temporary storage on Ethereum right now, right, where before the blobs, all the data that stored on Ethereum has to be stored forever, it costs a lot of money to store data forever. The blobs allow you to store data for only a couple of weeks, but every node still has to keep a copy. So it's cheaper than like nodes keeping a copy forever, but it's still every node keeps a copy.
And the idea with full dank sharding is we want to have nodes only store part of the data on the network where you store like a bit of the data yourself. And then what you do is you ping the rest of the network, you ask them for proofs of data, and you do this enough times that you have like a high probabilistic guarantee that like there's no data missing. The same way, you know, like when we use like hash functions, we trust that like a private key only maps to like a city or a public key only maps to a single private key. And you know, the odds that like there could be a double match is like one in like two to the 256 or something.
So the idea with full dank sharding is you basically do that as well where you're saying, like I only have a small part of the data. I've asked everybody else in the network and I've gotten, you know, this many responses. And I know that like given these responses, the odds that the data that any part of data is missing anywhere is, you know, a really tiny probability. And this and if we can do this, then it means you go from like node storing all the data today to nodes all the data today forever to node storing all the data for like a few weeks today to like node storing only a part of the data for only a part of time.
And this is how you can scale the number of blobs without scaling like the validator compute requirements. And so peer dust is like a first proposal or maybe not the first one of the latest proposals that like actually implement this based on the current like validator architecture. And so similarly to how people are starting to work on the verge and prototype that we are starting to see people work on like peer dust. It's a bit earlier in development. So like maybe that's not the final thing that we end up shipping. But it's at least like a very promising step. And I will say, if you look on the ETH research, Danny Ryan has like five ETH research posts that he's like authored.
Every one of them has been like a shift in like the entire Ethereum roadmap, like sort of the like the quick merge post and like the metallic road, the row of centric posts, and then Danny wrote the like, how do we actually like implement this post? So like, Danny has like a really good hit rate with each research post. So yeah, I don't know if like we'll ship peer dust exactly as how it's spec'd, but it seems very promising. Cool. And of course, peer dust is a part of the story of the evolution of blobs. These are like blobs growing up from little blobs to big blobs. Yeah. Yeah. Exactly. And it's not actually sorry, just maybe to clarify this, it's not that the blobs are bigger.
But the total data availability is bigger. Yeah. There's just more blobs. Yeah. There's more of them. Right. So think of it as just like more blobs showing up. Right. Yeah. The blobs are actually getting smaller, but there's many of them. But when you aggregate all of the smaller blobs together, it becomes like big, big blobs. Yeah. Yeah. Many, many, tiny little sharded blobs form big blob. Yeah. These are technical terms. Max effective balance, Max EB. What does this do? So right now on Ethereum, you can only have a 32-EAT validator, which causes like a couple problems. Like, well, I guess maybe I'll start with simple about that is like we can treat all validators the same on the network, right?
Like when we shuffle validators, they all have, we all treat them with like a 32-EAT weight. And so you can like shuffle among. One validator equals one validator. Yeah. Exactly. But then the downside for that is twofold. One is we have these actors on chain that obviously have more than one validators, you know, staking pools, but even like a bunch of people have more than one validators. And every validator needs to send a bunch of messages over the internet. Like, they all have to say like, oh, I tested to this or like I saw this and then send all those messages. And this creates a ton of bandwidth requirements.
And right now I'd say like running a validator, you know, it takes maybe like two terabytes of this space. It takes like a relatively recent computer, you know, I could run one on my MacBook easily. But the biggest bottleneck is probably like bandwidth. Like it takes, you know, from like a couple terabytes to maybe low tens of terabytes of bandwidth per month. And this is like something where, you know, a bunch, in a bunch of places, even if you can buy a MacBook and buy like a two terabyte hard drive, you maybe can't get like that much bandwidth. So the idea with maxyb is if we can tell people like, oh, you have 10 validators, you can put them together and then just sign like one message instead of 10, we can really lower the bandwidth requirement.
And that like makes it easier to run a validator. The other thing that's really nice with maxyb increase is it could potentially allow any amount of each sized validator. So that right now the other disadvantage is you get only stake in 32 eith increments. So say that I have like 50 eith, well, okay, I can stake 32. But then what do I do with my other 18 eith? And this is the sort of thing that like drives people to like liquid staking tokens where it's like, I can get, you know, 50 eiths worth of like rocket pool staking tokens or lightostaking tokens and not have to think about that. So if we could move to a world where like, okay, I have an arbitrary number of eiths that I want to stake.
And then I can actually stake on like a reasonable internet connection because like we've sort of aggregated these validators together. Yeah, that's a really positive thing for Ethereum. So there's a ton of challenges in doing that. And this is why it's like not a no brainer to include it in the next work. Like if it was easy, we probably would have done it already. But it is being considered and we're trying to think about like, okay, harder like simplifications we can do in the spec that like maybe we get like a first version of it out in the next fork and like make it more complicated and provide more functionality into fork after that.
So that's a big area of just like research and development right now. Right. And it also allows solo-stakers to compound their rewards. So 32 can immediately turn into 32 point like one, 32 point, 32 point, yeah, that's a great point. Yeah. Yeah. If you only have 32, yeah, it would compound. Right. And yeah. And so like rather, so like right now when you have a 32 eith, you get your eith rewards. But they, they don't. Yeah. Yeah. Exactly. Exactly. Yeah. Exactly. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Okay. The cool thing about max, max effective balance like there's also minimum effective balance, minimum effective balance staying at 32 maximum effective balance is going up to 2000 and 48.
Yeah. I think that's correct. Inspector inspector is 2048. Yeah. Yeah. Cool. And then last one, inclusion list. This is a big one. Inclusion list. Where is this in the mempool? It's just about the trade off of like complexity versus the value. So like, again, it's like if we could have, you know, perfectly working inclusion list tomorrow, and it was like a one line change, obviously, we would have done it. Um, I think the, the biggest questions here are like, if you do something that's in protocol, can people circumvent it? Um, and what is it like? Can we just define? Okay. Yes. Yes. Yeah. So inclusion list is specifying a set of transactions that you as the current proposer believe should be included either in your current block or like the next block.
Um, and, and then, you know, the, there's many flavors of this, but you could imagine the most extreme flavor is something like somebody else specifies an inclusion list for you, like the previous proposer. And then your block isn't valid if it doesn't contain those transactions. So it's like the previous validators like forcing you to include those transactions, assuming, you know, their gas gas prices high enough. And so the goal with this is just to improve censorship resistance, because you can imagine a validator just like seeing transactions that are censored in the mempool and like wanting to force those into the network.
And so there's like two problems that inclusion list can address. One is validator censorship. Like do we want say that you have, you know, a nonsense or invalidator a and then the after afterwards the validator be a censoring, do we want a to be able to like force beat not the censor. And this is probably the part that adds the most complexity like having like the validity of a block dependent on an inclusion list. But then the other, the other use case is a validator forcing an external block builder to include some transactions. So right now, the way mvboost works and the whole like PBS infrastructure works is a validator has to choose either to build their block themselves or to delegate 100% of the block's contents to like an external builder.
And this means that if the builder is censoring, they sort of give up on censorship resistance, the sort of forced to choose between censorship resistance and like a potentially higher profit. And one thing that that may have boosted us today to deal with this is they have like this min bid flag. So if you're a validator, you can say, unless an external builder gives me this much, I'm going to build my block locally. So you're sort of saying like, I'll be censorship resistant unless it's like a 10 of mv right now, then I don't really care as much just give me the most paying block, which is still like a valid approach, because you know most of the time there's not huge spikes of mv so it's you can like get censor transactions in them.
But a version of inclusion list that you could imagine is one where we just force the builder to give you a block that includes your transactions on your inclusion list somewhere in the block. So you're saying, you know, most of the enemies at the top of the block, like let's find you know, build me a super profitable block, but make sure that like the last four transactions of this block are these or that somewhere in the block, there's these four transactions. And otherwise I'll just pick my block locally. So I think this is the big challenge with inclusionness is like, do we want a sort of like validator to validator setup where they're each like forcing people to do stuff or do we want like a validator to build their setup where it's really about the block I'm going to propose.
The validator to build their setup is much simpler to implement. But then the validator to validator setup one, you know gives us like sort of full censorship resistance at the validator set. And then it also improves on things like base roll ups, so a lot of like the pre confirmation. So again, this is like a trade off between we could do like this more complex more powerful version of it or maybe just like a small quick fix now and eventually, you know, expand on it. And this is what people are debating just shooting from my hip here. I do really like the idea of very strong censorship resistance that also enables base roll ups.
So it's a way that like synergy and serendipity between these two properties. Is this like a hard work after Petra kind of timeline or is that kind of unknown. So the simplest version you don't even need a hard for you could do the simplest version of this just an mev boost right where you just say. And then again, it's like, you know, there's you rely on mev boost for trust here, but like we sort of do already for a lot of other stuff. I also like full validator set censorship, but I also like shipping things. If I was like the dictator, I would probably ship the mev boost change. And then the thing as well, we get out of that is you can you can get like a usage data, right?
Like maybe this is a terrible idea. Like there's some flaw in it that we haven't thought about for whatever reason, but like if it's only a change in mev boost. Okay, whatever we can fix it, we can revert it and whatnot, but we didn't like enshrined that in a protocol. So yeah, I'm sort of biased if like if there's ways we can test things quicker in like a more controlled environment, I'm all for that. But I agree that like long term having something that's like more robust at the protocol layer is is extremely valuable. Sure. Okay, those are all like my big IPs that I want to talk about that I know are in the men pool.
Are there any other like valuable EIPs that we haven't brought up that are worth elevating? Yeah, let me check the list real quick. Okay, so we have this thread on if your magicians called try slash lecture network upgrade meta thread, which I should upgrade the extra now that tracks this. So basically you can find a whole list of everything that's being proposed there. And this is what we're discussing sort of every week on all core devs at this point. But aside from all the stuff we talked about, maybe one one big thing that's also being discussed is EIP4444 or for fours, which is about stopping to serve historical data from Ethereum.
You're the peer network for all the pre merge stuff. So the idea is like right now all the nodes have to serve data about all the way from Genesis. And we'd like to move this to like other data providers so that when you when you sort of sink in Ethereum node, you can know like for sure what's the latest valid chain. And then you could import your historical data from something else like imagine you just torrent it, for example, and then verify that that history actually matches up to the head of the chain. So this is something people have been working on for a while and yeah, what a key is this a snapshot versus snapshot in Ethereum.
Effectively like you can think of it as like last snapshot in history. And the thing that's that's important is like when you sink the chain and you think like the current head, you know, you want to make sure that this is secure and so the nodes like do this already. But then when they backfill the history, they're always checking that like this history actually ends up at this current head. So it doesn't really matter if you're confident in like your current head, it doesn't really matter where you get the history from because you can always verify that it's correct. And so right now we're kind of using Ethereum as like a weird sort of torrent seating network for this.
When it's just like not the most efficient thing like literal torrent networks are more efficient or you could imagine like going to internet archive and just downloading you know the first million blocks or you know the first 10 million blocks or something. So we're working on just like having a good format for exporting that data clients importing that data having a couple of places that like serve this data. So they just like again removes like the burden in terms of bandwidth on the peer to peer network. And so that's a big piece of work. So like a ton of upgrades to the EVM people are still considering that's a whole other like bucket of proposals.
There's a bunch of proposals around account abstraction and EOA improvements and what not it's another big one. And then the other one the other like bucket I would say is around just like the format of transactions. So how we want to encode stuff. But now we're getting like really in the weeds. And aside from that is a bunch of other like ad hoc EIPs but I'd say like history expiry EOF account abstraction and then sort of a long list of miscellaneous EIPs is what we're thinking through. And if you score that ETH magicians post I sort of have a little diagram showing like all the different EIPs proposed where they fall already like CL EL a mix and we're slowly working our way through that list.
Well Tim I feel very informed about the horizons of Ethereum and what's beyond them. So thank you so much for coming on the show and walking us through all these EIPs. Yeah thanks for having me this was great. The link that you just mentioned Tim I'll get that from you and I will post that into the show notes. And so if you're listening to on the podcast or on the YouTube you just go to the show notes and find that link. Tim thank you so much my man. Yeah thanks for having me. Banklessation you know the deal crypto is risky defi is risky EIPs and hard forks they're also risky you can lose what you put in but we are head west.
This is a frontier it's not for everyone but we are glad you are with us on the bank this journey. Thanks a lot. you