 Cool, I think we are we're alive awesome. Yeah, I know I'm very grateful for for the talk here I think this time as this hyper ledger Conference is starting we want to change a little bit like the dynamic we would not do like a 40 minutes talk only And we just literally do some some discussion with Matt. Let's introduce ourselves briefly. Yeah, for sure So I'm Matt Nelson. I'm a product manager that helps manage basu at consensus So I've been working with a bunch of the hyper ledger community now for about six months and working on the merge You know for even longer than that so very excited to talk about kind of what we view as the Next steps post merge how we want basu to be able to serve a bunch of different use cases clients needs you just get on that and You know basically how we see the client evolving in this landscape. Cool. I'm francesco I'm part of the form Consensus I'm working mostly on on devrel for for protocol metamask and infura and I'm grateful that we are today explaining the merged next steps and Anything that to do with with hyper ledger basu Cool, because we can start it will be very interactive. So feel free also to ask questions I know we are many today in the audience But but hopefully we get some people's ask good questions online Yeah, we just recap. Hopefully how many people know what's happening actually in one day and a half a little bit more I don't know what's happening. Yeah, everybody know probably but yeah, why the merge why we are here what's happening and And and and yeah the progress in terms of ecosystem that we also overview baseless execution client and and then what's post merge infrastructure will look like Let's just start and feel free also to jump in these are literally like we said, okay How we feel in 40 minutes. So we literally I put a lot of like interesting slides just to give an overview but we need to Yeah, we can just quickly quickly show like how a web 3 and digital assets in terms Of like reaching out audience we put some numbers here I don't know like Matt feel free also to add things but those are quickly quick slides before we are getting to the important parts I Think the the next slide. It's it's quite interesting. So how how is the theorem ecosystem look like? How big in terms of like user addresses and and the transaction per days So this is something that is is growing a day today and and yeah And I don't know what I think the latest number around the 400 400,000 active depths And we're also seeing and you know the builders market is is remaining intact and it's still growing compared compared The token markets that we see today. Yeah, but Yeah, cool. I don't know any questions until so far or anything to add Let me jump so why the merge I will stop speaking here But Matt you want to you want to say quickly what's what's the roadmap and why we're here? What's happening in one day and a half? Yeah, yeah You know as the first bullet outlines, there's an increasing urgency around proof of stake The reason being is that aetherium has roughly the carbon footprint of the country of Finland And that is something that we're eager to get rid of for a number of absolute reasons the you know kind of less Sustainable points under that are that we think more enterprises will be interested in cryptocurrency and blockchain technology when the You know nightmare of sustainability is resolved and then the network So we were really eager to get rid of that so that more and more folks can come online without having the You know the frankly embarrassing carbon footprint that aetherium has today There's also a desire to democratize access to the network proof of stake in this case will allow more and more nodes to come online That are not basically concentrated in the hands of mining pools And of course there's optics around The usage of these things as I mentioned and there's going to be changes to the economics of the ether token that we are really excited About and those around the issuance rate specifically But there are some other tweaks that I encourage you to read about online to how the economics that work The other is that you know with the merge kind of sets the stage for the emergence of kind of a set of protocol upgrades in aetherium Specifically around roll-ups other L2s and other scaling technologies One of the misconceptions of the merge is that it will decrease gas prices. It will increase Scale and speed on the network, but that is actually not the case But it does set the stage for some upgrades that will Allow those technologies like roll-ups to become first-class citizens on the network Which will hopefully see a lot of these Improvements come down the line much much faster now that we're also removing the biggest obstacle to upgrading the aetherium roadmap If you go to the next slide it talks kind of more specifically around what we're looking at Some of the points that I had mentioned previously again The the reasons why we think that more and more enterprises will come onto mainnet after the merge Are around these kind of four points the energy efficiency is although listed at number two is personally my number one The you know diversity and openness of the network as I mentioned as we remove the need for hardware intensive mining operations to participate More and more Validators and clients can come online and participate in the network and we're going to see I hope a lot more enterprises join Yes, you still need a capital investment in order to participate in proof of stake Although for a lot of the enterprises that I think are are ready to join the public network that Investment is not quite so large The third and fourth point are really about the hard work that's been put into the merge from an architecture perspective around the seamless transition So API's will largely not be changing as Dano mentioned the Randall opcode is one of the only ones that requires a change So we're really making this easy for developers to continue to use the technologies before and after Yes, Basu has had to undergo a lot of changes in order to kind of go through this merge transition But as far as developer experience is concerned and those building on top of the client I think that it's you know, it's going to be pretty much the same before and after with additional components around proof of stake The last is number four. It's better for DeFi. That is really based around the economic changes that I mentioned Changes to the issuance of ether changes to the way that if ether is You know burned so essentially, you know with in combination with some previous things mentioned or I encourage you to look up EIP 1559 Then you know, we're going to see a lot different economics around the way that ether is operating Yeah, I think definitely also like the I mean what you're saying about openness and diversity of Ethereum clients will play a big role because today as we know we are kind of on a monopoly and having a Differentiator in clients is playing a big role. Yeah. Yeah, we're seeing, you know, Basu has grown tremendously in the past few months We're really excited about that But it's frankly due to a lot of the work that people in the community have done to help develop a client for Ethereum Mainnet and making sure that we are doing press around what that looks like for diversity participation and for getting enterprises involved Key takeaways we can I think skip this I'd rather go straight to questions Exactly. That's that's that's a longer. I mean, that's not long, but it's quite interesting exactly where we talk right now around around key takeaways Cool. Yeah, merged timeline. I think we are ready kind of like past pasties I but but it's quite interesting to have an overview. I think Bellantrix was successful with some bugs. Yep, right? September 6th was the beginning of the merge countdown The actual date and time is predicated on network conditions But there is a prediction that it will be sometime around Thursday morning on UTC So if you're in the United States like me, that'll be probably Wednesday evening And if you're in Europe, it's probably sometime Thursday very early morning We might see the hash rate and the network drop and delay that timeline a little bit as minors exit the network But we're hoping that it will stay relatively stable and the merge will be completed sometime on Thursday. Yeah, that's All those things to say that timeline is quite long because there's a long and storied history of the development of the V-conchain and it's been very exciting to participate in that but you know really it comes down to what we're looking at here on the screen We have a proof-of-work-based Ethereum today And we have additionally currently running proof-of-stake beacon chain, which is the consensus layer as it's called And as we go through the merge the current kind of proof-of-work stack will be called the Execution layer and that gets us to kind of the crux of what we're looking at here with with basu's evolution from an Ethereum one client to kind of an execution client and the reason around that Split is that the consensus layer has been intentionally removed from the kind of execution Because it one allows us to run consensus in a way that is based off of proof-of-stake but to it it splits out kind of the complexity of Executing and operating on the smart contract layer from the consensus mechanisms So this doesn't immediately provide the speed and scale that we might think with the merge But it will set the stage like I mentioned for a lot of changes to wait that those two layers work separately To allow us to make some very interesting protocol upgrades. You might have heard of sharding. That's one of them I Encourage you to look up EIP 4844 if you're interested to learn more, but basically As you can see still well my head's kind of blocking it, but it's on this bottom layer So the the data availability that sharding is going to provide will be on the consensus layer So splitting these out into two pieces has provided us the ability to really innovate and it allows basu Which sits in this blue? Box the execution layer to become a lot more lean and a lot more focused on Serving different types of use cases and at the end of the day we get a scalable sustainable ethereum But we also get a lot of other kind of benefits of this as basu is not just compatible with ethereum mainnet Because it's an execution client that we're interested in right here. It's executing EVM based smart contracts. It's executing You know in theory transactions that don't really require kind of all the baggage of the EVM And it's we'll get more to this in in the future slides as we go along But it's again splitting this out has allowed kind of basu to reevaluate what we're looking at as a client And we really want the community to help us kind of shape what that looks like going forward And how can we add you know more consensus mechanisms? How can we you know plug this layer out and put something else in on the bottom? You know, so that means support for different kinds of networks Dano just gave a talk on how they use the basu EVM and hadera You know in theory you could use the hadera consensus service to run a network where basu just does the execution And that doesn't even require using all the overhead of the other hadera pieces So there's very interesting things that are going on and I think that if we continue a little bit I can kind of break that down some more, but we can also pause for some questions. I know that was a lot I'm excited about the the layer of infrastructure. We're posing for layer twos That's definitely one thing. How many of you guys know the beacon chain exists. Just raise your hands. Okay, cool Nice cool. Yes, please So the question is how how it will impact the security overall yeah for proof of stake versus proof of work, so that's a great question and the you know There's a bunch of different answers and they all kind of approach this from multiple angles with the beacon chain itself The the reason that proof of stake is effective is because there are monetary Requirements to attack the network so that you know, you might have heard of a 51 percent attack That's the same in proof of work as it is in proof of stake if you control 51 percent of the consensus power Let's call it of the network you can make changes to the way that the ledger operates and then you can validate those changes with your Percentage of the network to make sure that it appears valid So in proof of work that was prohibitively expensive for a number of reasons due to to mining power essentially requiring hardware In proof of stake It's prohibitively expensive due to the fact that you would have to own over 50% of the market cap of Ethereum And if there was a centralized entity that would be approaching that threshold It would be extremely visible within the public ledger of the network to say you know XYZ organizations own 51 percent and therefore would control a number of validators to do certain things There are a lot of other kind of nuances to how that specifically works and a lot of it comes down to there's also kind of self-policing within the network after the move to proof of stake so validators can Slash or nominate to slash other validators when they misbehave so say I try to fake that I have 51 percent of stake I use my keys in my validators to pretend like I have two stakes when I only have one if somebody notices that fact they can Effectively reduce my stake to zero and are rewarded for that fact So I think that we're gonna see you know kind of these watchdogs come within the network We've already we had our a couple of slashing events recently people are I hope incorrectly putting their validator keys in multiple locations But but we're we're starting to see kind of an uptick of people who are Penalizing others in the network one to reward themselves but two to really keep the network secure as a whole Yes, that is true We would hope that everyone would not so the question to reiterate for the stream and for everyone that wants to hear is that the You know as folks exit the network the number of validators would go down and therefore the amount of value needed to attack the network will decrease Yes, there so there is an example for where you could say oh I would exit a ton of validators over here and then start like a bunch really quick so that I have Quickly have a percentage of the stake and I can take it over However, there's cues to both enter and exit the network so in theory that up attack wouldn't be possible kind of like As like a flash loan sqx plate And to the hope is that as we add withdrawals and exits from the network the demand for staking will not go down It will go up because the more liquid stake becomes the hopefully the more validators will come online There's also the notion of liquid staking in general where I don't necessarily need 32 E to run these validators So you're using a technological approach to add more validators to the network So there's things like rocket pool like Lido where they match up eat basically smaller steaks with larger steaks to create one unique validator Yes, you have to presume that those organizations won't collude against the network as a whole I think that we are going to see kind of centralization around certain entities that control portion large portions of network steak like big exchanges or these groups like like Lido, etc that control a lot of these steaks but It is hard to say how this will play out in reality. I'd encourage you to read up Maybe my understanding of how the secure the network would be is an open question but the the again the costs have moved from basically The the hardware perspective to an actual stake in the hundreds of billions of dollars And if you look at the breakdown of the top sets of validators So, you know these accounts since the validator keys are basically there's public keys for all these things you can in theory Look and see who controls what portion of stake. We're not quite at the point where we have to get worried about centralized entities controlling like like, you know XYZ exchange has maybe 20% of all online validators We're not quite at the point where we're worried about that yet But there are some open questions though. I think as far as the merge transition is concerned A lot of the kind of mitigations come down to like the technological components as opposed to the economic components so We're feeling very confident in the way that the merge is going to progress because of the kind of One the robustness of the actual consensus algorithms. So the proof of stake is based on something called LMD ghost which is just a fork choice algorithm So there's a lot of like nuance in that there's kind of nuanced mitigations to certain edge cases Researchers have been spending years trying to figure out what they could be for this exact scenario Once the things level off after the merge. I think like you said, we'll be able to really evaluate what the validators I think my computer No, it's all good I think that the validators will have to see how the chips kind of fall But I again, we're not really approaching the point where any specific entities have Even nation states like would have the ability to create these kinds of Yes, but in so think about it this way as more mission-critical Applications and things migrate to the network more and more folks will be participating directly or indirectly And you'd hope that more value comes onto the network distributed via decentralization whether geographically whether you know politically To the point where the cost to attack the network increases as there's more participation by users. It's definitely a concern But again, there's a lot of none of these things happen instantaneously There are a lot of signals to this kind of thing. It is a public distributed ledger So you would presume that nation states would be watching what each other are doing if they're accumulating hundreds of billions of dollars worth of ETH and Specific, you know, locales. I think that that would be something that people would want to look at for sure I think we should in the interest of time continue forward But yeah, I'd love these questions Just wanted to show the 51% attack would be around 25 billion Yeah, be constrained status. This I think was like a couple of weeks ago, but around 400,000 active validators. I don't know what's what's today the amount, but it's it's I don't know more and more are coming online, frankly by the second as people get ready for the merge So the the activation queue is getting quite long, which is good And like I said, these cues are designed in such a way where It's impot you can't just jump on the network all at once and can start immediately controlling a portion of the stake And there are also execues to prevent kind of the opposite where you can't just withdraw all of your stakes so that maybe somebody else has a 51% stake Yeah, I think we should get straight to the bulk about basu as Mentioned before basu is a monolithic ethereum client What that means is that it essentially tries to do everything as Dana was mentioning It serves a variety of different use cases not just within proof of work or proof of stake But it also serves BFT based consensus algorithms And to this point, it's been quite, you know, great actually. This is a pretty good view of the architecture right here the pieces to note that are kind of Unique to public networks are probably the engine API that is unique to ethereum based public network consensus And again, we have proof of work consensus click consensus and BFT consensus down here The big the reason that the EVM is in a dark green box right here is because as dano mentioned in his previous talk It is actually separated out from the rest of the components of the architecture It can be removed and put in other networks and use the sustainable module and it has been intentionally designed that way through dano's very hard work to make that happen and the reason that we want to do things like that is because whether we like it or not the EVM is coming to gobble up a lot of the smart contracting world for applications that are Created today a lot of the other talks and a lot of the other hyper ledger based projects Their goal is to bring EVM compatibility to other things or to create interoperability directly with the EVM And you know, again, I'm not here to comment on whether that's a good thing or not but it is What it is and within basu it is a first-class citizen and what we're trying to do is make a lot of these other boxes dark green as well where the Components are not necessarily stuck in this layout and you don't necessarily need all of these components So the reason that these kind of things are dotted lines is because they are optional Those are privacy related features. You don't necessarily need to use them You don't necessarily need to you know not use them and they kind of touch a lot of different areas Which is why things can get kind of messy We like this picture for what it is But we're really trying to move kind of towards a new paradigm And I think that that's being driven in part by the fact that we support a lot of different network types And that we want to continue to support different network types and we want to support more network types And they might not use POW. They might not use proof of stake. They might not use BFT consensus You know, we we want to kind of lean into the pluggable consensus We want to lean into the fact that the EVM can go away and you know or not go away rather but exist in other Components exists elsewhere because our users want different things. So if we go to the next slide here Francesco Like what is this kind of boiled down to what are the users and developers want? They want an execution client for Ethereum proof of stake. Sure. They want to be able to run on main net They want a client to connect to a consortium network. Maybe they want to join, you know One of the pre-existing Ethereum based Private networks and they want to be a node that validates transactions running proof of authority or BFT consensus They might be an infrastructure you know Software provider and they want to build a business with a blockchain They don't necessarily know what that means and they don't necessarily know what all of their requirements are right now Because frankly the requirements reveal themselves much further into the line of developing blockchain based applications Then you would think up front And they might want a diverse software to connect to many different kinds of networks This could be like, you know, noses chain for example some other L ones They we can provide basu as a piece of software that connects to those different things. It could be a chain link node It could be you know a bunch of different applications run Semi-adjacent Platforms to a main net Ethereum or they run entirely different chains with different chain IDs And we want to be able to serve kind of all these different things or they may just want EVM execution So the users really don't necessarily know what they want up front Which is why a monolith appears enticing because you get everything in one box However, we only serve kind of the one basu thing and if they just want One of these boxes they have to get the rest of the craft to kind of with it So what needs to change right? Kind of two things that I view and again, these are this is a proposal for what we want to do with basis So this is an active discussion. We want to actively bring people in You know, we have a binary distribution, but we want to go to binary distributions multiple. We want to move to A proof-of-stake distro. We want to have a distro for private networks for proof-of-work networks. What what have you? We don't want to provide everything that users don't want to need and we think this is kind of a step one That's a quick win where you can decouple some of these components in a way that makes basu leaner and quicker And it's for example I just want XYZ for my infrastructure and that means we can give them modularization and componentization Where I for example need to run Just the EVM for my infrastructure because I want to make an application for my new layer one that I don't necessarily It hasn't been built yet. It's a new blockchain technology. It hasn't been built yet I just want an EVM or I just want to run a chain link node Like I said, and I don't need all of the stuff to do with proof-of-stake consensus. I just need RPC I need RPC from basu to be able to run Queries I just want to get data from the network I don't want to participate at all then you can have state storage within basu And you just pull the stuff out via the RPC. So it's a If we go to the next slide actually It's basically like how do we make basu just this execution client, right? I'd like to skip actually two slides ahead in the interest of time This one, sorry, this is perfect Plugable execution, pluggable consensus Possibly pluggable storage we have to figure that one out But it's something that we're looking at very closely because there's a lot of nice use cases that are enabled by pluggable storage and then networking pluggable networking You know what like that that one is unique I haven't we haven't thought too much through that yet, but you know there as Dano mentioned We have different kinds of networking and we have different kinds of interfaces that are not just JSON RPC How do we create a modular code base where I'm a new developer? I have this basu client in front of me, but I know that I have a hard requirement for GRPC I slot this thing out because you know, I have a very clean interface between JSON RPC and my execution And then I'm able to replace that right. I have a very clean you know line between For example the EVM and this potentially, you know, I use engine API here But I think that this is frankly could become a lot bigger to mean any external connection to the EVM Where I have a roll-up and I just want to plug like we can already expose the engine API in a way today Since since proof of stake has opened up this kind of big Rethinking of how these clients actually build blocks Execute them and then move on with their day Why don't we just open this up so that any like any consensus mechanism that happens in theory outside of basu land can work Right away with this engine API, which is already designed to interact directly with the EVM directly with state storage You know not necessarily with networking, but basically it's a it's a big line in how do we turn this into a much bigger notion, right? so I think that the Client that we're looking to build serves all of these use cases because it's designed to have Exposure to what you need and then you can drop in the rest and it's an open source product Right if I want to tweak basu to serve my certain needs Or if I want to build a plug-in that extends the engine API or extends the JSON RPC I can you know As we move to a modular architecture, I think that that's what we want to see right is Opening these connection points up so that folks can come in and design exactly what they need and drop everything else Not because it's you know one because we want to move to a more sustainable code base But two because I frankly think that we're moving towards a multi-chain world that will require You know some or all of these components and we want to be able to serve that because it's the best way to bring in more Developers to basu it's the best way to bring more developers into the Ethereum and Ethereum adjacent ecosystem And you know it's the best way to build the best execution client we can Let me take a breath and see what we have here Any questions I think modularity is the next big thing yeah, it's you know, it's like That like cacti the cactus team is now becoming the cacti team and they're building all these interoperability components But imagine if you got a lot of that for free by just exposing the low-level API's that you needed to interact with the blockchain state And the blockchain virtual machine Not that I don't like those projects. I just think that we can go bare metal on this one and avoid a lot of that stuff by opening up these kind of four layers consensus interface Execution and then you know the rest is already essentially build your own choose your own adventure because basu has plugable storage to a degree We have several options and you can write your own plugins to do whatever storage you want anyway We have relatively modular networking and we have a kind of plug-in interface which I haven't discussed much because I Frankly think it needs kind of a revamp or it needs to be opened up a little bit more or even created into the thing that I'm trying to describe here But you can already extend basu to do most of what you want to do through this plug-in interface But yeah, it's you know Legos Dano kept saying talking about Legos and it's this is really just a bunch of components and you only need some to do what you need to do and My goal is to make basu kind of a prolific piece of infrastructure software and to do that I think that we want to accomplish something that looks a lot like this And then again back to the privacy thing. I think that you know once we Solve the problem I made on the previous slide We get this for free Plugable consensus plugable networking and then to Sarah as an optional component of the basu code base not going away just moving I think we reserve couple of slides. Oh, one more. It's like a animation slide. I need to get rid of this crap But so why again, why why am I doing all the stuff that I just where why is that like the why do we want to move basu towards this kind of new mission statement and It's right here, right? We want to enable network participation I don't know what that looks like in two years and I don't really want to know I just want the client to be agnostic enough to serve The network like the users of the infrastructure to participate in whatever network they want to whether that's again Ethereum something different something yet to be created I think that all the building blocks are relatively the same and also we want basu to still be relevant in five ten years and if Things shifts away from this kind of vision if we have a modular lean execution client we will be able to adapt to the changing landscape regardless and Hopefully our users will not have to Change away from basu or to throw away what they've already worked hard on because the client will evolve kind of with the landscape So again to read what I've written up here. It's basu enables network participation for institutions It supports Ethereum post merge private networks mining networks And we aim to evolve for a multi-chain EVM compatible world around, you know EVM compatible virtual machines roll-ups hybrid networks sidechains more all that good stuff with a familiar license Familiar programming language Institutional grade features and hopefully keeping our nodes very low overhead as we move to a kind of lightweight approach to stake ether to do Interactions with any blockchain networks that run on similar Tech and we want to be the best and most flexible infrastructure for people looking to participate in blockchain networks That was that that was a peach. Yeah, that's the pitch This is kind of a boilerplate why do you want to do or why do you want to run on public networks? So I mean another of the big reasons that you know, Francesco and I are here today is not to espouse basu It's mostly to talk about why do you want to participate as an enterprise in public networks? This doesn't just mean Ethereum. I'm talking everything like we want to see enterprise We think enterprise will converge on kind of a mainnet focus within the future anyway So getting your toes wet now is definitely valuable And we think that basu is a great means to do that and it's rewarding you can get literally paid to do this You know, as I mentioned, there's a capital investment in actually staking But the staking rewards will likely be around 12% post merge, which is pretty great That number will go down over time However, it's slated to stay around 12% post merge for a little while as more validators come online We'll see that come down But it is a literally rewarding prospect for enterprises to learn how to run node infrastructure on public networks And that means getting the right approvals to do so with your organization's infosec teams Learning how to set up the infrastructure in a way that is highly available and fault tolerant and all that other good stuff And making sure that you have like everything kind of squared away so that when again When these things come to disrupt what your business does you don't have to be reactive You can be a little bit proactive Because I believe that a lot of the public network infrastructure will Disrupt many enterprises, of course not all But I also believe that that enterprises can feel safe and secure in participating in public networks for a number of reasons However, I'm working with Hyperledger to provide a bunch of different workshops on what that actually means So I know Antoine one of the basu contributors has run a great recently a great workshop on how to Operate and extend hyperledger basu Extend as I mentioned There's that plug-in interface where you can change the way that the client operates And operate is self-explanatory. You have to actually know how to run it. Um, but there are more details I think the next workshop is october 5th So check out on hyperledger and they will the wiki has the dates and I will be hosting a workshop on enterprises running public network infrastructure And we may even stake some fake eith, so that'll be fine That would cool. Yeah, we also have a bunch of like developer communicals also on the protocol side from consensus There might be worth to check out And the contributor call also on the basu side might be also cool Yeah, I think that the rest is just questions. Oh, actually, no, that's right. You're princess go Oh, no, no, that's the boring stuff But I mean, I don't know how boring is that but basically like super long story short is I mean, I don't know everybody saw the vitalic paper on on the verge You know merge verge search all all those great namings But literally it's what what matt is mentioning the post merge. Nothing is is finished It's it's literally like a process and you know sharding is the next big Etab and and yeah, and I really also recommend and free also to to reach out for for the slides Like a couple of links always on the on the merge research and and the specific also resources On on on podcast and it's exactly like explaining all this paper Because I think it's it's full of great information on on the next progression and roadmap of of east Yeah, this is like something super interesting that we find out on on reddit visualization But it's a mix on on how how now If you will look like in 2025, I think for digesting this I talk maybe like two weeks But for what I'm understanding is literally like a mix of those four for Top top and left. I don't know sidechain layer ones. It's quite interesting I don't know Matt if you know more but around those volitions and Validium's and obviously roll-ups we know it's ready But I don't know if you if you know more a little bit on yeah, it boils down a lot to Data availability and proofs So there's some complex cryptography in Through volitions and validium's improving how certain data interacts and exists within the network Again, it takes more than the three minutes. We have left to explain volitions But I think that the key the key pieces as francesca mentioned is that like We are going to continue to see side chains in l ones We're going to continue to see ethereum execution layer consensus layer and shards And then focus on roll-ups here And and you know, what does this all look like is basically how do we provide data to users cheaply? How do we continue to scale? How do we serve a multi-chain world? I think that the ethereum roadmap has actually been smart in evolving to Not presume that it's the only l one that will ever exist that has smart contracts So I think that making all these things first-class citizens is kind of like 2025 like this long-term vision for ethereum is how do we Combine everything together as opposed to trying to segment the network And I think that that's You know done through a bunch of these different bridges that have been proven to be a little air prone up to this point But working on that and using zero knowledge proofs and other proof systems To basically tie everything together and use ethereum as this kind of settlement layer for this new vision, right Is is taking in all of the different blue boxes Which are doing variety of proofs a variety of mathematical calculations to ensure that the data either exists Is correct or hasn't been tampered with and then it sticks them on that execution layer in the state storage And then it communicates out to the rest of the network via so this pink box Cool any questions so far We have like a minute, but 50 seconds But I think yeah, we'll put some learning Resources that might be cool. I think team also speaking visually today for tomorrow tomorrow. Yeah tomorrow More on the merge tomorrow with some folks from the ethereum foundation speaking Yeah, we also did a bunch of interviews that have connect on on the merge and the next next steps with I think just in drake and team that was really helpful Any questions so far? I know there were a lot of link information I think this is something that you know, it's We can I can send it to you and uh, yeah or attach we can send directly I think hyperledger will also send them out, but we we can send these directly to you Yes Any other questions so far? We're ready to to go. I think we're literally the last talk Cool. Awesome. Thank you so much everybody