Holesky madness, Base speeds up and more - The Daily Gwei Refuel #829 - Ethereum Updates

Transcript

hello everyone welcome to another episode of Del refu where up the latest news in eum ecosystem I'm your host and thisday 28th of February 2025 all right everyone let's get into it so some big news out of the ethereum foundation over the last couple of days so you probably would have seen this on Twitter already this is something that a lot of people have been talking about for the last couple of months but a from the the foundation so she's the executive director there has announced that she's actually transitioning from being the executive director into a new role as president of the etherum Foundation now there is a statement you can read I'll link it in the blog post uh sorry I'll link it in the YouTube description below uh for you to check out but I think the TDR of this is that a is moving from I I

should say is moving from the executive director position to the president position and it's a different set of Duties I think people were confused about what a president actually does and what the executive director actually does a lot of people don't seem to know what these what defines these roles it broadly speaking I would say that a president has more to do with the bureaucracy inter internally like basically the day-to-day kind of admin stuff of the internal organization whereas the executive director is more like someone who sets the overall vision and Mission uh for the entire I guess foundation and coordinates around that and he's is's a public facing figure as well um or I mean they can choose to be public or not but in a lot of time times they are a public facing figure they're

basically the face of the foundation there at least that's my understanding and it is different it can vary uh from Foundation to Foundation it's not like there's a strict rule in place that says you have to be this or have to be that but I think that this basically sends the I guess message to to the ecosystem that the EF is doing a big shakeup of its leadership I mean there has been other announcements that have been made over the last couple of months here but there isn't a new executive director yet so no one's been announced for that position yet I think at this point in time I would say that the odds of Danny Ryan becoming the new executive director are quite low if not zero just because I feel like we would have heard about it by now but at the same time I was

thinking about it more myself and about where Danny Ryan would be best fit in the ecosystem because I mean's he's a friend of mine I've known him for for a long time i' I've followed his work for a very long time and I was just thinking the other day that I I feel like a man of his talent so to speak would probably have a better and more I get a bigger impact uh somewhere else maybe not at the theum foundation uh depending on he want what he wants to do himself as well uh you know I I think that his talents might be used uh in a better way somewhere else but in terms of who I can imagine stepping into the executive director position at the eum foundation uh I don't know I've thought my head like there are good candidates out there

I believe but I'm not sure maybe they promote from within I don't know if that's something that they've uh they wanted to they want to do I don't know if that's something that the community would like but maybe they promote from within uh which they have done for the other leadership positions or maybe they go out and find someone that maybe isn't even in crypto maybe they go and find someone who is really hungry wants to get involved with the ecosystem uh has a probably a a nice understanding of crypto and a decent understanding of it but comes with fresh new ideas from some other world maybe from like the AI world or from just the tech World in general I don't know we'll have to see I've got no honestly I've got no additional information to that this is all just me speculating so we'll have to see who

ends up becoming the new executive director of the EF I'm sure the announcement is coming soon I I I I doubt they're going to wait very long from when this announcement was made which was what two days ago now uh yeah so this was made 2 days ago we maybe even get something next week we'll have to see I'm not I don't know like I don't have any advanced knowledge of of these sorts of things as you guys know I don't work for the ethereum foundation it's funny cuz a lot of people think I work for the ethereum foundation I don't I never have as you guys know I'm an independent guy um you know I like what I do within the ecosystem but hey we'll have to see how that all shakes out there all right so another big piece of news from the last few days was that the

heski test net went through its Petra upgrade and unfortunately it didn't go as planned and you know the funny thing is is is that it didn't go it didn't go as planned not because of any bugs within like the pectra eips themselves but because of a silly bug that affected the majority of the clients which tldd basically meant that the chain ended up not F from what I know it didn't finalize on a bad chain but what what ended up happening was that the uh bug caused the chain split and the the minority chain was actually the valid chain um and that meant that the uh uh validators that were on the the I guess like majority chain that was not the chain that was valid by view of the rules of the network essentially so they

were on the I guess the bug chain uh which has resulted in a bunch of interesting outcomes within the uh the test net here so as I said uh this wasn't an issue with pectra itself so I don't think this is actually going to delay the sepolia fork I don't think it's going to delay the main net Fork maybe it does but like a week or two but I don't see it delaying anything that that much because of the fact that as I said it wasn't an issue with any of the pectra eips it was an issue with the deposit contract uh not being included properly across the clients here the deposit contract address which is funny because it's like the edgiest of edge cases I was actually reading about this and and and someone said that the reason why this wasn't caught on dev Nets is I

can't remember the exact reason but it's because it doesn't actually apply to Dev Nets so the funny thing was is that like we couldn't even test for it on dev Nets and then we test it we did it on a test net and then this bug came up and it was such a simple thing that is just very easy to miss but it did unfortunately lead to some pretty drastic consequences and pretty dire consequences for the whole eski test net which ended up being revived uh so there was like Mass slashing events to basically get the validators uh to on that kind of majority chain to essentially slash them off that because they're on the bad chain right and and get them to come over to the minority chain kind of re-enter as part of that there and get holeski basically uh live again and

finalizing again there but it has been extremely messy Tim biker has a great thread summarizing all of this if you want to check it out I'll link it in the YouTube description below for you but also on top of this I think that there was a bit of comments about these people saying you know this is really bad right this is uh what if this happened on Main net this would be catastrophic and I kind of agree with that to an extent is that like if it happened on mainnet it would be catastrophic but as far as I know this particular bug couldn't happen on mainnet I can't remember the exact reason I've read so much about this and it's just all jumbled in my head right now but I'm going to link these threads for you guys to to read cuz it's got more information here but it beg it does

beg the question of like if there was a chain breaking bug that happened on on mainnet where essentially the majority is on the wrong chain and the minorities on the correct chain uh how do we deal with that right because no matter especially if it gets finalized like how do we deal with that because no matter which way you look at it someone's going to get hurt someone's going to get wrecked and then uh through no fault of their own because if it's the I guess developers fault because they introduced a bug or something like that then uh the community would have to come together and socially coordinate around this so what this heski kind of um incident has done is basically being a nice war game for all the core developers and researchers to see how the network reacts to these sorts of things to see

uh how they can actually go about incident response if this was to happen on Main net and basically tightening things around uh testing for these really just weird edge cases because it's always the edge cases that get you because you can test for so many things but like I remember there was um there's this thing in like uh when I was at in working in cyber security they always said you know there's the known knowns there's the known unknowns and then there's the unknown unknowns so essentially you don't know what you don't know right so I think this bug was essentially an unknown unknown because no one had really thought of it no one had really considered it at least from what I saw and now that it's been I guess like now that it's happened this is something that they'll obviously consider going forward and Phil put out

a good tweet here uh uh in about this he works on loadstar as part of chain safe Lo load Stars a contend layer client he he said you know we're not trying to save h because this is something we can uh replicate on mayet as disaster mitigation um everything that they're doing for heski is for science we haven't been able to test a massive slashing at this scale nor revive a chain from multiple invalid SLV valid Forks some of us didn't even know how some of our clients will handle the chaos this exercise has and will allow us to create more robust software for ethereum expect new apis flags and maybe even some spec changes that will benefit from the chaos which I think is really cool because as Phil said here this is not something that you want to war game

on Main net because of the fact that there is actual consequences on a test net it's different like no one cares I mean there people care but like you're not losing money on a test net whereas on Main net there is vast consequences monetary Financial consequences for for stuff like this and I I think that those consequences especially if it's something as as potentially big as this where you have to do like Mass slashing to get the chain back online and certain people end up losing money or you you try to do some kind of socially coordinated thing where you basically I'm just thinking out loud here but you could technically slash everyone and then mint eth again and give that eth to those people that were on the wrong Fork through no fault of their own in order to make them whole again but you see how

messy this gets and how how quickly it gets very messy like that that would be quite quite an insane thing to do and I'm just saying it because it's an option right there's always a million different options that you can go down and different paths you can go down but we don't want to be invoking that so obviously we want to uh with core development and research we want to be moving as fast as we can but I've said this plenty of times on the refuel there's a there's there's basically a limit to that because you have to consider the security implications here you have to consider the stability implications of the network especially a network like ethereum which is home to so much and such a diversified set of use cases and and and ecosystem participants and stakeholders it's just not something that we can risk happening

on Main net that's why we do so much testing so many Dev Nets we do the test Nets first then we go to main Nets uh but it also speaks to what I I I think I've been I've been saying on the refu the last couple of months and what the core devs and researchers have been talking about a lot is separating out things so essentially because we want to move fast in certain areas of the protocol for example we want to move really fast with scaling up blobs right we want to do pias we want to have as many blobs as possible on the network so let's like separate that out from the other stuff let's separate that out from epbs and fossil and the verle tree stuff and other parts of the road map right and that's what it seems like they they

they're trying to do at this stage it really does seem like they're trying to to separate things out so that the user-facing stuff um gets priority the the stuff that really impacts the network get in terms of uh for for its users uh gets priority which is something like blobs and then other things that also have impacts on the network and and users but uh I guess like maybe secondary to scale such as fossil such as epbs and and the other things that I mentioned uh they would come later and they would be uh considered less critical than than scaling so it's all part of that conversation there but that's basically the guess summary of what happened with heski as I said I don't foresee this uh resulting in any kind of like long delays for uh uh Petra or anything like that maybe there's like a one to two

week delay or something but I think at this point in time it doesn't really matter because as I said like the core devs have already moved onto essentially um you know trying to finalize the faka spec so that we can get pias and and eof delivered as well as fast as possible they're thinking about how to do blob scaling faster and all that sorts of stuff so this is something that obviously Petra we want to have on the network but it's not like it's something uh that is is is you know very very urgent right now Petra does include a blob count increase but it's not something that's absolutely critical orse everything's going to go to no especially with the market the way it is right it's very bearish right now um it seems like there's a little bit of leeway here in terms of uh timelines

there not an excuse to slow down mind you but if if doing a one or two we delay is needed to make sure that we're doing it the right way then I think that we should all we should be all for that all right just another quick thing I wanted to highlight here is as you guys know that after Petra goes live there is a big appetite to increase the L1 gas limit as much as we can uh right now it's at 36 million uh Ben Adams here from the nether mine team wants to increase the heski gas limit uh to 60 million after Petra goes live on that Network obviously once the network stable again from the the um I guess Reviving it's going through right now this uh will hopefully happen there but the logic is basically you know do it on the test Nets early and then uh do it on

mayet after Petra goes live and essentially get us up to 100 million if we can as well because I think 60 million is a I mean it's a conservative Target you know we want to go higher than that imagine if we can get to 100 million by end of this year or by q1 next year that would be really really cool just keep scaling up the L1 alongside the L2 with blobs and make sure that we can uh stay obviously the ethereum ecosystem stays competitive on the scale front and make sure that Builders uh and users know that ethereum is going to keep scaling into the the future there all right just wanted to highlight this tweet from Greg here so essentially I was speaking before about the ethereum foundation and about how everyone wanted you know Danny Ryan to be the head of

the EF and obviously Danny Ryan is awesome he's great but he's not the only awesome and great person in ethereum and Greg actually highlights a bunch of people here it's not an exhaustive list but he highlights a bunch of people here across the different areas of ethereum and uh most of these people if not all of them I think work within the ethereum foundation but you have people like uh um like joshia Josh Rudolph who's doing a lot of things with Le to inability I've been highlighting his work on the refuel so he's doing that and he's acting as like the Danny Ryan the leader the coordinator of that effort then you have devops and validators which is paraos who have also highlighted a lot on the refuel does a lot of really great work on that front uh current protocol Tim biker you guys know he's like the

main coordinator of the all core devs on the solidity side here you have Alex uh who's been around for a very long time actually and he's been doing a lot of great work for uh solidity future protocol stuff you've got Justin Drake working on things like base rollups obviously working on issuance stuff as well native rups uh even L2 interoperability right lots of great stuff there uh funding of the allord developers through things like the protocol Guild Trent veps works on that I mean I've talked about the protocol Guild countless times uh and then Moon maath and Beyond with vitalic I mean yeah balic just across like everything on the core protocol in terms of uh research and even outside of that uh and there's also other a lot of other people that are focusing on different things within the ethereum foundation too that Greg uh talks about and other people

reply to his tweet with so I'll just link this tweet in the YouTube description below but my overall point here is that and and this is what Greg was trying to say in his tweet as well you know ethereum is is too big for just one leader we've got many many different leaders here and that's actually incredibly healthy we don't just want one leader as part of one kind of entity dictating what what's going on with ethereum we want many leaders as part of many different initiatives and entities uh doing things within the ethereum ecosystem and I think we have that and I think that's going to keep growing over time because you do really have the opportunity to do whatever you want in ethereum no one's telling you what you can and can't do no one's stopping you it is a truly decentralized ecosystem so

if you want to start being the uh you know the lead on some new effort you can you can go do that get some people around you get drum up some support for it even possibly get funding from things like the ethereum foundation and you can go uh and do that there all right so we have a postmortem on that bybit hack from the other day so end ended up being that it wasn't bybit themselves that were exploited it was actually the safe multisig front end that was exploited so the tldr is that the Lazarus group so the North Korean AP or advanced persistent threat group were able to modify the official website of safe to inject some uh you know malicious code that targeted by bit

actually so it wasn't a kind of like there's different terms for this but it wasn't a them casting a wide net here it was literally like a spear fishing thing where they're like okay we're going to Target specifically by bit we know they use the the safe wallet interface so we're going to we're going to change it uh uh uh by kind of exploiting it there changing it and then that's how they were able to drain by bits funs here now this is obviously quite scary and I do want to preface this by saying that nothing's wrong with the safe smart contracts so the multisig safe multi smart contracts as far as I know are completely fine there's no known exploits in them no nothing's been exploited there but this is like a front end attack right and I've talked a lot in the past about front ends and how

they are a central point of failure for a lot of reasons but I think there's there's multiple angles you can come at this from one is that it's scary because like a lot of people use safe and if this was a general exploit on the safe front end it could have led to a lot of losses from a lot of different people but I think that the reason why the it was targeted at by bit was because you can imagine that maybe someone moving a small amount of money around was to notice this right on on the front end and they would alert the safet and then it would get patched pretty quickly whereas if you only Target by bit essentially what you're doing is making sure that the the the target you're going after is the only one that can trigger this and also you're going after

a target for specific reason in this case because you know they have $1.5 billion worth of eth that you can steal from them right so that that's that's obviously um one aspect to it the other aspect is that like if I don't know what buits internal security practices look like I will commend them a lot on their incident response so their incident response should actually be studied at you know by by by people in different kind of universities for how well it how how good it was and how well it was conducted there but I think that there's there's a couple of things here so I as I said I don't know what by bits internal security procedures look like but I I think that responsibility still lies with bybit here over safe yes of course the safe team should have been better at securing their front end like

there's obviously blame to be laid there but if you're moving $1.5 billion worth of money around whether it's ether or whatever you think that there'd be a much more stringent and lengthy process to do that that and You' think that they wouldn't be using a thirdparty front end to do this as far as I know you can actually run the safe front end locally or you can interact with the contracts directly yourself so for an organization that is managing other people's money that has the money to pay the top security people the top um operations people the fact that they were able to get exploited by this or the fact they able to get essentially you know spear fished by this is speaks to the fact that they don't have the controls in

place that they should have internally so as I said I still think that the blame pretty much lies almost entirely on on bybit for this because their existing processes shouldn't be like this at least from from from the outside looking in they should have much more stringent processes on this and I think that the other exchanges do like for example coinbase as far as owner has never been hacked ever and they've been around for a very long time and they have more customers than anyone else basically or at least maybe more maybe not more customers cuz binance has more but binance I think only got hacked once in the past um and I don't know if I can't remember what the hack was exactly I don't know if I don't think it was on their Cold Storage it was on some hot wallets but basically like these big

exchanges they they they take security extremely seriously especially coinbase coinbase's security is um would be Top Notch here but but I think when you're operating a centralized exchange you essentially need to always default to as part of your security apparatus you need to default to okay I'm going to get targeted by Nation States because you are right like you're a massive Honeypot for nation states and they know that they can steal this crypto and then wash it in a million different ways and then once it's gone it's gone there's not really many ways to recover it you can recover some here and there but for something like eth or BTC and no one's going to Blacklist these addresses except the uh centralized exchanges you're not going to be able to Blacklist it on chain right and you can do a lot of different things on chain with these

assets and then you can as I said like wash them through different means and launder them through different means so I think as a exchange you have to have that at the top of your list there so I would say that I I I still personally put the responsibility on buy bit but as I said they had a killer incident response here and they actually made everyone whole so so they've done a great job there as I said I commend them on this but it still doesn't take away from the fact that it's a huge obviously lesson for them to be much more strict with their internal security posture and it's also a lesson to um everyone in crypto that just because you're using a third party uh front end doesn't mean sorry a trusted front end doesn't mean that it is secure against the tax

because as I said this could have been this could happen to anyone this could have been a general exploit and imagine if you were using a a safe multi here and you went to the website and you're like okay well I'm going to do a transaction from my wallet everything looks good uh I'm you know I'm going to initiate this and then your funds were drained think you're thinking you actually are on the legit website and you're thinking everything's legit and then you lose your money like that so I think it's it's it speaks to the fact that we need more decentralized front ends for sure that one that can't be changed like immutable front ends decentralized immutable front ends we need um easier to run local front ends so being able to run the uh safe front end locally should be much easier and

much more accessible for people and we also need to understand as an industry as I said that that these these nation state actors are targeting the honeypots like they're targeting everyone so you need to be much more I guess security aware if you're doing things like self- custody and there's always obviously a risk of custody your assets with with centralized exchanges as was evidenced by it here but if you're doing that you need to understand those risks and you need to if you're going to do it you you you you should only do it with reputable exchanges and and I know that it's sometimes hard to know what what's reputable and what's not but I think at this point it's pretty safe to say that coinbase is extremely reputable in terms of I guess like using and storing your funds there your biggest risk with

coinbase I would say is the fact that they can just arbitrarily freeze your account and it can take a while to get it back for whatever reason I I would say that's the biggest risk the the risk of it getting hacked or drained or like that is is very small there's always a risk there of that but it's very small I would say binance is quite legit too I I I think I've never heard of um anyone really um uh losing funds in a in a binance export or anything like that unless they were somehow fished by giving their account up or something like that so uh but but binance is also I mean you guys know my opinion on binance right historically they've been quite dodgy so I wouldn't trust my funds there but if you're talking about like if you had to store your funds on an

exchange yeah I would say like you know coinbase Kraken binance maybe I mean I I don't know much much others and you also have to be aware that a lot of the other services that op offer crypto custody and trading they actually use third parties like coinbase to custody so you would want to read what who they actually use for custody are they doing it themselves or they're using a third party uh and that's just custody with third parties obviously I still recommend self- custody above all of that but I understand that a lot of people aren't comfortable with that I understand that something like this makes people even more uncomfortable the fact that a a multisig that they thought was extremely secure can be compromised like this as I said it wasn't the contracts the smart contracts themselves that were compromised it was the front end but hey

99% of people are using their safe multisig front end they're not using their own front end they're not running it locally I'll be I'll be the first to admit that I don't run it locally either I should honestly but I I actually didn't even know that you could I I I I honestly thought that you could and I think someone in the daway Discord Channel linked it to me saying that you could but it was a bit of a involved process there but it just needs to be super easy so you can imagine you know it becoming just like a very easy thing that you can download locally and then run it locally on your on your own machine uh if few clicks and that's that's all it really takes but yeah I I I think that when it comes to these kind of products it's also against the best

interest of the product itself because for example the front end is where these products commercialize so if they let everyone run their front end locally they can't commercialize it as much and it becomes a revenue drain on them rather than a revenue generator so I understand that as well but hey if you want to uh have everyone trusting your front end you better make sure that things locked down really tight and secured really tight because this is this is a failure on safe's behalf as well that they didn't T they didn't lock down their front end to the point where it couldn't this couldn't happen um so yeah that's the that's the kind of I guess like te there on all of that you can go read the post that safe put put out I'll link it in the YouTube description below uh for you to do so uh

there's more details in that all right so just something I wanted to highlight here from the uh op Labs team so they introduced a feature a while ago into in in in in a beta fashion which was the ability to set a custom gas token if you were an OP stack chain so I I think that this feature was not needed to begin with but they introduced it because they wanted to obviously add more flexibility to uh op stack chains but they've now deprecated this feature and I think this is a really good decision because in all honesty the gas sticker is eighth like and it should just be eighth there is abstractions you can do it like the interface and wallet level where essentially you say okay well you can

pay for your gas fees in stable coins and then in the background it gets converted to eth gets paid in eth on optimism or base or arbitrum or whatever it is and then it gets paid down as eth to layer 1 ethereum as well I think that just makes it easier from an accounting perspective obviously ether is incredibly liquid so it's it's no problems there with liquidity uh and it makes it simpler for users as well so and and it reinforces E's use as a monetary kind of uh uh unit Within the ethereum economy outside of ethereum L1 right in the ethereum l2s and l3s or whatever what have you there so I'm glad that the op stack has done this and I think this should be the standard across all the l2s they should just use eth and then you can abstract it away if you

need to at the interface layer you can do gas sponsership you can do uh pay masters stuff like that that's fine but under the hood it should always be eth just for as I said for the reasons I just outlined um and also just to reinforce eth as the money within the ethereum economy all right so Bas has a pretty major upgrade coming soon that's going to reduce the effective block time from 2 seconds down to 200 milliseconds so it's live on test net right now and coming to main net in Q2 and it's called flash blocks so I believe this is a product from flash Bots it enables Subs uh sub blocks issued by the block Builder to be streamed to nodes every 200 milliseconds allowing for early confirmation times with Native revert protection and you

can learn more about it in this GitHub repo I'll link it in the YouTube description below uh for you to do so there uh but this is really cool I think for a number of different reasons arbitrum one is already at this so it's great to see Bas um getting there and and I guess like they're using a different product to what arbitrum is using here but as I've said before I think 1 second or below is what you want to be targeting but anything kind of uh sorry I should say 2 seconds and below is what you want to be targeting but anything under 1 seconds is just gravy I think for for most end users they're going to think well you know if it takes a second for my transaction to confirm that's fine like I don't need it to confirm in 200 million milliseconds but

if you're confirming it in in in 200 milliseconds it just once again steps up that user experience to the point of like it feels basically instant and yes you're not going to really notice the difference between 200 milliseconds and 1 second if unless you're like measuring it yourself but it I guess like gives that feel to to the chain being faster because it is you know 800 milliseconds faster than between 1 second and 200 millisecond CR but it also means that it's not just for end users it's also for like all the Bots operating on Network they now have a faster way to get their transactions included they can do more efficient Arbitrage and stuff like that which gets P gets like um uh not not paid down to the user but it kind of gets uh trickled down to the

user in terms of the user experience with different liquidity pools and different parts of Defi and stuff like that and the whole chain just becomes more efficient here so I'm just really happy to see this I'm really happy to see that uh base uh is is is doing this because I think that the standard needs to be like 1 second uh or or below 2 seconds is I mean it's okay but it's probably too much if we can set the standard to 1 second or below that would be great and then there's also other l2s that aren't live yet that are working on getting it down know as much as possible like Mega E for example and i' I've showed a demo of what this looks like they want to get it down to basically 10 millisecond block times I think or even less than that I think 1 millisecond

they were trying to Target here in order to basically make a fully onchain game viable where essentially you won't be feeling the latency of a transaction like everything can be a transaction but you won't be feeling it in the block times because you can imagine if everything is a transaction and and transaction times or block times are 1 second then it's going to be like because you do feel that in a video game right like there's um there's a reason why ping is measured in milliseconds and and if you have like for example if you playing like an FPS game and playing multiplayer honestly ideally you want like 20 Ms 20 20 ping essentially you want you want things happening very very quickly very very Snappy um but then if goes above that you you actually feel it

like you you feel it quite early on as well and then if it's like 1 second you are definitely feeling that because every time you click your mouse button to fire your weapon you've got to wait one second essentially for that to action to happen and then it just ruins the whole experience so they're targeting things like that those kinds of use cases but for defi for like sending you know stable coins to people sending eth to people that sort of stuff like it doesn't need that right definitely doesn't need that uh and one second or less is totally fine for those sorts of things um and it's it's obviously still a huge step up above uh tradire there but anyway you can go check all this out for yourself Link in the yoube description below for you to do so all right last couple of things

here so grow the grow the P now has a new application Level metric section of their website so these are tools for users and Builders to compare metrics across apps and see the top gainers and losers search your favorite apps and filter by chain and there's detailed metrics and charts when you click into applications so you can go to grow p.x yz/ application and see this for yourself um but I'll also link it in the YouTube description below I think this is great because I think there needs to be more of a focus on applications honestly we focused a lot on infrastructure uh over the you know a long time in crypto we focused a lot on um certain applications like defi but it's bigger than that like obviously defi is is probably the biggest use case we have within crypto and you can actually see that in the metric here but

um you can actually uh I believe gr theie wants to be able to track like every type of application here and then you can go in here you you can see things like if I was to click on into unisoft for example you can see things like transaction count you can see uh where the um the contracts uh uh living like on base and arbitr and things like that over different time frames and where most of the activity is happening so on and so forth uh in terms of transaction count um and and and more like you can scroll down and see uh similar applications as well to Unis swap there's a lot of stuff going on here more stuff's going to be added just figet it was worth highlighting for you guys so you can go check that out there and last up here l2b has introduced

something called da throughput on their website so essentially you can see the throughput of different uh da da layers or data availability layers on the l2b website now now there's only three that they're tracking right now it's Celestia ethereum with its blobs and Avil which is a DA layer as well there and you can see here that the there's capacity used vers versus it's Max Capacity and I actually think this is a pretty uh interesting thing to pay attention to because Celestia is a uh is a chain that's a lot more centralized than ethereum they've taken those trade-offs because they want to scale up faster so they have like a Max Capacity of 1.3 megabits per second and they're actually going to keep scaling that up as much as they can um and ethereum blobs right now has a max capacity of 0.03 megabits per

second but that capacity is pretty much all used right now you can see it's 100% whereas with Celestia only 23% has been has been used over the last day this is just measuring the last day the average of the last day and most of that has been eclipse so you can see here 98% of what was posed to Celestia was Eclipse as opposed to 32% on ethereum uh which is BAS which is the largest poster so not only does ethereum blobs have much more of a diversity in in usage it's also at capacity yes because it's more limited but the thing is is that I I actually like that we don't you know basically frontload the the uh the space too much because if you frontload it so much and then it doesn't get filled for a very long time you're essentially

subsidizing something for nothing right and and and it creates just too much space so I like that there's like a staggered approach here from ethereum I I do think that obviously with with with us adding blobs we should be adding blobs more aggressively but that's only because I think that that the blob usage is just going to keep going up it's going to keep going up massively from here um on on ethereum and obviously like it's way ethereum's Max Capacity is way less than um than Celestia's right now and I would love it if chains like Eclipse could settle to ethereum blobs instead of celestial because it keeps it within the ethereum family here and they get to become a full roll up but they can't right now because even though they they're not near Max Capacity on Celestia their past day average is 0.3

megabits per second ethereum's past day average throughput is 0.03 megabits per second so Celestia is still doing 10 times more um even though the capacity they're not at capacity and that's because of the fact that uh Eclipse post a lot of blobs right uh but I'd love I'd love for that or post a lot of data I should say I'd love for them to post that data to ethereum but it's on us to keep scaling blobs up here uh and make sure that we can have that capacity there for these other uh these other chains but I think on that note that's going to be it for today so thank you everyone for listening and watching be sure to subscribe to the channel if you haven't yet give it a thumbs up newsletter join the Discord Channel and I'll catch you all on Monday thanks

everyone