Ethereum Cat Herders Beacon chain proposals, 19 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: PEEPanEIP#80: Lodestar & The Merge with Gajinder Singh

Description

Topics covered
----------------------------
1:24 - Guest introduction
3:30 - Project and team introduction
3:57 - What is the Merge?
5:00 - The Merge in memes
6:05 - Big value adds of the Merge?
7:38 - Wen merge?
7:57 - Lodestar
9:02 - Production performant
9:28 - Merge ready
10:20 - Features ready
12:15 - MEV boosted
13:10 - Optimistic Sync
14:35 - Lightclients + Merge
15:47 - A Lightclient wallet in a browser demo
17:31 - Dream on
18:11 - Client diversity
18:56 - Zero configuration
19:56 - Open for contributions
20:41 - End of presentation
21:33 - What’s the main motivation behind adding an Ethereum CL client?
23:22 - Significance of MEV boost
27:29 - Main user base
28:44 - Experience of participation in devnets and public testnets
31:24 - Why is there a specific need for apps/webapps to be able to embed a node using typescript?
34:34 - Why embedding?
37:18 - Why not use Infura to run your app post merge
38:04 - Which is the best EL combination
Optimistic sync
42:00 - Client's diversity - How will Lodestar increase the current network share?
44:29 - Message for potential users and the community

Resources:
-----------------
Slides - https://docs.google.com/presentation/d/1jJpTuQJx9sJ5jo5elLocSaHp1unn8Y9XV9th5zvp5dA

TheMerge playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqoLxXqZqT4hcYhoHoP6w12

KnowYourClient - https://www.youtube.com/playlist?list=PL4cwHXAawZxoruie1hmYWJfiakpYivXft

PEEPanEIP playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F

Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herders/PM/projects/2

Follow at Twitter
-----------------------------------------------
Gajinder Singh @Gajpower | Pooja Ranjan @poojaranjan19 | William Schwab @wschwab_

Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herde...

Contact Ethereum Cat Herders
---------------------------------------------------
Discord: https://discord.io/ethereumcatherders
Twitter: https://twitter.com/EthCatHerders
Medium: https://medium.com/ethereum-cat-herders
GitHub: https://github.com/ethereum-cat-herde...
Email: support@ethereumcatherders.com
Website: https://www.ethereumcatherders.com/

A

With the merge upgrade, ethereum is changing the consensus mechanism from proof of work to proof of stake, and this is just the beginning of a new era in blockchain technology opening doors for many new users to join the network. We hope this know your client series will help enthusiasts to take a step forward and turn into a contributor welcome to p paneer episode 80..

A

I am pooja rantan with william shaw from the ethereum cat herders and we are joined by talented engineers of lodestar, gajinder singh and phil nigu load star is a relatively new typescript implementation of ethereum consensus layer, client joining the network approximately a year after the launch of beacon chain. The project is maintained by the chainsaw systems. We will get to learn more about the client, the merge, preparation and utility apps made and used by load star in this episode with kitender.

A

Thank you for accepting invite.

B

Thanks puja for having me and very excited to be here to present lord star to represent lord star and present our merge preparedness on peep and eip.

A

um Maybe if we can get a brief introduction of yours about the professional background or how you get into ethereum, because this is the first time you are here on our show, it will be interesting for our listeners to know you more.

B

Right so uh I primarily come from a web to era, and I run my own consultancy, but uh when the beacon chain was launched, I I used to sort of you know, uh get into discord of lighthouse and do technical discussions or they're over with the team members over there and one of the developers over there suggested. Okay, you know what languages you are proficient at and I said okay, you know I'm coming from that too and sort of typescript javascript is the stack I'm most comfortable in, and then he suggested. Why?

B

Don't you hop on to the lord star, uh discord and see what those guys are doing- and I said oh wow this, so our consensus, ethereum consensus is client in drive street and javascript, and they said yes, they are, they are doing good and they are almost main net performance, and this is how I basically got into uh the lord star discord and there I started interacting with the team members and very organically.

B

I basically, you know, got into uh the lord star development and uh it's very happy to be here very it's an incredible team and we have very incredible uh peers and uh doing incredible things. So that's how I got into this ecosystem and there has been no stopping since.

A

Thank you so much for the introduction. This really is inspiring for any new user who have been lurking around ethereum and are looking ways to get involved. So I hope this story of yours may inspire other people to join the ethereum community. Well, I'm aware that you have got a great presentation to talk about uh yeah. So without further ado, let's just peep in.

B

Okay, awesome, so load star is ethereum, consensus and typescript, and uh we have about 655 github stars, and this is developed being developed on the the roof of chain. Safe line. Is our team lead and we have incredible team members like cayman, um turian, daddy, myself, phil, and I have a very, very new member that has joined our team desert.

B

So so what we have? We are here to talk about this about merge and what exactly is merge right. So there is this traditional ethereum blockchain, which basically has the transactions in each of the block, which are modifying the ethereum world straight and through something called ethereum virtual machine right.

B

So these are the blocks that are being added and they are modifying the straight, and this is basically what results into restaurant, into the balances being transferred, the tokens being transferred, are tokens being maintained or burned right, so so all the tokenomics that is behind it right. So now, what is happening is that we want to subsume this execution there into uh into the beacon chain right.

B

We want to subsume these execution payloads into the beacon chain and this beacon chain has been running since uh december 2020 and it has gone through an ultra upgrade which basically provided native support for the light clients.

B

So let's just have a small review of what this merge is all about. So what we want is we want to.

B

We want to couple this execution layer which basically is responsible for modifying ethereum straight with the consensus layer now consensus layers.

B

Responsibility is how to build blocks to form the blockchain and that so these are the two modular parts of the new ethereum ecosystem and that's what we want to couple in the merge and what we want to take take ethereum off is proof of work and there is a huge, huge effort that has been going on in this direction, uh led by pari and marius, and so it has been going on now since seven eight months and uh we had a very recent success in sepolia merch right.

B

Basically, apart from the few configuration hiccups for the clients, it all went really well, so so what what are we trying to get out of merge? We want sustainable security. Basically, we don't want to spend so much budget on basically making sure that okay, miners are compensated.

B

We want to really scale uh the transactions and the way to do that is through data scalability, and that for that beacon chain is a stepping stone, because then the next things that are coming up are going to be sharing on the beacon chain and all that is sort of natively being integrated into the beacon chain. The one thing that is being another thing that is being provided is finality, because in proof of work there is no concept of finality.

B

The highest difficulty, the head with the highest difficulty wins, but at any point someone can build a chain which can re-out the canonical chain, but here in the beacon chain we have finality, and then we have like clients which are sort of you know. We want to make sure that everyone, even with very less resources they can, they can sort of validate at least validate the chain natively not uh and in a semi verified way.

B

So that less and less you, you need to trust less and less to the gatekeepers of the gatekeepers and of the apis that connect to the nodes, and we all want. We all want to do this without sacrificing decentralization. That is the main point.

B

So, with all the good things, there is a natural question when should when, when is the merge- and this has been asked again and again in the twitter verse, and but what I'm saying is that we are running out of test nets, so we are almost there. Next is go early and lord sir, is ready.

B

So load star is the youngest consensus kid on mainnet and we have been uh proposing mainnet blocks since november 2021 and basically we have been. uh We have been around even a few months before that. So so so that's that's. When we first got a chance to propose the block and since then we have made huge strides, our uh we are running on par with other clients.

B

The profitability is on par, so phil basically conducted a twitter poll in which, basically, he presented that okay, you know which one of these nodes is is lord, sir, and which one is, for example, the other leading consensus, clients and, of course the last one is where the block proposal has happened, but in the other ones there is no way to basically say which one is lotsa and which one are the other leading clients that are running on the main net.

B

So we are there and that's why you should use us, because we are also production performant, we don't consume so much resources. People will think that our java virtual machine will sort of hook. The memory will take too much cpu, but that's not the case here. Our team has worked really really hard to make sure that we are production performance, and that is how we want to be.

B

And obviously we are merged ready and we have been participating in the merge since the beginning since devnet's in the kiln network, in goalie shadow folks in mainland shadow folks in dropstern in sapolya. Next, we we will be definitely uh doing a successful, merge in goalie and then the main mainnet is our goal and the clients that we work really well with our cat. The mind bezel tmjs arigon is a client that we are testing with to make sure all the points are covered, but other clients are sort of well tested.

B

Obviously, ethereum gs is not a client that is running currently on the main net, but on the kiln network on separate network, where the blocks are not heavy, you can also pair us and go full javascript stack right so and the main sync features that allow us to be much ready are weak. Subjectivities, sync and optimistic thing now, which subject is subjectivity. Strength, is not really a much feature. It's it's right.

B

Now it's working even now, but for the people who are coming from it from uh the proof of work landscape right, then they will jump into into the new landscape where, where the consensus and execution layers are coupled, they will sort of need to just jump to the to the sink point to the head and weak subjectivity.

B

Thank you will allow them to sort of jump to the head and get them up and running in a minute and optimistic sync is something uh that is that has been born out of this merge effort, because now we have two coupled clients right. We have consensus and we have execution and obviously their payloads have to match right. So they have to go step in step, but but but you, but these are independent chains which are merging and at any given point uh it's they can go out of step right.

B

So optimistic sync is the sync method methodology to take care of the fact that, okay, even if execution layer is out of step from the from the consensus layer, abs or there, it's it's a bit ahead, it's a bit behind. So there can be any kind of cases that are that that can be over there. Optimistic sync will sort of make sure. Eventually, both execution, layer and consensus layer will come into sync, and then they will further on. They will proceed uh in a locked step manner in a tightly coupled manner.

B

And we are not only merged ready, we are also meb boosted. What it really means is that you can hook up an ev boost, relay or or a builder, and basically if we will try to maximize uh that, you get the maximum block rewards and now these two things it's not an either or for load star. We, we basically run both of uh these workflows, uh parallelly and then we basically, if mev boost, sometimes can give you nothing because they might not even have a bundle to build a mev boost block.

B

So in that case, load star will fall back on the execution block and it will definitely not miss any opportunity to build the block, because building a block is like a lottery on the beacon chain.

B

And not- and I I won't stress again how important is the optimistic thing in this entire process, because it seems like a very small feature, but for cl clients, it's like how there are so many ways in which execution clients can respond as to to the payloads that are coming in and cl, clients will have to sort of embed those responses in their full choice.

B

Now folk choice is sort of a very sensitive module of a beacon chain which every which each client has to sort of you know make sure that they are robust over there and they they sort of uh evaluate it correctly and because, in the end, your heads have to match with other clients head.

B

Otherwise, you, you can't follow the network anymore for el clients, it's even more complicated, because now, if the cl clients tell the execution clients that okay, this is our head now execution, clients will have to go back, fail all all the way to a canonical chain. If they don't have that head and they will sort of have to execute all the blocks, they will have to build up their state all the way to where the cl head is then.

B

In the meantime, the cloud is also moving because the blocks are coming in with each of the slots. So it's it's a very complicated piece and that's why I think it deserves a mention over here and the second thing that that red, the second awesome thing that can happen with the merger. Basically, you know you can combine like clients and into awesome scenarios.

B

Basically, we know we so there there are community members in our lord studies code who are working on bridges on embedding other, like client, like client into bridges, and obviously hardware wallets is one go to use case, and then I just recently came to know that get is sort of also embedding a light client into the into itself so that it can be used as a standalone client and provide finally finality.

B

So basically, finalize header and the latest error right as a pointer into uh into uh into the execution chain, and this is basically what everybody wants. They want, what is ahead and where with and what is the finalize point, which can't be reverted, and so so ex so like clients are going, can have a very, very important uh space in this new ecosystem.

B

So that's that's what I'm we want to show you over here how I like client wallet. We were able to run a light client wallet in a browser currency with low satellite client and ethereum js. Let me just stop a video.

B

All right, so, basically, uh what we want is that everybody has their dream for where the ethereum ecosystem is heading, and somebody wants to flip the number one cryptocurrency in the world, and somebody is just thinking about okay, what what are the benefits the merge will get and obviously, if the data you know, if there is data scalability, then l2 is going to get lots, lots and lots of boost, because f2 is totally dependent upon how much data we can bundle into our ecosystem and that should basically shoot on the price.

B

But what is really important is that there is a word of caution that right now, uh the consensus clients are sort of you know not really evenly distributed, and we need to diversify the merge. We need to make sure that more and more people use minority clients, and you can do your bit by running load star against any of these clients using any of the combos. We work well with nethermine gap, bezou, ethereum, js and arigon as well, so choose any of the clients.

B

If you find any problems, you can always come in our discord and we are.

B

We will be very happy to help you out and make sure that our client works well with all of these other clients, and for that we have a very easy, uh quick setup guide uh using our merch scripts that has been written by phil. All you just need to do is you need to add edit your feed recipient.

B

You need to just tell okay, you want to run validator of key stores or mnemonic from mnemonic is only supported on on the test nets. And you can you just need to secure your el communication with the jwc secret and you you just fire the command and everything else will be done for you all.

B

The configuration will be pulled, all the images will be pulled for you and they all will be spinned up, so so that you know basically- and we we are committed to maintain- uh maintain these this setup so that there is an easy on-ramp uh for any user out there, and then they can basically edit uh the configuration over there once they know what they are doing and use that configuration even for their production setups, and we basically invite anyone to come contribute to us.

B

We are a very open, open team and we love contributions, and we will be happy that you know, since there is a huge, huge developer base for typescript javascript we've. We would want that uh as many as developers who want to come. Look into our code do things that are there in our pipeline or even if they are not in a pipeline.

B

If they, if they add something to your applications, you can open the pr, because many times we have upstream the prs that people have done and sort of integrated them into lordstar or any of the other modules that go with it.

B

And thanks thanks a lot for for going through uh this. uh Someone awful lot started now how lots of is doing with the merch.

A

Thank you. It was great presentation. Thank you for sharing all this information, um as I mentioned in the introduction, like lord star, is relatively new and I'm assuming that there could be more utility apps, as also mentioned on the official website, that load star is already using some of the utility apps. So the usefulness of this client implementation cannot be undervalued. Well, the presentation shared a lot of information. um I have a few more questions. On top of that that we have collected from the community. If it's fine, we can probably take a few.

B

Yeah, please please go ahead.

A

All right, um so my first question is about the client. uh We know the project is supported by chain safe, which is basically a blockchain rnd form with a multi-chain perspective.

A

Also load star was not a part of initial client's launch when it was in 2020 with the beacon chain genesis. I'm curious. What's the main motivation behind adding an ethereum consensus, client.

B

So the main motivation is that this is, you know you have a big developer ecosystem that is out there, which is working on this web 2.0 stack. How can you bring you know on to bring them onto onto this blockchain ecosystem and make sure that and bringing them on to means that, okay, they they can participate in the consensus they can part they can look at the code.

B

They don't really have to learn something new to contribute, and this is sort of our goal that okay, we want all of all of these developers not only to contribute, but also to use notes all right and we are we can. We are browser native as, uh as you know, you will see with our uh like client video uh that that is lord satellite trend directly being used in the browser.

B

So we are browser native, and it makes sense for us to make sure that you know we can provide accessibility to as many developers as many devices and as many applications that want to embed us.

A

That is awesome and in a way it is good, because ethereum is anyway moving from proof of work to proof of stake. So, if joining, why not to join with whatever is the future.

B

A

That's also cool. Thank you. uh My next question is about uh the present and post merge for the client. uh We talked about different features. Some of them are actually not part of the emerge like weak subjectivity and optimistic link is still in discussion.

A

uh There is this one uh topic mev boost, which I feel is like very important: pre and post merge. Maybe if you can talk a little bit about the significance of maybe boost.

B

Right so basically, what really happens right now is that uh all these miners they are running, running modified for version of geth or whatever they have whatever is their favorite uh execution client right now, and what really happens is that, okay, you know they get bundles, which they have to execute in a one particular order, and for that bundles, obviously they get free and but what they, what what they really want to do is they want to put those bundles embed, those bundles in the block and what? What?

B

What enables people who are trying to bundle their transactions in uh is that? Okay, you know there is some dex exchange in which there is something there is. There is an opportunity to have an arbitrage right. So, for example, there is a pair that is not balanced, which is lagging behind the market, so they can sort of take arbitration, uh arbitrage opportunities and make money in the process. So all this is good for the ecosystem, because you don't want a bundle to stay out of the market rates right.

B

So these are the market participants who want to make sure that there is equilibrium in the in the ecosystem and mev boost allows that to happen, and so so this is currently. How is how it's happening right now in a post-merch world, the mev boost is sort of natively being integrated. It's not really part of the specs, but there is a very clear integration path that has that is really being. Data has really been turned out for mav boost and what's happening. Is that uh the consensus clients themselves?

B

They are they? They will be running a parallel flow with the execution clients so that we get the bundles and now these are the bundles that are beneficial also for a person who's proposing a block right because they get they. So they get they get money for it. They get what is called a buildup bit in which, basically, obviously the amount has to be more than whatever the uh block rewards are fermenting a block right so in a post-merge world.

B

So now you want that a person who is running beacon chains right, so they don't really have to worry about. Okay, you know how how do I sort of have this big infrastructure, so they can just integrate with the imev boost relay, which will which, which will integrate with this imeib boost builders and all the bidding whatever their processes will happen on their platform. They have.

B

They are sort of created a marketplace for that, but with regard to uh the person who's running a validator, we really want to simplify that integration, and so that is the integration that that is being called the builder integration and and then it's all about how much money you get you can get for your blog right. So that's that's what we want to maximize that our users do not lose any opportunity to have maximum profits.

A

Awesome, I mean more features and more easy to join in things are provided by client. That is, I believe, is uh one of the criteria that a new user look for adopting any client. So I'm hoping um this client will get user adoption fast with all these features enabled already.

B

Right and I mean a bit so we hope that with the people will definitely try to embed us in their apps, which are again based upon the typescript javascript stack and use us as much as possible.

A

B

Want to take advantage of that huge developer base, and so so the first users in who are going to strike, so they are going to be developers only. I mean this is what I really believe in, or developers related roles right, who are sort of consider them techies.

B

So we want to really. You know, make sure that it's super easy for them to join in and not not only join in, but also to look into the code. Because again it's trust but verify right.

A

Absolutely it's, of course, javascript is one of the popular language among the technical community, so my hope is like it will be adopted faster in the developers. Community, yep.

B

That's our hope. Please, diversify the merge, use, lodestar.

A

Right yeah: that is something that we are going to come later: uh the client diversity, uh but before they are. I would like to talk a little bit about the devnet and test net, as you mentioned that the first minute block was proposed somewhere in november, but you were participating before that in developers testnet, assuming that there are high chances that you may have missed some of them.

A

uh I don't know uh if the team were there at the time of rayone's, memphis and all, but I would be curious to hear about the overall journey and your experience with the participating in public, testnet and governments.

B

So definitely I mean when we started, uh we would have problem at genesis right somewhere around genesis. What would happen is that lord sir, would choke up the memory usage would go high and we would basically choke up at genesis and then basically sometimes we would talk about uh the upgrade point.

B

So we have come from that point to a point where you know everything remains smooth and steady, and a lot of work has been done by the team to make sure that we we keep our memory under control and uh we don't use too much of cpu.

B

uh So we we refactored our ssd uh to make sure that you know we are really performing because all of these things they somehow uh use ssd library in one way or the other and of our bls integrations. We have awesome integrations so that we are again performing on our java virtual machine.

B

So we have we try really hard to make make sure that we stay performant and we have been coordinating with uh with the teams with other teams in order to make sure that okay, we are compliant with the specs. We at the merge points we perform really well, and so all that shows because in all of the recent public test, nutmeg muds at merge point lordstar has never ported and we have stayed really stable and hopefully we can continue doing that.

A

That is cool awesome and I remember the ascii task: panda art. After the sipolia testnet, it was lovely and it's really cool to watch for panda, showing up after every merge on chestnuts, great.

B

Thanks thanks a lot.

A

I think uh william schwab has a question for you.

B

C

Sure something I've been curious, a bit about with lodestar is so I mean you've mentioned typescript, it's easy to embed.

C

um Why is there a specific need for apps, even web apps, to be able to embed a node using typescript like why not just like the classic kind of either api call or back end or like where's, the big gain from that.

B

Right, that's that's a brilliant question because I mean, if you are using the gatekeepers, there is a high chance that you know the gatekeepers might at some point, uh try to take advantage of you right and but if you can natively verify uh the the state of the blockchain in in your web app using, for example, our light client. Basically, what what really happens is that you are decentralizing that trust.

C

So, basically, what you're, hoping for, isn't that the app itself will be embedding load star. It's that each user will have a load star node.

B

No so so I mean it can happen in both ways in in many ways right, so that really depends upon how the app wants to have its architecture. It can happen that app can have, for example, bridges would have just uh like one light client instance running, and it could happen that some app can decide and a like client in in the browser itself, and that's what that video shows you that how the light client is working in a browser.

B

What it really means is that you don't transfer your trust all the way to these gatekeepers. You know you get data from them, but can you verify that data? Now, if you have load cell light client running, you can basically say: okay, this is the checkpoint. I I'll start from okay and from this checkpoint. Can you give me a proof that this that uh this is the snapshot that I have downloaded, that this snapshot is valid and then you can? What are the header updates that you are getting?

B

You are getting latest and finalized header updates on that snapshot. Can you verify that snapshot and see? If you have those headers which are verified, then basically you can verify the data that is coming from execution layer. They they have verified proof api which which is being used in our demo as well. So you can verify whether the balances that they are telling you does that match up against the finalized or the latest that is coming in right. So so what you?

B

What you are doing is you are decentralizing your trust and I think it is very important that we move away from these gatekeepers because then, once the trust is decentralized, then you can easily switch the gatekeepers and then maybe at some point you can even go p2p for the gatekeepers.

B

We hope that we reach that point.

C

I I guess what I'm not understanding, though, is why it specifically needs to be embedded in a browser like how would that differ from running a right, a light, client or just even a full client outside the browser like. What's the gain from having it specifically embedded.

B

I mean again it depends upon the architecture of the app.

B

But the point is that, if, if you are embedding it in the browser and if the user trusts the code that that is being run, the browser, obviously they can verify because it's open source, so they can be pretty sure that you know the data that the browser downloaded is not malformed is it's the true data, and so we have seen the kind of hacks that happen when, basically, you know hackers feed you some data by taking over the gatekeeper and then you do some transactions which you later find out.

B

You know you are pulled so so the point really is to to enable a user to do to sort of decentralize. This trust again. I am using this word because decentralized means that a user can be sure that the verification has happened for him right now. It can happen in a browser or it can happen in the app back-end. But then the app is sort of you're, putting your trust in the app, but obviously, at some point, uh users can demand that all this happen in the browser I mean.

C

So I understand to be right: when you, the the the advantage being able to put in the browser, is the the kind of the extensibility that you're able to build something. On top of that, that should be able to verify information adapts for a user very easily, as opposed to being kind of a more manual process.

B

Correct I mean, and, and basically what we want is that users should be freely able to switch their gatekeepers right, so we want them to move from gatekeepers to p2p right. So you you, don't basically then rely upon the apis. You will rely upon peer-to-peer network to feed you the data and that's where the real decentralization will happen, because then no gatekeeper can sort of take advantage of you, because the trust is decentralized. Now, why? Why do everyone really, you know, is okay using inferior because they really trust infurial right.

B

How can you decentralize that trust? That is, that is the question over here.

C

ah Cool thanks.

A

uh Yeah, that's right! uh That is good. I think uh the decentralization of infuria is also very important here, because that has been a center place and with this much uh upgrade it is said that do not use infuria for even running your uh execution, client right.

B

Because correct because I mean the connection between uh your consensus and execution, client is assumed to be of full trust right. So there is 100 trust that is happening over there, because if your execution client will feed you wrong data, you will definitely follow a wrong chain that that is the worst scenario.

B

In the best scenario, you will just not be able to sign and follow the chain.

A

Right and my last uh set of questions are related with the the client's combination and then decline diversity um according to you, uh which one would you think, is a good combination to run with lodestar the execution layer, client.

B

So I would go for a minority combination uh so that you know we also have diversity on the execution layer of site. So maybe nethermine is a good combo, but we play nice with everyone and we would want you to try running lordstar with everyone, because if we are running with everyone, we are robust right. So we don't really want to have a preference, but you can start with nevermind and then move to the other clients, because testing other clients is just changing the argument in that simple setup, the link for which has been provided.

B

So you can just change an argument and spin up a different client and since the client support optimistic sync, it doesn't matter whether the load star is synced ahead or they are starting afresh, but they were thinking ahead and lost is starting afresh right. So that's all that matching is done by optimistic thing and we are very proud to support it.

A

That is very good know. I know um optimistic sync is a topic that we probably would be having on our show like we will be having some guests to explain it in detail, but this high level uh information of uh the flexibility that it is providing to use. Any combination is good to know.

B

Yep and basically, if you try different different combinations, you can see you know you can run, for example, get in one and then you can stop it and then switch on to nethermine and then switch back to get so you can, you can see, you can see how how how the clients are behaving and how robust is optimistic. Sync- and I think it's it's it's a great spec that has come out of the entire effort.

A

Absolutely absolutely I mean all the research work which are being added by the ethereum researchers and community are great. We are hoping to make the network really robust. One.

B

And we uh we also have. We can also say that we contributed to one part of the optimistic sync and which was adding safe slots to uh optimistics, to sync optimistic right, so which is basically at the much point.

B

Basically, if, uh if you get a block uh whose execution which is refuse terminal uh uh which whose terminal block which basically, which is the last proof of the block that is referred to uh post, merge if that is not available, then basically every every client. If all the clients import that block all the clients will go into a syncing mode and they will uh stop following the chain.

B

So the network will break so we uh we uh we contributed to that module where we have this windows safe slots to import optimistic blocks uh so which is currently set to 128 slots, in which you can't use optimistic sent to import the blocks at the merge time so that you don't run into these kind of scenarios.

B

So that is a contribution that has come out of the load, starting.

A

Incredible, thank you so much for sharing this. I hope that we will have either someone from lodestar or from the research team on this topic to be uh presented on this show, so we can have a deep dive into it. Well, um the next one is my favorite one. It's about the client diversity. If you like to share your thoughts on the present client diversity ratio, I know that uh there is a need on both the execution side and even on the consensus side, to come up with a better ratio.

A

How do you think load star will be able to increase the current network share.

B

So uh I mean, but we so I think the primary channel is so the primary way to make sure that happens. Is that to be present on all the places, uh uh for example, on rocket pool we uh we did, uh we basically implemented a feature for doppelganger so that we can be on rocket pool, and you know people can use us. So easy accessibility is uh one of the key things and we are trying to make sure that we are present everyone.

B

We are integrated with everyone and then we we are trying to make sure that we are very, very on par uh with other clients in terms of possible on in terms of profit profitability, and we definitely want to uh have state of the art features like mmv boost and make sure that we provide opportunity for our users not to be left behind in any way.

B

So so our that that is sort of you know, and then there are outreach uh that we are trying to do. We are trying to make sure uh that you can spin up uh execution client combos with lordstar in an easy manner, so we we are trying to do all those things so that people just they don't need to think twice. They can just run join any test net and if they find load star performance satisfactory, they can they can use us for production as well as our discord is very friendly people.

B

uh People have sort of uh said that uh you know this is the friendliest uh client team that is out there on the discord, because we take whatever troubleshooting is coming our way very seriously and we go extra mile to help out our users.

A

That is very sweet of the team. I understand there are a lot of development work involved and, on top of them, providing support to users where discord is really great to have well, it's time to wrap up any message for the ethereum community load, star users or potential users of the client.

B

So I we just want to say that okay, don't think twice just run that uh single command and we have very easy setup for you. Just try us out and if you have any feedback, just let us know coming our discord, we're happy to help you out.

A

Cool these are great words and I'm sure these are comforting as well for new users.

A

Well, it's my thought that ethereum implementation and typescript may have a lot of potential in future, and I hope the information shared today will be helpful for validators, considering running a load star node for consensus layer getting there. We appreciate you taking out time and talking about client apps features and merge preparation. Thank you. A lot.

B

Thanks, thanks uh very happy to be here to present all the work that we have done and hope to continue doing doing that and make sure we make the ethereum ecosystem proud of us.

A

Of course, and on this note, thanks to everyone watching or listening this special episode on the merge, should you have any question? Leave a comment or reach us at eatgathers.com check out description for links to useful resources and guest twitter to follow check out, know your client playlist to follow the recordings of merge special talks with different clients subscribe to the channel for more useful resources. Coming up your way, keep sharing your love with eternium cat elders, cheers.