Tim Beiko and Danny Ryan are two of Ethereum’s lead coordinators, and work at the Ethereum Foundation to shepherd the many parts of Ethereum into the future.
How are they feeling on the other side of the Merge? What does this mean for Ethereum?
Few (if anyone) on the planet are more qualified to discuss the Ethereum Proof-of-Stake than these two, and we use this episode to reflect on the magnitude of the event and look forward to the future of the network.
------ Swell | Liquid Staking for the People https://bankless.cc/swelldiscord
------ SUBSCRIBE TO NEWSLETTER: https://newsletter.banklesshq.com/ ️ SUBSCRIBE TO PODCAST: http://podcast.banklesshq.com/
------ BANKLESS SPONSOR TOOLS:
LENS | WEB3 SOCIAL PROTOCOL https://bankless.cc/Lens
ROCKET POOL | ETH STAKING https://bankless.cc/RocketPool
️ ARBITRUM | SCALING ETHEREUM https://bankless.cc/Arbitrum
BRAVE | THE BROWSER NATIVE WALLET https://bankless.cc/Brave
JUNO | BRIDGE FIAT TO LAYER 2 https://bankless.cc/Juno
️ ZKSYNC | THE LAYER 2 SCALING ENDGAME https://bankless.cc/zkSync
------ Resources:
Tim Beiko https://twitter.com/TimBeiko
Danny Ryan https://twitter.com/dannyryan
------- Not financial or tax advice. This newsletter is strictly educational and is not investment advice or a solicitation to buy or sell any assets or to make any financial decisions. This newsletter is not tax advice. Talk to your accountant. Do your own research.
No summary for this episode yet.
Hey, Bankless Nation. Welcome to another State of the Nation episode where we talk about something big that's just happened. Get into the details of it. And David, what could be bigger than the Ethereum merge? Five days ago, proof of work was abandoned. Proof of stake executed, implemented. We merged the proof of work chain and the proof of stake chain, and we're here to talk about it. This is kind of a post-game show, I think. Who do we have on? What are we covering today? Of course, none other than Danny Ryan and Tim Baco, the two lead coordinators of this whole entire merge effort who have been just shepherding the many parts of Ethereum to get this done.
And there are many parts of Ethereum, so this coordination effort was no small feat. And so these people have been, Danny and Tim, have been at the spearhead of this whole coordination effort. And so we're just going to talk about what are they feeling right now post-merge? Also, what are they going to do next when they have been thinking merge, proof of stake, beacon chain for the last over a year now? What's on the horizon? And also, what drink did they drink after they merged? So all of these super important questions and more when we finally get to Tim and Danny. Yeah, these are the important questions, I think, David.
And in addition to that, I think we want to ask what the future of Ethereum is. So this is a major milestone. And now it's in the rearview mirror. Where do we go next is the question. And I actually think one of those areas we go next is we need to work on decentralizing our staking providers, in particular our staking pools. I wanted to give a shout out to our friends and sponsors at Swell Network. They are a staking application, similar in some respects to RocketPool and Lido, with some differences, though, David. What is a Swell network and what can folks do if they're interested in decentralizing staking pools with this new protocol?
Yeah, Swell has joined the ranks of Lido and RocketPool to be a decentralized staking as a service provider slash DAO. It's like Lido in that it's got a permissioned validator set that the DAO approves or bumps out. But it's also like Rocketpool in that it has a permissionless validator set that you can join if you put up a bond. So trying to do the best of both worlds. And the Swell Network is just getting started. So if you want to be on the ground floor of something, you can go and click a link in the Discord. And as a disclaimer, you can see that Ryan and I are also angel investors. So they both sponsored this message.
And also Ryan and I are angel investors into Swap. Make sure you check out that Discord, an opportunity to get on the ground floor of something new. So David, got to ask you the question, but I think it's pretty obvious what the state of the nation is today. What is the state of the nation though, David? No, Ryan, the state of the nation is merged. Importantly, past tense. The state of the nation is also proof of stake, as in much of the DeFi economy was previously proof of work and is now proof of stake. So Ryan, the state of the nation is merged with the future, merged with proof of stake, overall just merged in general.
Yeah, there we go. How'd you like that one? I love it. It's music to my ears. And we are going to be right back with two of the individuals instrumental in making this happen, Tim Bako and Danny Ryan. But before we do, we want to thank the sponsors that made this episode possible. Lens Protocol is an open source tech stack for building decentralized social media applications. It is the new era for social media. We all have toxic relationships with our Web2 apps. We want to break up with them, but we can't. These applications own our digital lives and all the relationships that we've made. We need to break through to a new paradigm of social networking applications that we control rather than them controlling us.
Lens isn't a social media app. It's a protocol to let a thousand Web3 social apps bloom. Lens is a permissionless and transparent social graph that is owned by the user. In crypto, we say not your keys, not your crypto. And on Lens, we say not your keys, not your profile. With Lens, your followers go with you to whatever social media application you want to use. And instead of being trapped by an algorithm chosen by that app, Lens lets you choose the way you want to experience your social media. Lens is the last social media handle that you'll ever need to create. So in order to get started, there is a secret code word in the show notes.
Enter that code word in the Google form linked and you'll be well on your way to entering the world of web-free social. Rocketpool is your decentralized Ethereum staking protocol. You can stake your ETH in Rocketpool and get our ETH in return, allowing you to stake your ETH and use it in DeFi at the same time. You can get 4% on your ETH by staking it with Rocketpool, but you can get even more by running a node. Rocketpool is the only staking provider that allows anyone to permissionlessly join their network of validating Ethereum nodes. Setting up your Rocketpool node is easier than running a node solo, and you only need 16 ETH to get started.
You get an extra 15% staking commission on the pooled ETH that uses your node to stake. You also get RPL token rewards on top. So if you're bullish e-staking, you can boost your yield by adding your node to the decentralized RocketPool network, which currently has over 1,000 independent node operators. It's yield farming, but with Ethereum nodes. You can get started at RocketPool.net, and you can also join the RocketPool community in their Discord. You can find me hanging out there sometimes in the chat, so I'll see you there. Arbitrum is an Ethereum Layer 2 scaling solution that is going to completely change how we use DeFi and NFTs.
Some of the coolest new NFT collections have chosen Arbitrum as their home, while DeFi protocols continue to see increased liquidity and usage. You can now bridge straight into Arbitrum for more than 10 different exchanges, including Binance, FTX, Huobi, and Crypto.com. Once on Arbitrum, you'll enjoy fast transactions with cheap fees, allowing you to explore new frontiers of the crypto universe. New to Arbitrum, for a limited time, you can get Arbitrum NFTs designed by the famous artists Ratwell and Sugoi for joining the Arbitrum Odyssey. The Odyssey is an eight-week-long event where you can play on-chain activities and receive a free NFT as a reward.
Find out more by visiting the Discord at discord.gg slash Arbitrum. You can also bridge your assets to Arbitrum at bridge.arbitrum.io and access all of Arbitrum's apps at portal.arbitrum.one in order to experience DeFi and NFTs the way it was always meant to be, fast, cheap, secure, and friction-free. Bankless Nation, we are excited to introduce you yet again to Tim Bako and Danny Ryan. These are two of Ethereum's lead coordinators. They've helped shepherd the Ethereum Foundation and Ethereum itself into the future, including implementing most recently the Ethereum Merge. Danny, Tim, welcome to Bankless.
How are you guys feeling? Pretty good. Yeah, thanks for having us. Pretty good, honestly. I had an inclination. Huge relief. Very exciting. It's a culmination of quite a bit of work from quite a bit of people. So, and it, it went well, I would say. I think going, going well might be sort of a, an understatement in some ways, because this thing was like smooth as butter. And I'm wondering if that was kind of like what you anticipated. I'm sure it was what you hoped for. That was on the optimistic side of things. But did you think it would go as well as it seemed to go? Danny first. I thought it could go as well as it went.
I thought there was a non-trivial chance that a client of moderate use would have had more substantial error where there's a bit of scrambling, maybe a quick release, or maybe telling 10% of the network you have to restart your node or something like that. But the fact that I think we saw a 4% drop, I think we saw some intermittent node failures on one client that a few people did have to restart their nodes. But just like, it was very, it was, it was a dream. Yeah. Tim, how'd you feel about this? Was it a dream? Yeah, it was like, I, you know, historically, when we have an upgrade, I have to do something in the next couple hours, whether that's reaching out to some operator or client team, like, I didn't expect the network to go down.
I was incredibly confident we'd finalize and all of that, but I expected that somebody somewhere would have forgotten something quite important. And we'd have to reach out to them and coordinate. And that didn't happen, which was kind of wild. Like that he said, there were some minor issues, but even that 4% drop, I think in a matter of hours, it was back and potentially less than that. So yeah, I, I don't think it could have gone much better. It went pretty much better than like most of even the shadow forks and whatnot that we did. So I think we've had like one or two shadow forks go similarly as well.
Yeah. You know, and one's later in the process, but just like we've had plenty of times where you're like, oh, 20% of the network's off. The network's fine as a whole, but like we need to go triage an issue, but we didn't have that. Yeah. So one of my questions was going to be, what did you think you would be doing immediately post-merge versus what you were actually doing? So Tim, it sounds like you were about to be picking up the phone, calling a particular client team, perhaps, or messaging them and saying, hey, this thing's going wrong. We have to troubleshoot this. But instead, you were just watching the merge and nothing going wrong, I guess.
How long did that take to set in before you realized, wait, we had a perfect merge? How long until... Were you in disbelief? What was going through your head at the time? So we kind of knew as soon as we finalized, and even before we finalized. So there were some people from the research team who were looking at the attestations kind of piling up on the epoch. So before it had officially finalized, we sort of knew we were good. That was like a pretty big relief. Yeah. Each block, like, so you see the first block and then there's slots, right? Slots are kind of the ticking of time every 12 seconds.
You can have a block or you can not have a block at each slot. And so we had a block and then we had a block and then we had a block and then we had a block. And like every slot that took by that we had a block and we had no missed slot, it was an indicator that like the network's online the network's very healthy and like this thing's going through so like iteratively through the course of like 20 minutes as we're waiting for finality i think we're just more and more like okay it's working it's still working and it's still working i think we missed maybe one slot maybe two slots between the beginning of the merge and finality um you know and it was only like on the third epoch or something which is normal if if you have 95% to 99% online.
It was just kind of shocking. So we're talking within minutes, you guys realized that the merger was going to be perfect, or not perfect, but as good as one could hope? Iteratively. Iterative knowledge until that finality point. But it was looking pretty good. So where were you two? I know, Danny, you were at the EF office in Colorado because I saw a picture of you there. Tim, oh, you were also there, Tim. You guys were right next to each other, weren't you? Yes, I flew into Colorado for this. Yep. It turns out it's hard to plan a party around a total difficulty. Yeah, yeah, I can relate. We're like, is this going to be a breakfast party?
Maybe a luncheon? And then at some point we're like, it's going to, okay, we can have dinner and it's going to be at 8 p.m. And it ended up at 1230 a.m. So we're just like, we ended up, it's kind of this funny time in between everyone gathering and like waiting. It's like a lot of like, so it's coming. Everyone's like refreshing. There was a wager pool on when it precisely was going to happen. People were playing Super Nintendo, you know. I had like, my iPhone had 20 different Bordell tabs open. Like, you know how you can go in this like safari view of all your tabs? I would just scroll up and it would just be like Bordells everywhere.
yeah so that's what I did all day I know Vitalik said he was um he was surprised that you know kind of the the merch date didn't oscillate as much oh my god people expected were you guys surprised by this yeah I mean we did this better than a proof of work hard fork like the timing the the the timing when we hit it was like closer than we usually get I mean it was what it was just a few hours off of the total predicted time. Right. Yeah, we were aiming for 12 UTC, and I think we got six UTC. So we got like six hours from what we made, what we aimed. Yeah, that was as good as it could have gone as well.
Tim, you mentioned Vitalik. During this interim between 8 p.m. and like 12.30 when we were waiting, you made a beverage, right? Oh, yes, that's what I did. Yes, I spent all evening drinking Vitalix. Because I wanted, you know, by 8pm, I wanted to drink, but I don't want to like be drunk if the merge was happening at 2am. I didn't want to fall asleep either. So like the Vitalix was actually perfect for this because you had a little bit of red wine, some caffeinated green tea. So it kept me awake and going all the way until the merge hit. And what's the Vitalix ratio? Is that 85% green tea and 15%?
Am I remembering that correctly? correct you have to get that ratio correct or else it's just yeah 84 16 just doesn't work okay yeah so i have to ask how how was it was it it was all right yeah i feel like it tastes a bit like cranberry juice um yeah that's like the closest i would i would put it um yeah and so what what was the atmosphere like when when it happened of course i i think a lot of people listening to Bankless right now, maybe they've seen clips from the live stream the moment the merge happened. Maybe they were even actually up and present for it. What was the feeling? I guess you guys were in the Ethereum office.
Was there like shouts? Was there high fives? Like how excited were people? Or was it pretty chill? Like, you know, it's a dev group and like just silent nodding and big smiles. Like what was the reaction to all of this? Yeah, yeah. Exciting. Everyone yelled pandas because we all saw pandas on our logs. And then a bit of anxiety as it approached finality. I wanted to pop champagne after the pandas had happened and everyone was like, no, you can't pop champagne until finality. But once, you know, call it 18 minutes in, 15 minutes in, a finality happened. Champagne popped, lots of hugs, lots of excitement and cheering.
It was an emotional release for a lot of us. I think a lot of people in that room have been working on or at least following this thing for many years, somewhere between two and five years. And so to see it come together, definitely emotional, emotional experience. I sit up till 4am and I usually go to bed at like 930. So that speaks worlds towards the importance. Tim, do you have anything to add? No, yeah, no, the atmosphere was great. And I mean, the fact also that it went so well, I was sort of expecting people to kind of be partying, but things not to be perfect. So I would be like, you know, going back to work on my computer somewhere, like reaching out to that staking pool or, you know, that forgot to update or something.
Uh, no. So like I got to eat cake and like drink the champagne with everyone, which was nice. Um, and it was just wild. Like, it was kind of surreal that like, you know, it just happened on mainnet. Like you kind of see it happen so many times on shadow forks and whatnot. And the graphs all look the same, right. It's like, it's all, it's all this, it's literally the same thing that happens over and over. But the thing like, Oh man, like this is mainnet, right? Like it, that was, that was pretty wild to see. Do you guys have any, like any family or friends? like your in real life friends that that you could share this victory with like so so for me right it's um a whole bunch of my internet friends my ethereum friends and they're just as excited as as i was the merch happened and like get to share that victory with them obviously but then i go to you know real life and it's like no it's like that meme and you're the guy in the corner of the party nobody knows the merge just happened right as i walked with my wife the next day i said that up to her i said i feel like the guy i mean because how big was this danny i mean we're joking before we uh we started recording that um the merge may have single-handedly in one night reduced global electricity consumption by 0.
2 percent like that happened yeah it's like a big deal it's like you know norway or or chile or something yeah yeah it actually was this moment where at least because i you know i think my my parents and others they like kind of know what i do it's not very clear than what i do um but they're definitely seeing some of like the the energy uh narrative over the past couple years as nfts became more in the mainstream i think that became fodder for some of the mainstream media uh like my dad always says like bill maher like it's who talk show person uh just shits on on crypto because of the energy it's all about the energy my dad's like so this is like this is a big deal this is like a game changer right because because bill maher can't shit on this anymore yeah i think i think i think so i think so dad's right though yeah yeah yeah no no so it's it is cool like they they had some context i think they know i very much believe in this stuff but also like uh had seen some of the mainstream media criticism so that it it it came together to a certain extent my sister actually was in there she joined um the party which was cool i think she just got to see a one she thought it was going to happen at eight and then ended up staying until 12 30 in the morning um on a weeknight but she got to see just some of the energy and see like how meaningful it is to this little sub community um so it was cool to get a glimpse there too tim how about you did you get any text from family, friends, you know, celebrating this with you?
Or they just have no idea like what you do? No, my friends definitely follow it. Like they're not like into crypto, you know, they might hold ETH or whatever, but they're not like, you know, LPA on Uniswap or stuff like that. So they all thought it was pretty cool. My dad texted me, he was like, well, if this went well, why did the price go down? Yeah, so also an ETH holder, but not far beyond that. um yeah and i think you know have this i think it was kind of nice how a lot of the mainstream media actually covered the merge like i think it is one of the cases where things at least i don't read everything but like the stuff i saw was like pretty fair um so i felt like i don't know people around me who like sort of follow crypto you know they read like new york times or whatever articles about crypto or like bloomberg um it seemed like they had like a decent picture of what was about to happen and the impact um and so yeah that i think that that made it easier like i didn't have to go and explain all of this to them they were like okay this is switching off um seems good uh seems risky but if it works you know it would be it would be a nice thing um yeah that was quite neat yeah i definitely every time i spoke with someone from mainstream media leading up uh they They clearly, playing into the risky part, they were clearly looking for people to talk about how risky it was and how crazy it was.
And they were always trying to get me to validate, is this actually changing the motor of a plane? I'm like, yeah, it's going to be fine. So how did it feel to remove 0.2% of global energy consumption? Because I feel like if I was one of you two, I'd be like, nice, I did that. I helped. Very important. I think to contextualize it though, if the ETH price 10x, it wouldn't be 0.2%, right? It'd be like 2%, the new equilibrium. So it's not just removing an absolute number today, but removing this insidious growth that was coupled with the platform that we want to reach massive global adoption, right?
So it's not even just what it does for today, but what it does in the event that Ethereum becomes what we want it to be, what it does for that future. And that felt pretty good. I will caveat this a little bit. So we remove, it's like this energy still exists in the world, but it's like the world, Ethereum can exist in the world without requiring that energy. So I kind of feel good. I feel the good that we can keep doing our thing here and not have like a disproportionate impact. But yeah, I also, I'm always skeptical when people like push that too far. And to a certain extent, I mean, like, obviously you can use free energy that maybe wasn't being used in some mining, but you're also putting demand on it, which is either going to increase the supply or increase the price for others that are trying to get back, you know, act in that supply.
And I think the growth rate, like you said, is like the part for me that like is the hardest to convey. Like there's all these articles, you know, that I was saying, like Ethereum is reduces its energy impact by 99%, 99.5, 99.9. And it's almost like those articles are understating it because like you take the point today and the consumption today, and sure you can like get a number, even though there's very wide error bars, but it's like 10 years from now, that number would maybe be 10X bigger. And then, you know, even though looking at the energy impact of proof stake is kind of a weird thing to do.
We also benefit from growth in the opposite direction. If computers get better, if chips get better, then Ethereum takes less energy to run because it just uses computers now. So I think that is a really neat thing. And this platform that we rely upon the price of the asset for security, we no longer have a linear relationship between that thing that we rely on and energy consumption of a platform like plain and simple it's very very very important um i just don't think that over like a 10-year time horizon that there's going to be much social and political appetite for something that has that type of relationship so we can be very much more excited about you know price increases without all of the baggage that was kind of lingering right the sort of the narrative baggage but also the the real baggage of um inefficient energy use yeah yeah i mean i also just as we saw with one of the first applications to be adopted outside of like our immediate community nfts and art use cases like you know even it's very the farther you are from like the understanding of like the how these mechanisms work the more you're just like why the hell are we bringing all this energy this makes no sense you know it's just it was not going to adoption i don't think could be adopted uh mass adoption of that paradigm and as you said danny like as if ether 10x in price that would actually have been two percent uh of energy global energy uh consumption you know in theory um but then if we if we eliminated it then it would have really just been another nine on the other side of the decimal in like how much energy we reduced so like what does it really mean to the average person to reduce energy by 99.
95 versus 99.995 like it's still the same level of like impressiveness and kind of like loses a little bit of the point And I think, you know, bankless listeners in the broader Ethereum community, we all kind of know like why we did the merge. You know, it's a more secure consensus mechanism. We're reducing energy consumption. So like we know what it means for Ethereum at a pretty concrete level. But I want to ask you guys what you think that it means for Ethereum in a more broad sense. Like what else does it mean for Ethereum? I remember Vitalik on the livestream, he said, these are the first steps towards Ethereum becoming a very mature system.
So just want to peer into your guys' heads. Like, what do you think he meant by that? And what does the current state of Ethereum mean inside of its own trajectory and aspirations to fill its own shoes? Tim, I'll start with you. I'll leave the technical roadmap to Danny's stuff because I think he has some interesting perspective on it. But I think one thing that the merge, beyond moving to proof of stake and reducing the energy impact, I think one thing that I am really excited about is it shows we can ship complicated things. I've grown much more excited about this over the past two, three years.
It felt like Ethereum launching was incredibly ambitious. And then we had a couple of years where we weren't shipping that much on-chain. It was a ton happening within client teams, a ton of research happening, but I was kind of concerned, will we be able to ship complex things or are we just going to make these small incremental changes to Ethereum? And then we launched the beacon chain, which was wild, but we did that separate from the applications. And then 1559, I think was also kind of neat because it showed it was the first time since we launched Ethereum that we changed the format of the network and not just adding new things in the EVM or whatnot, but with these like flexible blocks and stuff like that, it was kind of neat.
And then the merge is just like 10x, you know, 100x bigger than that. But it's like, we're shipping this insanely complicated transition across all of these client teams, which all have to work together smoothly behind the scenes with no downtime. And we did it. And we did it, you know, obviously it took a while, but like, when you think that within like 13 months we went from shipping like EIP-1559 to the merge. It's not like that long, you know, in hindsight. So I'm really excited. It shows like we can ship like really complicated things engineering-wise, both from like a coordination point of view, from obviously like the implementation point of view, but also like from getting the community to run this.
Not that we shouldn't like try to minimize complexity across all of those things, but you If we want to get through this entire Vitalik roadmap diagram, there will be more complicated things to ship. And I'm much more optimistic than I was, say, like three years ago, that we can ship all of that. And the merge was like a huge bump on that front. To be fair, you could argue we've been attempting to ship the merge since 2018 with the beacon chain, if you actually encompass that complexity into this, right? So like, which, but the fact that for the past year, that the complexity of the merge has not been riding the beacon chain for all these execution layer clients.
It's just been like the plugging together. You know, I think that the modularization here is also gives us very much gains in terms of scaling out teams, resources and software. yeah and tim you touched on this subject but ethereum previously previously it's actually gonna be my question uh has this branding of like oh ethereum doesn't ship it's full of promises it's got a bunch of ideas uh but it doesn't actually follow through on them how much like i mean i'm talking to the person that is directly antagonist to this to this idea but just like do think that that take has any weight left to it at all no i think it's wrong like and i've tweeted about this before it emerged but i think you know for what ethereum tries to do i think even from the beginning like since genesis the execution has probably been like top tier and that like yes it was a mess but like every every company that does something complicated is a mess or like project or whatnot like it's not this is not like an ethereum thing like it's hard to do complicated things And I think the fact that it all happens in the open makes it look much worse for Ethereum.
Like you don't see what SpaceX looks like, but imagine what it must feel like to do something like what they're doing. So I think that is a big part of it. It looks worse because it's all in the open. And I think the other reason why it looks comparatively worse is there's a lot of shortcuts you can take that don't show in the short term. So you can have all these other competitors that come and don't do the hard stuff and look like they're making more progress. But imagine if you had something like someone doing that to SpaceX, the rocket would just blow up. And actually, you do kind of see that.
There was Tesla and then there's all these fake self-driving car companies who stacked. And they all had all these demos and whatnot. And none of them actually had a self-driving car um and i think you kind of get a similar effect where like it's easy to like look like you're doing as good as ethereum or like you're 90 of it but then it's like the equivalent of this self-driving car that was just rolling down the hill um so i think we look worse than like we are and i think even and i do think we we have improved significantly in like yeah the past like two three years it's just been wild the amount of stuff that's shipped um yeah you also you say people might say oh it's just ideas it's not just ideas we certainly but we certainly have more ideas than we are able to ship i mean that's just the nature of like the the the vibrant research community and the ethereum ecosystem is like there's new ideas every day there's new ways to think about how to solve these problems every day and like what shipping is is actually distilling those into simple you know what is what are the requisite ideas to get where you need to go how how do we simplify them as most as possible and then how do we not break this you know hundreds of billion dollar network in doing so and so sure like if you're just watching the ideas you're going to be like they're never this is never going to happen they're going to have but that that's the point of ideas it's a point of research right it's also kind of wade through it all and it's a it's a really good sign if all the ideas that most of them come from like people working on ethereum because it kind of shows you that like this is where a lot of the energy is going uh even though it looks worse from the outside because you see all these ideas that actually don't i mean the ethereum the theory community is a shocking intellectual powerhouse um it it we call it um kind of the intellectual gravity well of ethereum is strong and it just continues to suck people into it um academics engineers random people on the internet uh it's the force is coming for you can you can you guys talk about that for for a minute so like like who actually made this happen?
How did it happen? So I think, you know, so many people's experience with software projects, if they're kind of in the field, is there's some top-down hierarchy structure, right? And we have like agile processes, of course, but, you know, there's a budget and then there's, you know, a program and there's a set of teams, even complicated projects like run like this. but it's all very well orchestrated and coordinated and kind of top down. But I don't get the impression that this was how the merge shipped at all and how clients are developed in Ethereum at all. I get the impression that it's maybe completely different.
I don't know if there's an analog somewhere else in the open source world, something like Linux, for example. But Danny, could you talk about that? because I think people are kind of wondering, the core devs, who are these people? Is it hundreds of them? Maybe somewhere? Like, how are they all coordinated? How does the sausage actually get made here? It's hard to say. Even being in the middle of it. You know, and there are maybe some analogs. Like, maybe some of the, like, engineering standards bodies that have mailing lists and, and like form new standards that ultimately get adopted by the internet, like SSL and that kind of stuff.
Or maybe Linux, maybe Linux has some parallels. They have a, there's a foundation, they kind of all ship the kernel. There's many different companies that work on it, but ultimately there's Linus, who's like the BDFL, the benevolent dictator for life, who gets to like decide what goes in and uses that for their Linux foundation's political agenda to, you know, maybe if you go work on the plumbing, put your feature in the kernel um that kind of stuff so we don't there's some parallels to this stuff but i honestly do think it's like very um unique you know in in this context in that there are like we were talking about ideas it starts with ideas starts with research starts with um people thinking about the protocol thinking about its needs thinking about the kind of the design trade-offs those becoming uh posts sometimes becoming academic papers sometimes becoming prototypes and ultimately becoming proposed specifications right and there's a number of places where people work on ethereum specifications just because something is a specification doesn't mean it's ever going to mainnet there are probably more specifications that will never make a domain net than than are um maybe maybe tim has the answer to that one um and then ultimately there are a bunch of people that build software that runs on the Ethereum network.
These are often what we call core devs. Who is a core dev? I don't know. I think Amin might be able to answer that one for you. But there's the protocol and the abstract, and then there's people that implement the protocol. And we have tons, we have many, many implementations of that. There's two layers now, the consensus layer and the execution layer. There's something like five teams on each side. Maybe not all of them are production ready, but maybe five, four. And these people kind of through asynchronous processes around the EIP repo and other specification repos, through the Magicians Forum, and also through some synchronous processes on our all-core devs call and consensus layer call, hash out kind of the importance of, one, they kind of technically vet a lot of these specifications, and then try to figure out an optimal configuration of how to bring them to main net, balancing what are the most critical things.
Often security bubbles up as like a very, very, very critical thing. Without security, this thing doesn't exist. And then there's other things like nice to have features. Like those might get less prioritized, but sometimes they do make it into this process. And so it's this kind of like amorphous process amongst specification writers, researchers, prototypers, and these client developers to figure out how to bundle specifications into network upgrades, often called forks, and ship it. The process of shipping it is also very complicated. The amount of testing, security analysis, and all that goes into that is pretty massive too and happens also in a very distributed fashion.
But Danny, what I'm curious about is, you know, so you're a lead organizer here and you're kind of also like, I don't entirely know how it organizes. It's like somewhat, it's like some kind of chaotic organization type structure. Like so so and I would contrast that, you know, Tim was talking about we've entered a new era for Ethereum. This is the Ethereum can ship era. We've just proved it. We have three recent proof points. Ethereum didn't always have that reputation. I hearken back to like 2018, 2019, when it felt like the project was almost like stalling out, even though you might say, Danny, like research stuff was going on behind the scenes.
I remember a very famous part of this maybe was the bear market, but part of it was maybe some truth. A famous tweet from Fred Wilson, Uniscore Ventures, and he was like, Ethereum just doesn't know how to execute. They have the lead and they are falling. Someone call Silicon Valley. Right. This is basically what he said, because this is not how you build startups in Silicon Valley. How do you build startups? Well, you have startup organization. You ship fast, you break things, of course. We'll adopt that in the startup mantra, but you have to have governance. You have to have accountability. You have to have some structure.
And the idea was that Ethereum would just fall prey to the tyranny of structurelessness, and it would never actually get anything done why because silicon valley knows how to build software we did facebook we did google and that who are these ethereum people trying to like make this thing happen with like what volunteers around the internet like how does this even happen can you it's funny because the internet actually is much more built like that obviously you know rather than these companies that were built on top of it maybe that's the parallel here is that like ethereum's not trying to be a company ethereum's trying to be the internet it's trying to be a foundation of the internet like what motivates them why did they get involved but this is like interesting because i think if ethereum is trying to be the internet like what what a lot of these people are trying to build are like web browsers right like when you think of like a client it's effectively like a web browser for ethereum and the original parity client actually had a ui like a web browser ui uh now they've all ditched that but um and and i think that kind of gives you a good feel for like why would they do that it's like well why do people build chrome or firefox or like safari like you know different organizations want to like own access to the network like the interface you know to access on the network for a bunch of reasons like you know and and so i think you can get this mix where like you have these organizations that are financially motivated like consensus is a company sigma prime is a company nevermind is a company right like they need to make money at some point somehow they don't necessarily make money on the client itself or need to ever do that but like they very much need to like survive in the long run as an organization and they i think they do provide like the people working on this are not all just like random volunteers basically like a lot of them i think do see themselves as a company as like professionals who need to ship high quality software.
And we get a lot of, let's say Fred Wilson was complaining about through that. The thing we don't get is the top-down roadmap. This is the other thing that's 10x easier in a startup. You have the VP of product, talk with the CEO, say, okay, we're going to ship these three things, and then that's done. And then you can just execute on them. We can't do that on Ethereum for many reasons. The first is just like the people who write the code aren't the people who run the software as like with the majority of the stake or the majority of the nodes on the network so it needs to be like this weird sort of conversation across all these places of like what what is the thing we're converging towards and otherwise you know client developers can write code for a bunch of stuff um but if the community doesn't want to run the upgrade then that was useless and similarly if the community might want a bunch of stuff to be possible on Ethereum, but if they can't convince client developers that there's value to it, that it's safe.
Yeah, safe is the big one. Usually they can't convince client developers that it's safe. But then the code doesn't get written, right? And it doesn't go live. So I think this is the part where from the outside, it's incredibly messy. And even from the inside, it is incredibly messy because there's no VP of product who can be like, okay we ship this thing um but in terms of the contributors themselves i do feel like most people could like be spending their time doing something else because they're smart they're motivated uh so you know they want their time working out there to be valuable and you know i think that does create a pressure to like ship meaningful stuff um yeah yeah so i mean there there are certainly there are organizations that have structure and are able to ship but they're like a piece of the larger kind of amorphous puzzle i think um ben edgington referenced a it's an article from i think 1999 about linux the cathedral in the bazaar and how you know the ethereum process is much more about it is a bazaar you know it is a place where um there's lots of different specialties lots of different things going on and like sometimes if there's something missing naturally somebody's going to kind of show up and fill in the gaps because it's you know, there's a motivation to kind of be a part of this thing.
I will say, so you said in 2018, 2019, we weren't shipping. There were Herculean efforts going on on Geth specifically. I mean, certainly on the beacon chain stuff, like that was all being worked on. But like, sure, the feature set that users saw being upgraded in Geth was very minimal. but like the amount of work going on into like sustainability of that, of guests in the context of main net, like state management, state access database optimizations, all that kind of stuff. So that like it can't, so that it can handle state growth and not be docile off the network and optimizations and sync and other things like that.
Like that was happening. That was very, very important critical. But it was just like, it wasn't felt. So I think it's important to note as client developers, there's always kind of as many streams, but you can think of two streams like shipping new features and maintaining the client. Right. And like it oscillates between how much they're doing of one or the other. In 2018 and 2019, there was a lot of critical of the of the latter of that maintenance of the client. And maybe that goes back to what Tim was saying was that, you know, there was a lot of shipping. But if you tell me what an optimization inside of Geth looks like, Danny, I have no clue what that means.
Sure, because it doesn't matter to you except that it kept the network up. But yeah, I will notice when the network goes down. And so I haven't been seeing the network go down anytime soon. But Danny, I want to zoom in and just get this a little bit more concrete if we can. The way I've kind of pictured you and your job coordinating the arrival of the merge and proof of stake, and maybe this is incorrect, so we can start there. is you just go to the heads of the client teams, and maybe Tim, this is also maybe your job as well, you just go to the heads of the client teams and just like, all right, we need to make sure that this part works with the other client teams.
So you drill down into Prismatic and you talk to Preston and Raoul and be like, hey, are you guys coordinated with the other client teams? You guys all Gucci over there? And so first question is, if that's what you were doing, how many people were you interfacing with like a semi-regular basis for like the months leading up to the merge like if can we actually like put that into a number and then like if that's n plus one where you are and danny's uh danny's n preston van loon and raul are like n plus ones as in people that danny actually interfaces with how many people are they interfacing with that are also working on the merge right like the question really is how many eth does does it take to make a merge happen and like is there is it possible to put these things into numbers but I don't spend a lot of my time knocking directly on doors right I actually a lot of my time on upgrades is spent writing specifications okay and communicating and educating and coordinating around those so like and then dealing with the feedback loop around that right and a lot of that isn't like, Hey, Preston, have you seen this thing?
A lot of it's like, this is bubbled up as very important, um, pinging the right people or making sure it comes up in a kind of a group setting call to kind of work through, uh, and get through. So the coordination mechanisms by default are very good, right? We have, we have get, we have get hub, we have public channels and stuff like that. So like, I don't have to, I don't have to be a hub, right? Like I have to, sometimes it's like a matter of knowing what's missing and saying, Hey, can you do this? Or, Hey, like, I really think you should take a look at this, that kind of stuff. But a lot of it is just kind of like keeping your eye on, on, on the things and making sure the pieces come together.
And sometimes it's a bit more about like seeing, seeing the future in the sense that, okay, we have to write the software. We have to write tests for the software. We have to do test nets, just do this and do that. So it's a matter of like making sure that the people that are going to be involved in this piece of the puzzle or aware that that piece of the puzzle is coming right and that uh they need to keep their eye on this so they can trigger that piece of the puzzle so you know it's it's it's a lot more kind of these like soft things um kind of maneuvering around and then and then also like being the more that i think tim and i both are like moderate to deeply involved in the technical weeds at times so that we can see so it helps is kind of see how those pieces of the puzzle fit together and knowing how to get ahead of things and make sure they come together properly.
Tim, any thoughts on this? I guess to answer your end question, if I had to, like, my sanity, probably, like, I must have been in touch with 25 to 50 people. Like, and definitely, like, you know, 25 would be, like, multiple messages, multiple interactions per week, right? And then 50 is maybe if you're like once every one or two weeks. And then you probably 5 to 10x that in terms of number of people. For sure, 150-ish people working roughly full, not necessarily full-time on the merge, but for whom the merge was their main thing. That seems roughly right. But then if you add a bunch of adjacent folks, probably double that or something.
There was not like 1,000 people contributing. Yeah. I mean, if you start thinking about all the professional node operators and stakeholders, then you get into quite a many, but I don't think that's what we're doing. Yeah. But if you're thinking about people writing code that then gets used by professional node operators or average node operators, I say my upper bound of loosely involved is on the couple of hundreds. Tightly involved is on the hundred-ish range. Yeah. And that might be variable even within a client team. They might have, like at the peak have had four or five people dedicated to getting out the core merge feature set.
And then for the past three months, four months might have been more like one to two owning it. And then if they needed backup because there was like some big hole or minor specification change, more people would be jumping in. So, you know, it's kind of all over the place. The fact that we can't really pin down a number is awesome. Let me just go to the Ethereum ecosystem org chart. running a quick analysis you're muted ryan well honestly this is what i wanted to to kind of ask because i think that there's a um like a wisdom here and a resilience and a strength and i would even say a scalability um here that silicon valley doesn't benefit from and can't benefit from because this thing is um so decentralized now actually when you kind of look back and you actually see that it no it can ship which is the main charge if you have like a decentralized community it can't ship no it can ship then you look at how actually strong this thing is and how many individuals are involved because you not only have all of these separate gigabrains in all of the different client teams you also have the rest of the ethereum economy working for you right and like staking providers and, you know, bridge software that's being built and infrastructure applications like Infura and Etherscan.
But then you also have like the rollup centric roadmap, which further creates innovation on, I think, what we'd now call the execution layer of Ethereum with teams like Arbitrum and Optimism and like Matterlabs and ZK Sync and Starkware and all of these teams with their own set of like gigabrains are now economically incented to continue hacking and developing on Ethereum code base and like bringing that back into the core. And so when you start to like look at the different rings of the onion here, you have maybe like this core team and like these, you know, coordinators in the core dev group, but like there are so many other layers to this.
And this is a scalability that a Silicon Valley corporate structure could not possibly seek to emulate. And it allows you to like... Right, it's much more of the ecosystem. Yeah, it allows you to expand in so many different directions at once. It also has a resiliency, right? Like Ethereum needs to exist if the EF ceases to exist. Ethereum needs to exist if Nethermind closes shop. You know, like this, and that's a design constraint that like Google doesn't have, right? Like Google exists when Google exists. Like that's, they're the same, one and the same. Whereas the Ethereum protocol and the abstract and Ethereum network, you know, are independent of any one of these actors.
And that is a like very important design constraint of Ethereum. and thus it builds and operates in a way that is just fundamentally different than a corporation. Danny, Tim, when we come back, I think we want to talk about what's next. What's next for you individually? What's next for the devs? And then also what's next for Ethereum? We've bitten off the merge. We've successfully completed it. Is that the end? Are we ready to ossify? Is there more ahead? Guys, we'll be right back with these questions for Danny and Tim. But before we do, we want to thank the sponsors that made this episode possible.
Juno is bringing crypto-friendly banking straight into your checking account. With Juno, you can send money from your Juno checking account straight onto a layer two, like Polygon, Optimism, Arbitrum, and they have ZK Sync and StarkNet support on their way. You can skip the ACH wait times, you can skip all the gas fees, and go straight from your checking account to an Ethereum layer two in seconds. Inside Juno, you can buy and sell crypto with $0 fees, and your Juno checking account comes with a metal MasterCard that gives you up to 5% cash back on your spending. Juno is also giving you $10 cash back on your first crypto deposit and $100 when you set up a direct deposit.
This ad just writes itself. So go sign up at juno.finance.com. ZKSync is an Ethereum Layer 2 network that is pushing the frontier of high-performance blockchains that don't compromise on security or decentralization. ZKSync has combined the power of zero-knowledge roll-ups in the Ethereum virtual machine, enabling developers to build the greatest Web3 projects possible, ones we haven't even seen yet. Crypto needs its killer applications to onboard the world, but crypto killer apps need ZK Sync as a platform to build on first. It's generally accepted that zero-knowledge roll-ups are the conclusion of crypto blockchain scaling technology, and ZK Sync is leading the charge into the final frontier of crypto economics.
So if you're a developer who wants to build your app on a future-proof foundation which gives your users the best UX possible, check out ZK Sync's website at zksync.io. And yes, there's also going to be a token, so give them a follow on Twitter too, at ZK Sync. The Brave Browser is the user-first browser for the Web3 internet, with over 60 million monthly active users. And inside the Brave Browser, you'll find the Brave Wallet, the secure, multi-chain crypto wallet built right into the browser. Web3 is freedom from big tech and Wall Street, more control and better privacy. But there's a weak point in Web3, your crypto wallet.
And most crypto wallets are browser extensions, which can easily be spoofed. But the Brave Wallet is different. No extensions are required, which gives Brave Browser an extra level of security versus other wallets. Brave Wallet is your secure passport for the possibilities of Web3 and supports multiple chains, including Ethereum and Solana. You can even buy crypto directly inside the wallet with Ramp. And of course, you can store, send, and swap your crypto assets, manage your NFTs, and connect to other wallets and DeFi apps. So whether you're new to crypto or you're a seasoned pro, it's time to ditch those risky extensions and it's time to switch to the Brave Wallet.
Download Brave at brave.com slash bankless and click the wallet icon to get started. and we are back with Danny Ryan and Tim Bako I think if I were you guys and we were post-merge I'd be having this like big existential crisis it's like what the hell do I do next how does it feel to be on the other side of it do you guys know it are you guys taking a vacation you're going on a break what it was like the next thing the next chapter of your guys's lives uh danny i'll start with you um i spent a lot of time on friday and monday and tuesday doing a deep dive on the 4844 and withdrawal specs wow no breaks huh i think i was totally off on thursday i was useless on thursday because i stayed up till four in the morning right um but yeah pretty much i want us to be in a good position to have shanghai conversations and uh keep keep things moving i think withdrawals are very important to the community so there's a bit of testing and refinement going on there as are scaling proposals like 4844 um and you know again one of the things that i really enjoy doing and i think i have a good insight into is kind of writing and reviewing specifications so i want to make sure that i get that done so that we can keep moving but uh yeah i need a break um after devcon i am taking a not insignificant amount of time off.
Okay. So in a middle of October, second week of October is dev con. You can take like a month off. It's looking like three weeks, um, you know, maybe up for debate. Okay. Tim, Tim, you taking a break anytime soon? So actually I think a break right before the merge, um, I don't write code for this stuff. So, you know, when my job sort of picks up now, I guess in a way, uh, now that the merge is out of the way, you can ship so many more things. Now we need to talk about what we ship next and that's kind of what I do. And I think we had purposefully stopped talking about that for the past four or five months just because we wanted to focus on the merge and it was so big.
But you can think of it a bit like a dam. We kind of closed the dam and the pressure has built up and now people really want to talk about what comes next. So yeah, that's what I'll be focusing on. And that said, we didn't want to have the client teams jump into planning Shanghai the day after the merge. So we're going to be canceling a couple awkward devs and consensus data calls in the coming weeks. So people can have those conversations async and slowly kind of wrap their heads around what's being proposed, what are the different options here, but without feeling like they need to kind of attend every week otherwise they might miss like the whole upgrade scope changing um so i think it's like laying the groundwork so that you know after devcon like once people come back and they've had a time to disconnect and kind of refresh um we have a good idea of like the general picture and then we can kind of finalize the scope and and start start implementing these stuff in some sense consensus layer teams have been working on the merge for four years straight you know ever since they started working on the beacon chain the beacon chain was always intended to become consensus mechanism of theorem that's all they've been working on you know is getting it ready for being the consensus mechanism of theorem so i think um you know everyone is taking a moment you know is that is that a week is that a day is that is that a month um and when exactly hard to say but everyone's taking a breath um a well-deserved moment absolutely super well deserved yeah four years straight of just proof of stake merge proof of stakes merge i'm sure you need to take a break to be able to come back with a new frame of mind.
And it sounds like the answer to the question of what's next for Ethereum is Shanghai, the Shanghai hard fork. By definition. Yeah, by definition. But also, it sounds like the Shanghai hard fork hasn't totally been defined. But Tim, to the best of your ability, can you kind of just like, you know, using our going westward metaphor, Can you explain what's in the path ahead of us? What is the Shanghai fork mostly going to be about? Yeah, so like you said, it's still very much in flux. And part of the reason why we stopped discussing it is because like three, four months ago, at least on the execution layer side, people were starting to like make decisions about what should maybe go in and whatnot.
And it felt like it was so early, like we didn't have the code for the merge done and we were already committing to all these things for Shanghai. And on the execution layer, have this concept of like considered for inclusion which is like a soft commitment to eips because usually we don't know how like big eips are until we actually start writing the code so considered for inclusion is when we say look you know this sounds like a good idea it seems like it's not going to break ethereum we'll try and implement it and usually if there's no issues we would we would move it to maintenance right um if if we do find something not you know we might fix it but but it's not like a strong commitment that we'll ship this no matter what.
And then the consensus layer side has a completely different process of just like making PRs to the specs. And I can let Danny chime into that after, but at a high level from the execution layer side, the two main things we had sort of soft committed to our beacon chain withdrawals. So there's the spec for that is pretty much done. I like Danny was saying, He's been refining it and writing tests. And this is something we did like leave out of the merge. And there was always this idea that like we would have to get to it shortly after. So we have like soft committed to that. It's not implemented yet.
The second big thing or potentially not as big but it's this EIP called EVM object format. And this is like a neat thing. People have been trying to improve the EVM for years. And there's always this question of like, well what do you do with existing smart contracts, right? if you add new functionality, are you going to break everything that's on chain? So the Epsilon R&D team has come up with this really smart thing where we can define versions of the EVM on the network and have contracts specify that they use a new version. And then you introduce new functionality only in those, but everything that already exists kind of maintains its current behavior.
So there's no changes there. And so that's the second kind of big thing we'd already soft committed to. Um, there's a bunch of other smaller things we've we've soft committed to, but you can think of them as, you know, basically one line changes. Um, they're not in practice, but you know, they're all very minor features that add, um, yeah. One line, one line of feature and then like 10,000 lines of testing. Yes. Yes. So there's a couple of those. Um, some of them actually aren't even that much testing because they just add bounds that were implicit on the network and we just make those explicit.
So things like that. But basically the two big things we've self-committed to are these withdrawals and then this EVM object format. There's a whole other list of things that's being proposed. There's an Ethereum Magicians tag now called Shanghai-candidate. So if you go to Ethereum Magicians and you search for that, you can see the whole list of things that are being proposed. And this is what over like the next month, people will discuss and kind of wade through. And then we'll see if we update our currently existing list with other stuff, if we remove anything, because we think it's either no longer relevant or because there's some like unforeseen complexity.
So that's what we'll, yeah, right there. Okay, so if you click there, you see like say the first one there, Shanghai candidate, EIP 3074, but then you can see there's a tag under it called Shanghai candidate. So if you click on that tag, oh, you're actually already on the page, yeah. So that tag will show all of them that are being considered and the discussions on them. So yeah, so that's basically it on the execution layer. The consensus layer is a bit different. So Danny, do you wanna kind of walk through how that works? Right, so the consensus layer, the beacon chain was architected in parallel to the proof of work chain, we all know this, and then it was merged.
But in doing so, the specification process was independent of the EIPs at the time and ended up in its own repo consensus specs. And here features are proposed as kind of like little branches of code. It's an executable specification where they also do testing on issues and PRs we've discussed them. We do expect this process to over time inherit and unify a bit more with the EIPs and especially with some of these features like cross layer. So like withdrawals are not just a feature on the consensus layer. They're a feature on the consensus layer that interacts with the execution layer. So again, and I think these things will converge over time, but one of the big things that we have on the consensus side that's been specced and is up for discussion or refinement or the withdrawals, the consensus layer analog to the withdrawals.
And then another feature on the consensus layer that has been specced and is up for discussion is the 4844, both of those being cross layer. There might be, you know, I think especially between now and DevCon, there could be like a little thing or two that pops up and ends up as kind of, you know, an analog to one of those like one line changes. Like some sort of like weird edge case that's worth cleaning up. You could expect maybe something like that pops up. But those are the two big ones under discussion. I think the famous ones, the ones echoing kind of the user and investor community in our ears are definitely withdrawals.
So people want to know if they can get their ETH back, right? And when, at what point in time. And the other one, of course, is, as you just mentioned, Danny, EIP-4844, which maybe is the most famous EIP since EIP-1559. 1559, excuse me. Apparently not that famous. Yeah. And so this is one, proto-dank sharding. And this is all about, we've done entire episodes on EIP-4844, on Bankless. This is all about the scalability of data and providing that as part of the roll-up-centric roadmap. So this is the big... Yeah, and proto, because it's an iterative way to get there. It's the first one. We get some scale, and we lay the foundation to get more scale.
Just one small point on that. It's also because of proto-lambda, right? Correct. And it's dank because it's dank. And it's also dank because it's donkload. Okay, that's just fantastic Ethereum trivia I wanted to get out there. So So I guess maybe zooming out, right? What problems would you say Ethereum still has yet to solve in its red map? Because I think maybe you guys have a divergent view here, but I think everything we've seen from the core dev community is that Ethereum at a protocol, from a protocol perspective, like will ossify at some point in time. There will be fewer changes over time, right?
Like at some point in time, your jobs will be done. And Danny, you could go open that coffee shop that you've always wanted to open, right? But that day is not today. It's not yet. So we've gotten through the merge. But what are the other core problems? And I guess the high level of the merge is now we have staking. And we no longer have proof of work. We've cemented Ethereum's monetary policy and Ether's monetary policy as well. But what other big problems are there to solve, would you say, Danny? So my lens, when I'm thinking about what needs to happen to that one protocol, is first and foremost, we need to get to functional escape velocity.
Vitalik's written about this. Essentially, the minimum amount of functionality on layer one to be able to do, extend, and build, and whatever on top of it so we can stop changing it. And then my lens from there is, and I talk about this all the time, security, sustainability, and scalability. Right. Like I think we made a massive leap forward with proof of stake on the security front, also on the sustainability front. Sustainability is nice. It encompasses a number of things. Obviously, we've got that environmental sustainability stamp of approval. But now there's other types of sustainability.
So like the sustainability of the protocol from the state standpoint of state growth. Right. So we need this protocol to be sustainable such that we don't need to intervene with it. I'm abusing that term because sustainability, environmental sustainability and protocol sustainability is probably a little bit different. But, you know, so we need to we need to balance state growth. We need to bound node resource requirements so this thing can stay decentralized and we need scale. Right. And so that's that's roll ups with the nice L1 data multiplier through through dank sharding. I, there's probably some other very important things that could manifest inside of Ethereum, like the beacon state route landing in the EVM or BLS signatures landing in the EVM or things like that.
A lot of this stuff, personally, I consider nice to have and on our ossification journey, maybe they'll make it in or not. But really, for me, it's this thing needs to be secure, needs to be sustainable, and needs to be scalable. and we need to do the minimum and simplest approach to get those three things in a place where we don't have to touch this thing anymore. But Danny, are we like five years from the coffee shop? Are we 10 years from the coffee shop? Is it longer? I think five years is actually very, very, very reasonable. And the nice thing is, especially like sustainability, like the node architecture sustainability, that's something that isn't going to bite us in the ass tomorrow.
It's something that we have to fix, but it's going to, it can take time. And then the scalability, we're getting scale through all today and we're working on multiplying that iteratively over time. So it doesn't actually feel like there's a massive fire and that we can do this right and we can do this over the next three to five years. Tim, what about from your perspective? I think five years is optimistic, but I think one way you could do this if you really wanted to never touch the core protocol again is you can segment this between changes that require consensus level changes, not consensus layer, but just like protocol rules.
And you can think of something like on the execution layer, like a stateless Ethereum, right? Like we need to change the try structure from one thing to another. This requires a hard fork, potentially many hard forks. But then once that's done, there's some stuff that you can potentially do outside of the protocol. It's almost like semi-authification. You can have something where like, example, EIP4444, which is about dropping the history requirements for nodes. But something that doesn't change the protocol rules for Ethereum, it changes the client behavior, right? And it helps to get kind of a more accessible nodes and greater decentralization.
So I could see a world where like, you know, maybe we have five-ish years left of like consensus layer changes. And then I'm not optimistic that will be done then, but I could see maybe the second half of that decade like things that clients agree. So like the protocol rules don't change, but the implementations of them all kind of change in tandem to be better. And I could see- For example, you could have a better state sync protocol and that you could do it in eight years and doesn't change Ethereum. Yeah. But even EIP-4444 doesn't need any protocol changes, right? Yeah. That's kind of like a sync protocol change.
Yeah, exactly. Yeah. So I could see, and same with something like stateless, you could like front load all of the protocol changes, but only start gossiping the witnesses and building the blocks separately after that right and the rules of the protocols won't change from that um so i i could see that i i doesn't get it all done in five years but if you if you give me an extra five or you don't change the protocol rules um i yeah i think we're going to not i think it's going to get harder and harder and for and for good like because it's just going to be harder and because it's for good reason and And so things that take 10 years, I don't think are going to happen.
So I agree with that. I feel like the bar that a feature needs to hit or a potential protocol change needs to hit to be considered keeps getting higher. And the reason is just there's more stakeholders, right? There's just more people who need to agree it's a good idea and there's more impact if it goes wrong. And usually we're also at the point where there's not many free lunches anymore on Ethereum. Most of the things we're considering have trade-offs. By virtue of having your trade-off, it's like you need to get people to agree to one side of the trade-off, and that gets harder and harder as the community grows.
So I think we have this natural tendency towards there, and the question is, how do you strategically fit all the potential changes such that they're doable before the community is too big and too hard to coordinate for something like that? And I think the message we're hearing from both of you is that there's a lot of work ahead and like years of work ahead to pull off the entire Ethereum roadmap. And I know we're all here to like because we believe in crypto, because we think that Ethereum will make the world a better place. But also, Tim, I know it's your take that that's not necessarily inevitable.
And maybe this is a reason that we actually have to put in the hard work. Bankless Twitter account recently tweeted out, what's your most cancelable crypto take? And I thought, Tim, you had a really interesting, insightful take here, which is it's not a given that crypto will actually make the world better, is what you said. And we should heavily caveat such claims and push back and work hard to make sure it actually ends up being the case that the thing that we are building actually does make the world better. Can you talk a little bit about that, Tim? Yeah, I feel like the bankless Twitter baited me right before this call.
Yeah, look, I think, especially with the merge now and I think in general, like the space, we want to believe we're building something that makes the world better. And I think to be clear, crypto even today brings a ton of positives, right? And the question is like 10 years from now, is the balance in that positive or in that negative? I think it's sort of recognizing that There's still many scams. The environmental bit was like concerning up to recently. And, you know, things like privacy. There's a world where like crypto enables mass financial surveillance on a scale that's like never been seen and like lays the path for like central bank digital currencies.
You know, we kind of build the technology that's like governments would never have thought to build. And then they just co-opt it and build kind of the worst possible version of it. And, you know, I'm not saying that that's the likely outcome. I'm saying it very much is a possible outcome. And that's something that like, as a community we should think about. I think somewhat paradoxically at the protocol level, it's almost where we have the least impact on a lot of this stuff. I think we can help, you know, anything that helps make joining the protocol and participating as low requirement as possible is good because it means you just get like a more diverse set of participants and it's harder to capture.
But I think when thinking about what applications we build, what scaling solutions we build, I don't know, that's something that's very much on my mind. Are we sure that this is not just going to be used by some government or just use as is and force everyone to say use USDC? And then that's actually a worse status quo than, say, bank accounts on many respects. The joke I was giving with Ryan is when we were talking about this tweet before the live stream, before the live stream, Tim, was that, oh, sweet. We just shipped Ethereum to proof of stake. Now our Ponzi sys platform is like super efficient.
It's going to be great. Right. Uncensorable. And I think, yeah, I think, you know, scams are like almost the easiest version to like defend against because like people just kind of learn. Like you look at the early Internet, right? There were tons of scams and they like mostly went away or got like relegated. So I'm, I'm not, I don't lose sleep over scams. I think like privacy and like financial surveillance is probably the biggest one that I think is, is, is a challenge. And, and it's, it's, it's a challenge, not only because like the tech is hard, but also because there's a world where you build privacy.
And that's also like a terrible world. Like you, you know, there's very bad ways to build privacy software. So like, yeah, it is. I think it's super interesting. There certainly can be with any of these new technologies, many unintended consequences that become unleashed. I know in particular, of course, you guys, I'm sure I've been following like the, you know, AI type discussions and AI ethic type discussions. It's a bit of a cop out to say they're unintended. What I'm saying is I think we can very much predict the second order effects. And I think there's a world where like, and the AI risk people will tell you that as well, like with Google, when they'll criticize Google and open the AI, it's like the people there are very well aware of the risk, but they're driving in that direction thinking they will somehow avoid them.
But it's not like an unintended consequence. It's just like a second order effect you chose to dismiss because you thought you could like navigate around it. And we very well might, but it's, yeah, it's not a given, I think. This kind of stuff breaks my brain a little bit, but Danny, do you have a take on this? My take is that without such technologies that blockchains enable, we're on a crash course anyway with the massive corporate surveillance and government surveillance and kind of the manipulation and control going on here. And so at the very least, this intermediates that trajectory and allows us to kind of rethink and re-architect what's going on.
Obviously we can re-architect it badly, poorly. But one thing that blockchains do provide that traditional structures do not is that even if we end up in a weird or bad equilibrium, you can do new things, right? So if we end up in a world where we're using two roll-ups and they're massively surveyed and controlled, you can actually build another roll-up that has privacy, right? So like there's a certain amount of choice, as long as we have a neutral base layer that the stratum provides for humanity. Obviously there can be structures beyond that disallow us from exercising that choice. For example, if we were regulated to use the government sanctioned roll-up, we might have issues in exercising our choice to create a new privacy roll-up but um that kind of extra protocol consideration aside um these protocols allow us choice that does not exist in our current structure so i i'm you know i'm a pessimist i'm trying to be the optimist right here but uh you know i think that that's my optimistic take here and i did caveat my tweet with like a more optimistic one which is like it's really hard to have this conversation because when like critics will compare you to like perfect, right?
To the perfect world. And they'll say, you know, like Ethereum is like not perfect because of X, Y, and Z. But then like Danny was saying, like the status quo very much isn't, right? So ideally all you want is like a net improvement over the status quo. But to get that, I think you need to almost hold yourself to like a much higher bar internally. But yeah, it's a very tricky thing to do when again, all this happens in the open and there's no top down, you know it's not like i can choose what privacy solutions ethereum will build right like you know i can like that or even more so that people will build on top of it right exactly exactly yeah yeah so like i you know like i can do many things like an individual but it's like it's not like a top-down thing so it's like a tricky yeah it's almost harder than the ai problem because the ai problem you know you have like a limited number of organizations with enough uh hardware to actually meaningfully make progress and then you can like steer them we have like this amorphous blob of people all working on it um yeah and that's it that's a harder thing to yeah this is interesting it is interesting that it's kind of out of the core dev hands right and it's you know it's back to kind of the the layer zero back to the community and i do appreciate something that that you were saying is like um these types of takes are not takes that you'd get canceled for in Ethereum.
I feel very proud that the Ethereum community is always one that kind of is its harshest critic at times. And I hope we're able to preserve that moving forward, because I think that's gotten us to the merge and gotten us to this era of momentum around shipping. And Tim and Danny, we just want to thank you guys both for joining us and also for helping to deliver this. I know it's not just you, of course. You are flanked by and represented by dozens, hundreds of different... An uncountable number, yeah. Like developers from around the world who helped make this happen, but as kind of their voice and their face, I think on behalf of a community of users and passionate people, individuals on the bankless journey, like sincerely, thank you.
We appreciate you. We appreciate all of the core devs, all of the researchers who made the merge happen. And it's feeling very much like the future of Ethereum is bright thanks to your work. Thank you. Yeah, and echo that. Shout out to everyone involved in this. It was a colossal effort. Speaking of which, by the way, we are having Vitalik on the show tomorrow. What should we ask Vitalik, guys? Any burning questions in your mind, Danny or Tim? I talk to him all the time. Ask him. Yeah, I think Vitalik's been thinking a lot. He's been drawn into the AI conversations and where that's going for humanity.
I think a lot of people have, but he has some really interesting takes there. So if you have a moment, take a sidestep from crypto and his takes on AI. That sounds like some great bear market content. Well, we will leave it there. Everyone in the midst of the bear market, but we are building. Danny and Tim, thank you so much for joining us. And of course, Bankless Nation. Remember, none of this has been financial advice. ETH is risky. So is Ethereum. It always is. Crypto is risky. All of it. You could lose what you put in, but we are headed west. This is the frontier. It's not for everyone, but we're glad you're with us on the Bankless journey.
Thanks a lot. Thank you. Thank you. Thank you.