Remy and Phil demonstrate how to setup a Lodestar node on Prater

Transcript

hello everyone my name is remy i'm from the eve sager community and today i'm joined by uh phil from chainsafe and lodestar hello phil hey remy how's it going getting you um today we have a special tech demo video about how doing your own lodestar setup um but before we dive into this whole subject i'd like uh phil to tell us a little more about like what he does at chainsafe and what's this guide that we're going to be following today thanks remy yeah so my name is phil noe i work at chainsafe as a technical project manager i'm actually joined here in july of 2021 i've been with the

lodestar team since uh november of 2021 lodestar is is of course as you may know a uh a typescript client implementation of ethereum consensus um and sort of what i do here is i manage um the team the uh the projects uh the project itself alongside uh helping to like you know organize and ensure that you know the client remains steady optimal and uh is ready for use on mainnet in which it is so yeah that's uh pretty much what i do here at chainsafe i'm fully focused here on the modestar project and chainsafe itself works on many different things

not just on ethereum but also on other blockchains as well can you let us know why someone would want to use lodestar as its consensus client yeah so um so we are actually like a client that went uh to mainnet production in about november 2021. so yes we may be a little bit late comparatively to some of the other clients um but you know that is also not a bad thing you know we are the fifth uh consensus client to come online uh which is you know much better for client diversity we are the only typescript client which uh helps open the doors to a lot of typescript and

javascript devs as well um by us being the lowest used at the moment it also helps to you know keep ethereum safe when you look at utilizing an ethereum consensus clients some of the incentives you have to think of is not necessarily just how much money you can make but also what your risk tolerance level is because the more people that use a specific clients um the more inherent risk there is if something were to go wrong with it so we are kind of a plan e i guess for for most people now good to know um

with these words let's get started um with the guide here let me go ahead and share my screen so that you can see it and um let me just go and try to fix some of these issues with my thingy here there you go all right so we should be good and uh you should be seeing my um screen now uh what is this guide here um that we're looking at so actually when i started here with lodestar i realized um one of the hardest things uh is to actually um you

know lay out the step-by-step how to actually set up a client because um we do have a problem in ethereum with client stickiness and a lot of the times if we don't uh necessarily uh give people the information that they need a lot of the times they'll either give up or they'll have to troubleshoot themselves which is more time on their end so taking upon the um the model that sommer had done for all the other clients earlier when the beacon chain launched i thought it would be uh very pro of me to actually do something similar for the lodestar client so this is what this setup guide is this is the version two of its uh i did have an

earlier iteration but this one is uh is the most updated one here to get people to set up from scratch so let's get started with the the guide here we have a bunch of uh steps obviously if you're not aware this step will focus on using ubuntu 20.04 so you have to install that first if you have issues with that we can help you um with the eavestaker community um we'll be using um gef as the execution a client but um maybe there's different options there and once we get there we'll talk about those as well we'll set up the load start client and we'll have to

install docker first and docker composed and maybe we'll be using metamask to do the deposit but we'll see how long this whole tech demo um lasts if you don't know if you want to do your own validator setup you need 32 if that's for mainnet in our case we'll be doing this setup on praetor so that'll be free for us unfortunately praetor uses girly eteriums and girlie has been abused for a bunch of weeks and months now so it's getting a little hard to get a hold of 32 go if the currency used by the predator network to do the deposit

but if you need help the e-security community can also help you there um like um like i said here there's a bunch of different places that you can go to if you need support um for this guy at all like support in general for uh lodestar the first one is the chain safe discord you should definitely join their discords if you run or if you're a user of the lodestar client there's a another important channel that you should also be following it's the announcement so every time there's a new version being released there'll be an announcement there if there's any issues that you need to be paying attention to it'll be posted there too

um for the prerequisite you'll need a server um i'm going to be using ubuntu desktop here so maybe that'll work too uh we'll see and metamask and a browser so nothing special in terms of hardware what kind of hardware are we looking at here phil so uh of course we're not necessarily the most efficient uh programming language being used here on with loadstar so um you know we do require something a little bit more significant than saying like a raspberry pi um however a generalized uh like a generalized computer these days will be able to handle it

our heap size memory usage is uh somewhere along the lines of like as low as like one and a half gigs so far so a general purpose computer these days will will do um it doesn't even need to be like a one of those hardcore gaming computers either yeah absolutely like you don't need like this huge beefy machine to run your own validator setups what i usually recommend is like any anything that has like four plus scores um and which is like a recent cpu should do the jobs in terms of processing powers in terms of memory um maybe maybe you'll need something along those lines of 8 gigabyte or like 16 gigabytes of ram

and in terms of storage i believe those numbers are only for storing the consensus data but if you want to run your own execution client as well which is what we recommend generally you'll need something more along those lines of like either one terabyte of ssd space or like two terabyte yes the the biggest thing with this is of course the the type of storage hardware you use highly recommend using the end.2 nvme ssds because those have much higher write and read speeds that is generally the most important thing alongside the capacity

which i would recommend you know at least like a two terabyte stick at this point yeah that's probably a good idea here let's keep going here on the overview we'll be generating hours taking validator keys we will probably skip some of these security recommendations in terms of like firewall and security but we'll talk about those we'll set up our execution client um we'll set up and configure the load start client including like doing the prerequisites and installations and we'll do the deposit maybe we'll see how it goes and so this guide is separated in different parts and the

first part being the generating the sticking data here so that's generating your keys as usual like if you want to do this on mainnet eventually and stake your own money you should probably try this on a test net first which is this recommendation here running on a testnet is free you can try it you can see how it goes you can gather all the data that you want you can experience it first then and you can like eventually tell if it's if it's for you like in terms of um instructions and maintenance and like um doing it all yourself so that's a pretty good recommendation here so let's

get started with part one generating the staking data um in this guide we have a bunch of options um the options that i like um here is not using the official staking deposit cli but using the wagu um installer um not the wagon installer the wash gu keygen here which should be down below so if you don't know the wago keygen is a tool that i'm part of that we created um so let me just download it here um show you guys how it looks um so if you want to run it on ubuntu here you just have to make this

download file executable and you can start it here so the wago keygen is this simple tool that enables you to generate your own validator keys you're nothing fancy about it so if you are to create your new keys you just create here and click here on this new um create new recovery phrase you have to select the proper network today we'll be doing this demo with the prayer test net so that's what we'll be using um and we have like a bunch of these um descriptions about what you should be paying attention to like make sure to actually write down all these words since this is just a test for us we'll

we'll go ahead and we'll just copy and paste the words i'll be using a weak password here but maybe you should create a stronger password for your own users especially if you are to do this on mainnet and i would just add here as well if you're doing this on mainnet it's uh much um better for you to run this key gen likely on a air-gapped computer as well that's a very good point right yeah and so like you don't want this to be running like on any internet connecting connected devices because of the potential risk of someone being able to steal your keys and like eventually

steal your money right and so running this on an offline computer maybe on a live distribution [Music] would be even better there so at this final step here we just select on which directory we want to generate the keys in and we click the create button so nothing special here it'll take a few seconds and eventually we'll get our keys if i click on this link here i'll see the keys being generated um with our deposit data file that we'll need to do the deposit so nothing special here there's a bunch of other texts that you should be reading i've done this so many times at this

point that i'm just gonna skip ahead and go to our next step so i believe we are done with part one of this guide so we generated the keys and we are good to go for the next step the next step would be part two um but like i said previously i'm going to skip this part um but you should probably not right so this part has a lot of good practices that you can follow to secure and harden your own machine where you'll be staking and it's very important to do so in terms of like managing your own risk

right so you want to limit all the interfaces on which people can connect to your server you want to make sure that you're using like good ssh keys to connect to your servers if you need to you have you want to make sure to use a properly configured firewall and there's a bunch of other thing that you should be doing here since this is just a simple pack demo on a test net i'm not going to bother you with all these different steps but you should definitely look into these the interesting part here is going to be the guide to set up a load star itself right and so the first step would be to

to install the docker engine docker is this tool that we'll be using to run all our clients right so instead of just retyping those commands i'm just going to copy and paste them here i'm kind of lazy and so this is just faster for me all right so we're just entering this command here we're just letting ubuntu download all these packages and in the end after all of these different logs that you see on screen here you'll have docker installed nothing special about this this is just a usual way to install any software with once i'm done with that i'm gonna make

sure the ubuntu service is always running whenever i start this machine so if i were to reboot the machine docker would start on restart and we'll make sure we have um docker compose properly installed by checking its version there we go we have version 1.25 which should be good for us here this next step here is going to download load star and we will be using this folder to get started with um installing all the configuration that we need for a so let's get into load star whenever you

use this docker compose tool you have to use this end file and so we will be opening the file with nano nano is this command line uh tool that you can use to open and read any file and modify it so in our case here we don't want to be using the mainnet network we want to be running on crater so i'll have to change this option here and save my file so what i did there is just ctrl x there was this small little menu at the bottom that said um control x is meant to write the file um it asked me what my what name i want to write this

in i just press enter the dot env file name is correct it's the same file i just want to overwrite it and what i did here is just what was mentioned in this notice box here so if you want to run on prater you have to change this variable here the load star network once you're done with that you'll have to create your own docker compose file and you shouldn't be too worried about that we will just copy and paste um one which is pretty good for most of the use cases here so i'm just gonna

copy and paste this whole text here this one here is actually for the nethermine docker so you have three options now this is the updated version so surprise everyone we support client diversity that's pretty good yeah i just updated this today actually um so the first um yaml file that you see up there is if you want to run another mind as part of your um your execution node and then uh further down there's option two and option three one of them being for basu and then the other one for bing gap and then you just need one gamble file um depending on which one you choose to run awesome i haven't tried the neta mine uh yaml file yet but maybe that's a good

thing to do right we'll see how it works and we'll see how it goes here so let's go ahead and use neto mine as our execution client um and this leads me to this whole discussion about which execution client you should be using right because here we have three different choices phil can you tell us which one someone should be using yeah so uh if there's a really cool site called clientdiversity.org that someone in the community had set up for us which actually shows you the current uh combination of clients that are both on the consensus layer and also the execution layer so right now we

obviously have very little usage for lodestar but it's it gets worse when you actually go down to the execution clients because we have much more of a super majority with gap so part of the reason why i updated this guide to include some other uh execution clients is because we want to help diversify that layer of consensus as well um or or of the protocol so um nethermind is one that we're actively testing in combination with lodestar as part of the merge as well so um you know another mine is a great option we have one with the with bay zoo as well and then of course we have the

original setup with geth but we want to avoid uh more people from using get if we can help it right now get being like this huge majority client is not such a big issue because um miners are mostly the ones using it for producing blocks but eventually once we come to the merge people the validator is going to be the one producing the blocks and they will be deciding which of their execution clients are going to be building those blocks and that could be a huge issue after the merge if everyone's still using gef

geff has a bug it can create a bunch of conditions leading to a lot of people losing money and we want to avoid that right so eventually it'll be great if we could push this narrative of like make sure to run a minority execution client as well as using a minority um consensus client so maybe you will add this link to in the youtube video description so that people can see it so let's go back to choice here so um i decided to use nada mine because it was the first one but decide for yourself which one you wanna

you wanna run here so i just copy and pasted this uh yaml file and i don't believe i have to change anything in here so all these configuration options should be good to go for my next step so once i'm done with entering which configuration option i want to use with docker compose i can just press ctrl x and i can answer yes to save my file and i'll have to decide the name of the file by default i'll have to overwrite an existing file called dockercompose.yml so let me just copy and paste the name of the file here into my terminal and it asks me if i want to override it

i have to say yes and now i'm good to go for my next step um but before i i show the next step here i just want to show you guys the different kind of configure configuration options that you can use here one of the most interesting one is the ability to quick sync your beacon node right so if you wanna sync from the from start um it can take a bunch of hours and even a bunch of days before you can get a beacon node that is fully in sync with the latest state of the the network but using a quick sync um

endpoint like infuria can quickly um and like securely get you up to up to date with the latest uh sync for the beacon uh layer and so i'm not gonna be using that but this is a very interesting section that you should probably be using uh if you want to speed up your ability to sync your uh beacon node i'm i'm not gonna be using it but i'm gonna show you guys later on in the logs like how long it can take to sync a um a beacon layer uh we'll see yeah i'll i'll just add to that um so just to explain a little bit for further context there is something called weak subjectivity checkpoints uh as part of that protocol layer which basically

allows you to take a finalized checkpoint of the ethereum blockchain and basically sync from this point forward and then backfill the entire um node all the way back to genesis this is meant to get beacon nodes to actually get up to speed much faster without having to necessarily subject yourself uh to a bunch of security risks in fact it's also recommended that in order to prevent yourself from being vulnerable to a long-range attack for you to actually use something like weak subjectivity syncs and i believe adrian sutton had a great talk about this um in event that the dev connected so if you

guys want to learn more about this make sure to go and check his stock there all right so i guess we are good to go get started on running our execution client here this command line here was meant for gef but if you want to run the netamine client you have to change this one a little so let me just paste it here and you'll say you'll see here it didn't work because i'm not using gef i'll have to be using netamine docker uh for the name of the docker i wanna start so let me get that one starting and you'll see it's like doing a bunch

of uh stuff in the background like downloading the client and like building uh the images and once everything is done you'll see something like creating another mind docker dot right so the next step would be to see like what meta mining is actually doing and you can do so by looking at the logs so let me just copy and paste this command again and like the previous one i'll have to change the gef docker name because i'm not using gef here i'm using neta and so you can see that um in this log here we can see that metamine has started

and it's currently syncing right so you can see that it's downloading some blocks or some data that is going to be used to create the the execution layer database and if you want to keep watching like what netemine is doing with its log you can use this um flag here dash f and you'll see the live logs just going on right so you can see it keeps downloading um those ads and you can see the different peers and like how many peers are connected to so it shows you a lot of different information about the network that you're

syncing to i believe i made a small mistake here i don't know if phil saw it i believe i'm sinking on on main net for nethermine am i wrong here no you're you're correct so basically the yaml file is already set up so that you're syncing on mainnet there is a yellow box that makes a little disclaimer for testnet users actually where it says if you are looking to sync it with the gourley test net you just have to change one little parameter inside of that command so it would be configurely sorry i missed that so it's this one right so i guess i guess i i

screw that one up there so let me just go back and change my config file yeah in fact this will be great because then i can teach you how to actually wipe the uh the volume and then you can start over from scratch so that way you uh you know how to like basically clear out your your docker all right so here was the config that i missed so i was using the config for mainnet um so there's like this execution layer that's called girly which is the one that's required when you want to run on praetor so i'll i'm i'm have to to change that one save my file again and then i'll have to

remove my image and restart again yeah i could send you the the commands as well so i guess it's this one right or something yeah yeah sudo docker compose down um you can you can say stop stop right so let me get that one there we go okay and then uh we can actually get rid of the current volume on there as well sure so if you do um pseudo docker volume ls without the without the hyphen so that

docker space volume space ls okay so if you hit enter you'll notice that it'll return a bunch of different volumes that you've already set up for um for docker so the one that we're actually going to remove here is actually the modestar nethermine docker so the command to actually do that is sudo space docker yep space rn and then space load star underscore another mind docker guess i have this oh it's uh sorry it's a pseudo docker volume

removed that's it that's what we're missing there uh remove oh volume is in use okay so that makes sense actually because we haven't gotten rid of the container yet so if you do actually ps you can actually see what's actually running okay so there's nothing running and then we'll do we've got to remove the container so actually pseudo docker rn and then another nethermine underscore docker all right let me try that one

yeah that should remove that container and now we can do um the original volume remove command there you go okay that's it so now that that database is wiped basically and we'll be able to restart our neta mine docker um correct container right yeah and there you go and now if we have a look at the logs that we were looking at just a few minutes ago um we should be now sinking on the girly network right so yeah here it says that we're on the girly network and it's currently looking for peers

so eventually he'll try to find more peers and once it finds a bunch of fears they'll be able to download the state of the uh girly network and you can see right now it actually found a few and it's currently downloading some of this state right so i guess we went through all these different steps to come back and fix this minor issue but that was a good practice so if if that happens to you as well you'll be able to um get a better understanding of like what's going on um under all of these tools yeah so all of the uh the test that related um disclaimers are all in those yellow boxes in the setup guide so if you are setting up on testnet please

follow those as well awesome so i guess we are done with our execution client now let's uh go to the next step which would be to start the beginner client i guess all right so we just did this part start the execution note service let's go and start the load start beacon node service this one is just like the other one it's a sample docker compose command with the beacon node container here so let's start it up like it did with um metamine it's downloading a bunch of stuff it's building the um image and it's starting

it here so all we get um is this line here creating load star beacon node underscore one line done but if we want to actually see what's going on we have to check out either uh with sudo docker ps to see like what are the image that are being um that are running right now and we have to uh call this other command to see the actual log for uh the beacon node here so let's call this command we can see here that load start started with version 0.34 but i guess this is the wrong version

right phil yeah so actually when we released 0.36 we did not update that but what's more important is just compare the the commit which is 2 8 echo to charlie 7 4 charlie that is actually the 0.36 version we'll be pushing a hot fix for that and i had that issue the other day too so i was just wondering which version of uh loadstar was running but don't um don't despair there this this is the 0.36 version here and so it's searching for peers now i'm not like actually looking at the latest logs um as they come through but if you add the dash f flag there you'll be able to see like

the logs uh live coming in here and you can see that it's it's still sinking and searching for more peers i guess because i see here that i only have four peers so as your clients run it'll try to find more peers and it'll help syncing faster but you can see an estimate of like how long it's supposed to take uh to sync the whole network and you can see that it's probably gonna take like a few days right i'm getting like 9.5 days left here so hopefully it'll take less than nine days to sync the whole network um for this uh prater

test net but if you were to be using the quick sync as we saw previously that would only take like a few minutes like maybe two minutes um or something yeah just just to add to that you know as i mentioned before sinking from genesis is not necessarily recommended just due to the vulnerabilities for long long range attacks however we are doing some updates to our database which will help with the slots per second in which we verify all the data going back from genesis so um it may be a bit slow depending on your hardware requirements and stuff but um at the end of the day um you know

quick sync your beacon node if you can yeah that's the suggestion i tell everyone uh to use so i press ctrl c here to quit this live streaming of the logs and we will keep um moving here so you can also start the promedius and graphana services and those services are very interesting if you want to do monitoring or alerting those are very useful i'm not going to go too deep into those that's not the whole point of this um tech demo but you should definitely check those out as well now for the most interesting part here

i'm gonna set up the validator for lodestar the first part of this will be to create this directory for hauling the key stores right so the key stores are these files that are generated by the the key gens the either the sticking deposits cli tool or the wago key gen and so they need to be accessible for the load start validator client so we'll just create this new directory here to hold them and we'll have to copy our key stores there and i don't know if you remember i created mine in a directory on my desktop so let me just list those files there i call that

direct3 keys and you can see that uh when i generated those files i generated i generated one key store and one deposit data file and so all i need are the keystore files and since i only generated for one validator i only have one and so all i'll be doing here is copying that file from where i generated those files into this new directory to hold all the keystore for load star so if you were to generate your keys on a different machine you'd have to copy them on a usb stick or a usb drive or like transfer them in some ways and copy them back to your sticking machine

so let me just copy that file back from my um desktop into this new directory i just created you go and so if i list the files into my keystore directory i should see that i now have this new keystore file and so the keystore file has the signing keys that is required to perform all your validators duties so that's required for the validator client and so that's what's explained in all these um detail here in this guide i just i just

went through and did the copy myself the next step would be to create this key store password directory and keystore password file so loadstart needs to know what is the password that you use to create those keystar key source um and that password was the one i entered um when i was using the wagoo kijian tool if you were to use the sticking deposit cli tool you would be also asked for a password to protect your key store and so i just created the keystore's password directory and now i'll be creating the password file so i'll open

that file with nano and i'll just enter my password here in my case i use the very weak password called password but in your case maybe you'll want to use like a stronger password and so once i'm done with that i'm pretty much finish configuring the validators validator keys for low start the next step will be to simply go ahead and create the yaml file for the validator client and so this is very similar to what we already did with the beacon node we start by calling nano to create a new file and we just copy and paste this

whole configuration yaml file here and if you have to change any of these options you can manually do so if you know what you're doing but like the default configuration options should be just fine with the instruction that um were provided in the guide here so i'm just going to leave them as is type control x type yes to save the file and type the file name here so the yaml file for the value the decline is called docker-compose.validator yml so let me just copy and paste the it already exists within the directory

i'm currently in so i have to override it and i should be good there the last step would be just to tell docker compose to start this new container image so let me just go ahead and do that and we should now have this new container called load star underscore evaluator underscore one is going to be running our load store evaluator client so just like the other um docker container that we created and we wanted to watch we could use um docker ps to show what's currently running

and we can see that we have this new i guess it's this one the latest one i have the right right at the top yep the load store evaluator underscore one um container that's running our validator and a good practice is to check out the logs of it so let me just go ahead and type docker logs and the name of the container and we can see i'm going back to the initial log lines um that the validator client was able to decrypt one local key store that has this public key and so

these kinds of logs shows that everything's fine so far you'll notice we have this uh log line saying nod is in is syncing what does that tell us phil yeah so basically right now as um as you know we've done this tech setup it does take time for us to first of all sink on the gourley network but also sync on the consensus which is the crater network so you will get returns from the validator client saying the node is syncing error will get proposer duties that's nothing to be afraid of it just means that your beacon node has not been synced up yet so it's not able to get the duties that it needs to perform

so these will disappear as your beacon node syncs up any sort of additional outputs at that point will be when your validator is actually proposing things so if you see nothing that's actually a good thing good to know right so that's just one way to validate that everything that you did was done properly and i guess we're pretty much done right um in terms of um setting up our machine installing all the software and um configuring uh the client yeah so in in addition to this what i

usually like to do is um also just reboot the the the node just to make sure everything comes back online and actually reboots and continues working so that's another test that you can do for yourself afterwards the other thing as well is further down on the um on the setup guide it'll teach you how to actually hold your images when we push out updates and such like that so if everything that you need to know is pretty much on that guide and if you experience any sort of additional issues that maybe we have not seen or need help with um please feel free to let us know we're always available on discord to help people who are having issues with the guide and

also just with the client in general so i want to have a quick look at part four which we did not do yet which would be the next logical step to do here part four would be to do the deposit for your validator so depending on which network you are using um you'll have to do a deposit of 32 if if you're on mainnet or twitter to go eve if you're in girly for the prayer network and so there's uh these website from the ethereum community um called the launch pad there's one for the main net which is this link here and there's one for

prater which um i could potentially use to do the deposit but like i said previously um getting um gurley eve to do your deposit for testing running a validator on on praetor can be difficult if you need help make sure to get in touch with the e-staker community we can help you do the deposit unfortunately we cannot give you the actual um the actual go if um but we can do the deposit for you um so if you were to go to the prayer launch pad you see this lovely website where it explains everything in terms of the risk that you'll be

facing what are the technology behind it you'll have to accept a bunch of terms uh not they're not really terms but they're just um explanation of like what's going on and what you should be aware of in terms of like security and in terms of risk that you're accepting when you're running your own validator here but eventually the launchpad website will ask you for your deposit file that file is the one that was created with the keys so if i go back to my desktop here when i created my keystore using the wago key gen tool it also created this deposit data file that will be

requested by this launchpad website and eventually it'll ask you to do the deposit with an account on and you could use metamask or you could use any of the other different account that are supported on the launchpad there so i'm not going to do this step like i said getting gurley eve is a little hard these days because of the abuse that were um happening on the girly network but if you were to do this on mainnet you'd have to provide your own 32 eve if you want to do this on prater for running your own test you can ask the e-sticker community and we'll be glad to help you with that one so that was for part four um and if i go

back to the final remarks and next step as phil mentions there's a few sections to help you update your docker containers um this one is for the go etcherium the gaff docker container this one is on how you can update the load star container so like if there's a new version of load star you should definitely update your um lowstar docker container and make sure that you're using the latest version especially if there's any bugs or any improvements in terms of performance are in terms of the new features that you might want to use

so these um these remarks are pretty good and i guess there's a few sections that are coming up soon as well so i guess that's that's pretty much it right phil is there anything else we forgot to mention oh i think we pretty much cover most of it i mean you basically have a lodestar note set up now with netherline which is a very ideal setup for what some you know the beacon chain and the execution chain needs at this point in time which is some client diversity even just doing it on testnet and getting familiar with the different

clients that are out there is always something that we highly recommend people do um there are definitely people in the community who can help you with the girly eat problem um at the moment but um you know please like uh we are all very receptive other users coming to us and asking us questions about lodestar because we obviously do want people to run it to help ensure that client diversity remains a number one priority to the health of the so please give lodestar a try and we're always looking for feedback we're always looking for help so if there's anybody

out there who's looking to see how to work loadstar how to build those star in from a more developed developer perspective please feel free to reach out to us there's a lot that we can do to involve you with the project and with the ethereum community as a whole awesome and don't forget guys if you need any help make sure to get in touch with the lodestar community they have this nice discord that i've been using myself whenever i had any issues phil is is there as well he can help you and i i can help you if i i know what you're talking about um we also have this eve sticker community that can help you with a bunch of these problems so make sure to ask us we are always there

helpful and ready to to help us helps you with like everything that you need so i hope you enjoy i hope you liked it thanks for joining and i'll see you guys next time