 Today we are going to talk about options if you would like to launch your own validator node and talk about what the node infrastructure landscape looks like in Ethereum currently and you know why it's important that if you can you consider running your own node. So my name is Maggie Love. I guess next slide. Clicker. Cool. So my name is Maggie Love. I'm one of the co-founders and director of ecosystem and partnerships for Web3 Cloud. I'm also the founder of SheFi and that's me on Twitter and this is Shane. So Shane is the co-founder of decentralized authority and our teams are working together on some different place in the node infrastructure space. And just a bit about Web3 Cloud. So we are a compute and storage hardware infrastructure provider powering Web3 and we're also a joint venture between consensus in advanced micro devices and really our goal is to provide the infrastructure for many Web3 protocols. So the protocols on the software side can just focus on scaling and building it Web3 natively. So building infrastructure that's Web3 native. Okay so why is validating important right? So Ethereum believes that validators will play an active part in Ethereum's future and that they are key to more secure scalable and sustainable Ethereum. I got this quote from an article. I post all the things I take from and really this is the validators are really important to Ethereum. If you heard Danny Ryan's opening talk a resiliency is incredibly important in this space and we're going to touch on that again today in this presentation. Okay so I had a spicy treat earlier this year and kind of sparked me to go further down this rabbit hole and sort of why I'm here today. It got a lot of airplane and I spent like two minutes on it so I was really surprised. All right so you know what does it mean to be decentralized and should protocols like Ethereum and others be concerned if more than you know 50% of the nodes are running on one hosting provider? What are some of the things we have to consider? You know decentralization is a key tenant at least the Ethereum ecosystem not every ecosystem and so I wanted to challenge that notion that if we say this is important are we actually decentralized and because of this tweet Hertzner so you can see there's 16.9% of the ecosystem responded to my tweet saying they were banning running Ethereum nodes on their infrastructure so they're a data center within Germany that a lot of nodes are running on so we can start to see the issues here if we're not thinking about how to decentralize across hosting providers because Hertzner did it they're smaller but potentially Amazon could do it and one of the Ethereum foundation members Peter right kind of commented on that you know it's important to update the validator ecosystem so more people can run it at home update the protocol itself and you know if that's not happening then people are gonna go with the easy hosting providers they may not be aware of some of the risks that could happen so that was a fun fun week or so of notifications and so really quickly I just wanted to do a poll because this was a big part of the debate on on the Twitter thread how many of you think centralization of node infrastructure is a concern for Ethereum okay great so all of us are here because we're probably curious about decentralization and believe it's important for a resilient protocol and so then the goal of this workshop today is to teach you about the importance of running your own node to contribute to the resilience and decentralization of the network and also to protect yourself from penalties so we'll go over today actually the Ethereum protocol incentivizes you to be running your own node and not to be aggregated in a majority of any kind and so we'll get a bit more into that so really quickly the agenda why did Ethereum move to proof of stake node infrastructure landscape and examining decentralization across layers in that landscape and then node runner options and so Shane will get up here to run you through different node runner options at the end okay so proof of stake and solo-staking 101 so she finds an educational initiative to onboard women and non-binary folks into the crypto ecosystem so I am a teacher part of my time in the space so some of this is familiar to you I like to make sure everyone's on the same page by explaining things before we dive in so a quick proof of stake glossary for those of you who may be unfamiliar so proof of stake is a consensus mechanism where validators put capital at risk by staking it to validate blocks of transactions and secure the network a consensus mechanisms are just how a blockchain protocol or a group of any time any kind really comes to this sort of source of truth about something and it's really important in blockchain protocols especially Ethereum that we have one single source of truth in order for it to function properly a staking is just the act of locking up or depositing crypto and a validator note so really what we're focusing on today is a note that processes transaction sorry adds new costs to the blockchain and stores data a little misspelling there and so they're responsible for proposing blocks of transactions and attesting the transactions and blocks are true so if you're running a validator note they were sometimes responsible for proposing the block transactions and sometimes for a testing of the transactions a different block proposal is proposing are true so that's your quick glossary for those of you who weren't familiar and so why did Ethereum move to proof of stake of reducing barriers to entry for network participants so more people have capital to stake that improve of work where you would need GPUs electricity power a lot of capital in order to validate transactions and secure the network reduce Ethereum's carbon footprint by 99.5 percent that's really exciting for the ecosystem especially when we're thinking about attracting new applications in users who are extremely concerned and because we love the earth and we wanted to be around for a long time reduce the issuance so the protocol itself you know issues less eat to the validators than improve of work and so also means that we need to issue less eat to incentivize validators to secure the network and so 51% attacks are more costly and difficult to do than they were in proof of work and it's easier to have a social recovery if something happen negative happens and then this is the point we're going to examine today and why it's in bold and so it's reducing the centralization risk of validator nodes so there's a big concern and proof of work mining of these large mining pools of a lot of GPU miners like having a somewhat control over the network and being highly centralized so proof of stake is supposed to reduce that you know a group of validator nodes having a lot of power and so what are the requirements if you would like to be a validator in theory of proof of stake and so you know to participate in any consensus mechanism to participate in a network to be allowed to potentially earn rewards for doing so you must commit some type of capital and proof of stake it's 32 ETH and this collateral can be penalized or you can slash if the validator is lazy or dishonest so you're putting up that capital at risk likely incentivize you to behave well because you would not like to lose money and also you have to run three pieces of software so if you want to run your own solo validator node it's not just about putting up the capital there's a bit more work to it so you have to run an execution client and consensus client and a validator and so why solo valley you'll earn ETH directly from the protocol so if you're staking with Lido or Coinbase or some other exchange they're gonna take a cut of those earnings for running those validators for you and so Coinbase takes about 25% cut of earnings from stakers your keys in your crypto so when you're staking with other entities they ultimately have your private keys and so you ultimately do not have final access to your crypto which is not the case if you solo validate your complete control of your validator and your crypto control of the clients and hardware set up as recommended hardware setups but you know you can you're not locked into one type of setup and reduce the risk of large events slashing so we're gonna go over this a bit more but if you're joining a large pool that has majority of the network and if something happens to that pool they go offline they have trouble accessing the network you're going to get slash is part of that but if you're a solo staker you're not gonna run into that risk and then once again you don't have to trust a third party for running the node and information coming from that node is true so you know whenever you're staking with somebody else and they're managing all the infrastructure and information coming from that node or even if you're running a decentralized application and you're not running your own nodes you always have to trust wherever you're getting information from is true right and this is what we're excited about your solo staking you're improving the resilience robustness decentralization and security of the Ethereum protocol but there are some challenges with solo validating and so this morning this was the price of 32 ETH which is not accessible to many who want to stay at home even if we think about how large DevCon is right now it was not this large for the past other DevCon and so we're having a lot of new participants joining our ecosystem and it's really hard to accumulate 32 ETH so there is still a cost of hardware electricity ongoing maintenance of these nodes it's not set it and forget it in your home you have to have technical know-how to develop and operate in a theory of validator so there's lots of tutorials but if you're not very technical it will be difficult a secure key management so whenever you're managing your own keys you have to have very good practices around keeping it secure if you lose your keys it's not a good situation for you and so you also want to make sure you have a stable internet connection and so reduces the risk of slashing or penalties and maximizes rewards and then as you know right now even if you're staking with a non-liquid staking protocol I should say so on an exchange or on your own your Ethereum is locked up until the Shanghai update I believe or upgrade and right now post-merge it's about six to twelve months but there's no exact timeline so that means you can't do anything with that ETH while it's locked up you can't put it anywhere else or use it anywhere else in the ecosystem you can't sell it it's locked up until this next upgrade and so also we won't get to in the weeds about this but solo-stakers are at greater risk of a denial of service attack or DOS because your if you're chosen to be the block producer other players in the network can actually see that because you're not in a pool so you're not obfuscated and so they can actually you can have a denial of service if you're not familiar with it with what a denial of service attack is us a lot of averages are commonly a denial of service attack so all those memes on the internet you see them about going down happen from it's not to you know so what is the validator landscape reality taking into account the requirements and the challenges so right what a person doesn't have 30 teeth what if they don't have the technical know-how what if they don't have the time and ability to continue managing after so she could stick via a service a pool or an exchange and these options are wonderful because they increase the participation of individuals staking in the ethereum network but they aren't ideal for resilience robustness security and all those things we want for the ethereum protocol and so then knowing this knowing that there's more options what is the actual state of the valedictor landscape today so really quickly the theory validator landscape has many players and so we have a smart contract platforms so they're ones like ethereum we have software infrastructure providers we have hardware infrastructure providers as well they have solo stakers we have liquid staking protocols we have staking service businesses liquid stakers and we have investors so there's actually many players that contribute to the staking landscape and so today for the rest of this presentation before we get into the node running options we're going to look at the decentralization of the different layers of the node landscape so hosting providers 60 plus percent of ethereum nodes are hosted on centralized services I think the number is actually closer to 70 pool distribution so you know the different rules and how much eat they have staked in them or how much dominance they have a lot of coin base crackin binance etc node client diversity so it's really important that we're not all running the same node client so we're going to examine that and then geographic node distribution right we don't want to all be running our nodes out of US Virginia East the big Amazon data center and then coin ownership distribution right so depending on how much you know power and staked capital you have on the network especially these rules you're gonna have more coins and more rewards and you know more potential political say so first we're gonna look at the node distribution so this doesn't break down by hosting providers but you can see hosting is 63.9% this is taken from ethernodes.org you can go there right now and you can look up these charts in real time and so right now most people aren't solo staking most people are staking with some type of provider that's staking with hosting provider and so what this actually looks like this was the chart that made the tweet blow up and actually the number of nodes on Amazon have increased since my tweet in August and so hosting distribution so Amazon we still have quite a few on Hearthster and so right if you know Amazon cannot process blocks something happens to all those nodes they're such a supermajority that would impact everybody staking on that infrastructure and you might not be aware because you're staking through service provider that you would be in that flashing pool so it's definitely something to consider and then just the performance right of the network you know we're familiar with in the proof of work world when there was high transaction volume things would get expensive transactions would get dropped it was really unpleasant experience this can still happen if something if there's some type of outage with Amazon it can make the user experience and actually doing transactions very poor even if the entire network doesn't go down itself so then we have depositors by category as you can see it's staking pools is the largest and then exchanges so the combined staking pool plus exchanges really makes up the majority of what's being deposited on the network and you know that has many other implications oh I went back and so in September you know 13.5 million ETH were staked so a lot of money and more than 60% of the ETH was sitting with Lido Coinbase Crackin and Binance so all of these entities have a much higher likelihood of being assigned to produce blocks of transactions because they have more staked ETH and so some of the concerns that were brought up when this happened or when this was realized as obviously they're getting more of the rewards they're earning most of the money coming from the network and there's a lot of discussion around censoring transactions around the network a lot of the amuse me boost if you're aware of what happened with OFAC sanctions and tornado cash these entities producing blocks were able to censor transactions that are based on OFAC sanctions and so allowing you know unequal access and making Ethereum not a neutral network and so more importantly this is happening right now you can see what's going on between Lido and others is that they're defining the rules on block formation and what type of blocks get created once again so they can say like these type of transactions can be included in blocks these types of transactions should not be included in blocks so they're going to be able to set the rules of how things work in a theory of a mistake and then other staking entities if they don't follow these rules could be penalized so it's really important that not you know one group of entities producing blocks are creating the rules for the entire network and so this is from Martin Copeland if you don't follow him I highly suggest it founder of NOSIS and OG Ethereum a person and I believe now working on NOSIS chain she has a lot of great material around kind of like watching what's happening since the merge so you know a lot of people agreed that it's not great that you know Lido and Coinbase are producing all the blocks and so another type of you know decentralization or in this case diversity that's really important to blockchain networks is client diversity and so right now you can see gap is 77% of the consensus client so what people are running and so once again Peter he's another good person to follow if you're more curious about what's happening you know it is similar to all the NOS are being hosted in one place or there's a lot in a pool if something happens the consensus client later people also get flashed you're running that same consensus client and so you know I read an article that it's not great to have one consensus client it's better to have a majority in Ethereum purposely sorry a diversity I've had multiple clients running but it's actually worse to have multiple clients and one in a supermajority that it is to have one consensus client so it is something people are working on and there are other clients that you can run so you can see once again there are ways to monitor it you can find it but it's still you know gas is in the lead and it's a big concern for many people that are worried about the health of the network so really quickly just a couple examples so there are risks of infrastructure hosting pool and client centralization so in any of these groups if one third of the validators or like slightly more than one third are running to an issue the network will start slashing that group so anybody that's in that group and why so consensus needs two-thirds of validator agreement and so if you're in a group that's more than one third of the nodes running into issues that group gets slashed until the amount of heat inside that group is below one third of the total stake so you just keep and when we say slash it means that it is being taken from you and so if you're in that group you're gonna just kind of bleed eat until you're less than one third and so right now the Ethereum network has three major attack factors within clients prism lighthouse or gas and so if something goes wrong in those that whole group starts getting slashed and like really quickly once again Amazon has an outage issue or decides to censor and they have 53% of the hosting nodes right now these nodes will all start getting slashed until the value is less than one third and so you know going from 53% below to 33% before the slashing would end so anyone hosted on Amazon would suffer as a part of that and so you as an individual don't have control because you're part of this potential slashing group and also as I mentioned you may have no idea where your nodes are being hosted if you're going through some other type of service provider and right once again 80% it was about 77 use the gas client if something happens with the gas client and they make a mistake on the client 80% of the network would be slashed and so like the network cannot finalize in these cases it can't come to finality which is important for updating the state of the network and the penalties are much more severe for those using gas because of the inactivity leak so everyone using gas is impacted and so their stake is burned or slashed until the beacon chain can finalize again and this is just a repeat bullet so whether it's hosting whether it's pool because the pool is hosting there or the pool in general or whether it's at the client consensus level there's a lot of risk of centralization and you being penalized as a validator so like to what degree does decentralization matter in these networks there's like a big debate on that and like every blockchain protocol has their own version of how decentralized they want to be and there was a talk by tech from noses chain and you know he was mentioning that noses chain wants to be one of the most decentralized networks and that there tends to be a bit of a tragedy of the commons when it comes to decentralization or it's like this creeping phenomenon where people don't actually care about it until it's too late so until this large group starts getting slashed so not something that matters because the performance of the network is running fine and most users probably especially ones not at a technical developer conference are not that worried about decentralization they're worried about you know being able to successfully use their app and right the ethereum network goal is to be incredibly neutral resilient scalable and global settlement layer and the very validator goal you probably have or if you're stating somewhere else is to be performant validator earn rewards and avoid penalties and so right as we've been as I mentioned today the theorem network actually encourages decentralization less penalties for running your own validator node for running your own individual client for not hosting or going through a pool and in general the ethereum community is working across all these points of centralization two ways to decentralize these different aspects so the node infrastructure layer the pools the client diversity the geographic distribution and block construction so these are things and coin distribution this is not a presentation that ethereum ecosystem is like for the first time hearing they're very aware of all these things and working very hard to improve the resilience to centralization and even different steaky providers are trying to you know distribute where they run their notes okay so I'm gonna pass it to Shane from decentralized authority to talk about different node running options right so having an understanding now of kind of the the landscape within ethereum and the requirements for being a runner what options are there for actually running your own nose so actually let me get the clicker from you there you go so no broader landscape advanced users the world is a roister because you know they can there are gonna be some skills required here in advance user we're talking about you understand Linux administration you understand networking scripting docker these are all skills that you have and so because of that you have numerous resources for learning about which nodes you want to run which clients you want to run how you want to run them there's a lot of documentation with every single client about becoming an ethereum validator with them there's no limitation on the location of where you want to host your nose and there's no limitation on the client choice because you can take anything and run with it because you have the skills to be able to do that you can also create custom tooling so your developer your your competent on the node running side you can also develop your own tooling for monitoring for notifications things of that nature so if you're an advanced user there's a lot of options for you out there now the entry level users so these are the folks that don't have all of the all the skills mentioned above well good news there are three different GUI based software options so this significantly streamlines the level of skill that you need in order to run a validator you might be limited on the location of where you can host that validator we'll get into some of that but with with an entry node or with an entry level user you're much more likely to probably want to run it at home you also might be limited on the client choice because if you're using a software platform you're limited to whatever software or whatever clients that software has available to you but the good news is minimal skills required most mostly it's copy and paste with anything that you know any commands that you have to do it's just copy and paste so there are really good options out there so that's what I want to talk about entry level so this is a cerium I believe it's pronounced this is a very cool option it's I'm categorizing it as a remote server control control so what you do is you can actually install their application on its cross-platform to so Windows Mac Linux you install it on your on your computer and then you can connect it to a remote server they have a very simple tutorial on like setting up a remote server with different cloud providers but really what happens is after you just sign up for a server you can actually point their application to that server and then the application takes care of everything and it actually does it through a really cool technology called ansible so it basically is able to send send commands to the server to set it up perfectly for you the good and so with this kind of setup entry or skill wise you can be an office they have great tutorials it's very simple to set up time wise you're looking at maybe about an hour or less if you're following their tutorials it can be done very efficiently notable features it's got a complete GUI user experience everything's in-house they're not using third parties they built everything internal it's a really great suite in that sense I get a lot of patient freedom because this is a remote node controller you can host your node really anywhere on any kind of provider and so you really have a lot of location freedom you have extensive client options they do a great job with giving you tons of different client options so you could actually take a look at those charts that you were showing on okay which ones are over that 33% and you most likely don't want to be in that group because if something happens so say you're with prism and something happens to the prism client there's a mistake in an update what have you what happens is if they're over one third that whole group is going to start getting slashed so you want to be in a smaller client group and that's actually what's brilliant about how theory is designed is a one-client diversity so that you don't have the whole network hinging on one client another platform of auto this is a really cool platform it's different than the other one because this is a hardware platform so this is something where you have to actually buy their hardware in order to use their software so it's kind of like that complete package which is great for some users where they just want to buy it and have a real easy kind of point-and-click setup but you know you do need to buy their hardware you can't just use it on your own hardware you see and you also don't have hardware choice but skill level wise novice very easy to use we're talking an hour maybe a little bit more it's a little bit there's a few more steps in it but it's still a great user experience so notable features is there's no OS configuration because you're buying the hardware you don't have to set up the OS it's a full package in that way they also have a really impressive app store where you can deploy notes from other blockchains or other clients and it's really cool for validation though from my understanding I think there's a limitation on what clients they currently offer for validators so you might be limited in your client choice with a platform like about it until they add more clients that can be used as a validator probably the most popular that people know is that node so that node it's a server platform so this is one where if you have your own server you can set up and run it skill level wise I give this a moderate and the reason I give it a moderate is because there's a lot of options so for some users having that that amount of options to actually be something that is very intimidating and so but there are some great tutorials that you know can take people through you know setting setting everything up for a dat node it takes a little bit more time because there are more options there's a few more things you need to set up but their approach is really cool so notable features wise they have this modular approach so you can choose you know different monitoring tools that you want to use with your with your node and they have a really cool way of just being able to kind of create this this way of just deploying different packages as they call them deploying different packages that are kind of part of your validator suite if you will so there's a lot of customization there they have a very simplified OS installer so you can actually install it from a one to image that they provide and just streamlines the whole process so there's less that people have to do they have a very impressive app store as well far beyond actually nodes they also allow you to host your own dApps and things of that nature and so there's a lot of options especially in a theory of the ecosystem there's a lot of options that you can do it that is a very impressive platform and it's advanced user friendly so advanced users can actually do a lot of modifying there's a lot of kind of there's kind of this like tweaking community inside of that know where people are able to set things up in a certain way you know she's certain goals and so that's a really cool advantage to being kind of this platform is there's places you can go far beyond whatever's in the just in the gooey itself so no software is the best way to decentralize and that is my argument and the reason I'm saying that is because no software can encourage anyone to run validators from home you don't have to use a cloud platform if you can easily and simply run validate your notes at home it ensures that updates and best practices are being applied so it's if they say someone wants to run a theory validator but they but they don't have software options they're gonna have to go through these very complex tutorials on trying to copy and paste all these commands into you know terminal in order to try to get it all working but they don't know exactly if everything's working properly they don't really understand how everything's working that's actually where no software can come in because it can standardize how things operate and ensure that best practices are being deployed when you deploy the node when you deploy a validator it also simplifies client adoption you know ultimately if you have options inside these software platforms you can choose you know which clients you want to use ultimately that's where software can go and software can make it just really easy for people to pick their clients and pick the small ones and the unused ones so so what are some challenges to developing no software if that's kind of one of the key ways that we can really encourage people to run at home what are some of the challenges well it requires full stack development skills so we're talking back in the front so you have to be really familiar with the whole back end you have to be able to deploy notes understand doctor or if you're just deploying them directly onto the OS there's a lot that you have to figure out on that side plus you have to worry about the front end so you really the software has to be really a full stack software in order to really be able to meet all the requirements to be a good running no software we're also talking about you have to have a deep understanding of no running itself you have to understand the best practices you have to understand what your software needs to look for XYZ while also you know right brain left brain you also have to think about the user the creative side of figuring out user experience what we'll engage users will make them want to use your software so you really have to have a deep understanding on both sides of that minimal no tooling is there's minimal no tooling that's kind of weird sense but minimal no minimal tooling is out there for people who are wanting to develop no software that's just kind of the reality of where we're at right now so it's all one I want to develop no software you're kind of starting from scratch you've got to develop everything on your own with all this understanding and so that's those are kind of the challenges that we see right now in getting more notes software out more people but I didn't really give an introduction to decentralized authority what we're doing is we're developing software in specifically no software and so I wanted to talk a little bit about how we can see the no landscape changing with no software with tools like no launcher which is a type script no deployment engine so no launcher is an open source no deployment engine written in type script that enables the easy creation of no development applications so if someone wants to create a application that is for running knows what no launcher does is it allows them to start developing that application without needing to understand the back end because it's a full deployment engine it will deploy the nodes in the proper way using API's the features those can be deployed and controlled through standard API's you don't have to know how to deploy something on Docker all the proper Docker configs all this stuff you just simply need to be able to understand a type script API which type script is amazing for application development and you can be off to races to develop your own no software you are able to programmatically deploy those and upgrade them to validators so one of the what does programmatically mean here in this case like with the other platforms that we showed there's there's there's manual steps that you have to take in the in the process you either have to copy a file over here you have to you have to save this you have to do you know so there's in the process of deploying a note with those other software platforms there are certain processes that require human intervention programmatically means you're able to do this entirely through programs so you can actually have all the elements that would require you know a human to copy this over here to do this over here you can have that all done in a programmatic way so it creates a much more seamless user experience and you have way more control over the nodes and how they're configured because it's all programmatically designed you have seamless client updates with no launcher if there's a new client we and it's actually ties in with this point down here we have a client test suite so I'll kind of tackle these in a scenario that's happened recently where we have a client test suite where when a new client comes out we're able to test it against this library to make sure that nothing breaks inside of this library which node applications can use well earlier this year the geth geth nodes came out with a new version that actually sunset a configuration and it wasn't like widely used but it was a configuration in there but it wasn't in the release notes so we actually put it through our testing or our test suite and we realized we were getting all these flags we reached out to them like oh yeah they were you know sunsetting this you know but it wasn't in the release notes so there's there's there's elements to where you know either on the client side they can just make an update to something not realizing that other people might be using different configurations that would affect that this is where no launcher comes in by this can actually eliminate so eliminate that attack vector or not necessarily attack vector but that slash event where if there's a problem with geth and there's a feature that people are requiring and that's suddenly taken away and it's not realized how widely is used no launcher would catch that before the upgrade happens so that's the advantage of some of thinking thinking holistically about the back end of running those so this is an example of what a simple API could look like so for for application developers this is what you need to allow your application to deploy a theory value for the developers out there this is simple this is super simple you're not having to touch Docker you're not having to touch anything on the system the library itself is doing everything for you in the back end with best practices and this is all you have to add to your application so no launcher is it in use yes it is no launchers been well battle tested through no pilot no pilot is a consumer facing node management software that we've been developing we're currently in beta we're hoping to come out with version one Q one the next year and make it fully open source so far thousands of nodes and validators have been actually launched through no pilot so it's been heavily used it started off primarily in another network pocket network which actually serves RPC calls to a theory application so it's a really cool it's really cool synergy there but but the interesting thing about no pilot is the fact that no pilot is 62% CSS 25% SCSS and 13% JavaScript so we're talking about like a web application but yet it's able to run and deploy nodes and create a user interface and user experience that allows more people to have access to node running and it's just a simple application ultimately with no launcher any developer can start creating no deployment applications like no pilot we want to open up this space so that there's innovation happening on the user side of node software because we want more and more users to be attracted to the space and more user can be attracted to the space when we have these kind of when we have these kind of software that meet different users with where they're at or the features that they're looking for we can see that innovation start to grow with tools like no launcher and so we've actually begun testing no launcher with Ethereum no launcher we successfully launched a test net Ethereum validator last week using entirely only no launcher so we're very excited about that we saw some refactoring to or we were in the middle of refactoring I was talking to the dev yesterday he's like well yeah well the version right now has some bugs because I was refactoring and broken so right now what we currently have in our github is broken but that's the beauty of what we're doing is we're we're we're building it out and we're and once we're ready to make a production ready it's in a right now it's in its own dedicated branch but once we push the master then anyone could actually use no launcher to create a validator for Ethereum. We want to add multiple clients by the end of the year development progress can be followed on our github which is no launcher decentralized authority github and we hope to see developers use this tool or use tools like no launcher to create next generation of software where a super user focused super super feature rich so that it can attract more people to want to you know if they're considering hey should I put my should I put my stake in a staking service which I run on my own it's just so simple to run on your own and there's so many options for running on your own that you don't even need to consider giving your keys and putting your trust in someone else. So kind of in conclusion then with everything that Maggie talked about and then what I'm kind of closing here with in conclusion Ethereum is designed for optimal decentralization. It's really designed to push folks to decentralization by having those large slashing events where if you're part of too large of a group you know using a certain client or on a certain cloud provider you'll start getting slashed. There's an issue there. It really incentivizes the run at home decentralized kind of ecosystem. Validators can protect themselves by potentially from potentially large losses by avoiding over saturated cloud providers. AWS 53% it's starting to get to a point where it's a risk if you deploy on AWS simply because if something happens there even if it just goes offline they have a DNS error you know and something goes offline which happened last year they had entire data centers going down because an admin accidentally pushed a patch to their DNS that broke everything that you know those kind of those kind of simple things could actually affect the entire network. So it's becoming a risk to be on these large platforms and then use clients with less utilization in the network itself right now if you're using prison or lighthouse you're in that 40% range. So if something were to happen to either of those clients you could potentially see large losses. But the good news is there are great options for entry level users to participate in the Ethereum validation. I definitely encourage you to go look at those options they are listed on ethereum.org when it says stake ethereum and they talk about different options. All these options are there because they were open source all three that I mentioned. They're really great options. There's no reason to not run your own theory note today. But then kind of looking to the future we are very excited we're very bullish on where no software can go and the kind of user experience that can become standard for no software. And you know we're excited to be working on our side on the tooling side whether your cloud is working on the infrastructure and hardware side. So really the future is super bright with Ethereum validation we want to encourage everyone to run their own Ethereum nodes on their own. So that's thanks for joining us. I think are we doing like a Q&A because we have like 12 minutes do we have 12 minutes. Okay. Yeah. If folks have any questions about any of this let us know. Yes. Yeah. So so specific. So I'm not a developer. So how exactly no launchers are Yeah. No launcher is dealing with secrets. Yes. What we what we do have is the RPC password for those nodes are actually being stored in memory. So there are elements that are being stored in memory with no launcher and so they're not in plain text. Now we're still developing Ethereum and figuring out how are we going to handle all of you know handle everything handle all the secrets but we're building into node launcher ways to protect from having from having you know plain text anything on your server because we feel like that that's where no software should go to where there's a lot of security around how you're what's being stored on your server and how it's being stored. And so utilizing something like memory is one way that you can put the password inside of inside the memory and not have it be sitting on your server itself. So the RPC password. But you can actually check out the GitHub as a developer and you could figure out how a lot of that's working. So I'm not a developer so I can't get into all the specifics about it but that's kind of a general understanding of what we're building towards. Thank you very much. This was really useful. So two questions. One. The only thing stopping me from running a node at home. I mean like locally is that I don't have a good connection. I live in a very remote area. So perhaps I'll do I don't know update on the best like set up for that. And the second question is if I don't have 32 ETH and I want to run something at home is there an option. So so to address the first one if you have bad internet so how penalties work in a theory of for being lazy right. This is either you're offline or you're not keeping up or something of that nature. The that's considered a penalty. So what a penalty can be is it can either be a reduced in rewards that you receive or it could actually be where what you would have gotten if you're operating optimally is deducted. So your slash very small amount. So say you're so in a day you know maybe your internet goes out for 30 minutes or something like that. You're deducted what profit you would have made in that 30 minutes. So you lose out on that those 30 minutes of reward. But then it essentially is almost like you lost an hour right of rewards because it's deducted right. So so that's where you can kind of gauge you know you might not be as profitable even if you're in an area where your internet kind of cuts in and out or something like that. You just need to kind of gauge what that might look like. And maybe it's worth running a validator on one of the test networks to kind of see what the performance is like to see okay would this be profitable with this be worth going. But then there are you know solutions and I'll mention Web3Cloud that are putting putting a lot of work into getting servers and getting hardware into different parts of the world into different regions that are kind of outside of the you know cloud gig so that if you really do have that internet there there will be options where you can deploy you know to to hardware providers that aren't tied to that same like cloud cluster that we were talking about earlier. Was that both of your questions? Oh, if you don't have 32E. So if you don't have 32E that's your you can still run those you so run those you won't get any rewards for them. But you can you know there are other staking pooling options like Rocket Pool is a is a good one. Also if you have friends that trust you then maybe you can aggregate some people do aggregate ETH amongst groups of friends who may not have enough ETH and then you know adding a point of trust but it's an option. Yes, sir. That would be the case I would say if if no software was being taken seriously. So with no software people could minimize a lot of cost and and also minimize certain risks by just running at home. So while yes, you know, you could have, you know, large providers like AWS, you know, it really comes down to, you know, six providers as you mentioned right six providers. Sure, you can go that way and send money each month, or you can have an old laptop running where you're keeping all the rewards and you don't have that overhead and it's that simple to run that. So I think you're right in terms of just what tends to happen in these kind of ecosystems. But but I think because of the way that that theory is approached through such a state where they intentionally put in mechanisms to incentivize more and more decentralization, I think the market will will match that. Right. And I believe there are going to be a lot of options for no software in the future. There's already three great ones out there. We're building one ourselves and we're building tools that allow more people to build them. So I think the future is really bright with that. So that's my thought. May I ask if no launchers capable to integrate the dbt no department? I'm sorry, what? No department? dbt? Disgeputed by data technology? Something like that's what I'm not particularly familiar. What no launcher is in a really simple term is it's a it's actually like an API engine for Docker. So it allows you to put type script commands, and then it automatically converts it into what will be either sent to Docker or sent to a container inside of Docker. So because of that, yes, like it that no launcher could actually be used for any container, any container system, we're focused on nodes, because that's our focus. But you can actually use no launcher at basically JavaScript API to build any kind of container based node infrastructure or container based application or management. So it's very adaptable. It can apply to any parts of the node, any parts of any container. One of the things we're building right now is the ability to deploy multiple containers. So there's some like polygon that require multiple containers, right in order to run their node. It's actually multiple nodes. So we're building in that ability to have all those nodes all orchestrated and working together without needing to do it manually because it's all handled through the engine itself. Thank you. So there are so on ethereum.org, there's all that information. So definitely check it out there. From what I remember from looking at last night is they recommend kind of on the low side or on the recommended side was a i7 4470, which is like a 15 year old processor. So so yeah, I said from like 15 years ago or something. So anyways, yeah, ethereum is very well equipped for minimal hardware requirements, unlike a lot of other networks out there. No, you just on the server itself needs to have those requirements, which are very minimal. And then their application, I believe you can just run any computer that's running either Windows, Linux or Apple or Mac. So got two minutes. Yeah, absolutely. Like so we don't have to integrate right now. I was actually just talking about it yesterday about it. We don't have it integrated now. But it's literally service that you run alongside your theory validation. So it's a container. Yes, we can install it. And that's what no launcher does makes running containers super easy, and able to do it in a programmatic way to where it all automatically connects. So yes, maybe it's absolutely possible. Hey, um, sorry. Yes, thank you both for for the talk. Um, I been running with my own hardware, wanted to get like a recommendation on like, when the setup was pretty complicated, like you mentioned, like the resources from the theorem foundation, then they point to a random guy's medium post, and another random guy's medium post, which is not updated, or how do I know if it's a day or not. And good luck if you want to run any that are not like gif and like a typical combination of prism or like, right, like the limitation for anything that's not like the main ones are not existent. So um, first question, is there a source of truth in documentation, which I can follow like, to set up my own hardware we do to server, and like go through it. I mean, I'm not not no machine or anything, but like I can. Yeah, I would eat that work is is the best place official Ethereum documentation from the Ethereum Foundation is probably the best. But also it also depends on the client that you're using. So different clients do have different hardware requirements from my understanding each client in their documentations, specifically state what their hardware requirements are. So I would actually look at the documentation for the client and see what the requirements are for that for that. Now, the one thing you do need to be aware of is as Maggie mentioned, you have to run a execution client, you have to run a beacon client or consensus client, and you have to run a validator, which is really just a consensus client. That's only job is to be validator. So you have to run three different clients. So even though maybe the the one client has certain hardware requirements, you have to also look at what other clients are going to be using. And then you have to, you know, bring it all together. So I would say go to the clients documentation, figure out what each one is after you decide what you want your makeup to be. And you know, use the information that Maggie gave you in terms of the usage on where how how utilizing clients are to make a decision. Cool. And just one, I don't want to put you in a tough spot, right? But for the sake of decentralization, is it am I better off like going into, well, I don't think I could go to that note or about it because I'm running my own hardware, but like using something like stereo, or am I like exposing myself to a to any to any risks? If I go like install everything myself? Well, for one, you can use that note on your own hardware. So that of auto is the only one where you have to have your their hardware. So you could actually on your own server use that note. But I can't really speak to actually the ethereum.org they actually do give in talking about these different options. They do list out different features or different elements to them where like some of them have been audited, right? Some haven't, right? So you could actually potentially use that as a way to gauge. But you know, most of the time was something like, yeah, you know, it was stuff like both that node and cerium, you know, they're your those aren't things that are exposed to the public, right? So the application is just sitting on your computer and then that's connected. So if your computer would be hacked is how serious it would be hacked. So the app would have to be hacked from being on your computer to be hacked. So there's going to be a risk no matter what options you use. But yeah, there is some information on the theory network or the theory about that. Great, sharing money. Thank you so much. Thank you, everyone, for being here so early in the morning. As I mentioned on last day of com, you can follow us to stay up to date on what's going on with no launcher. And if you're a protocol looking for no software or even hardware infrastructure and want to decentralized, you should contact us because that's what we care about what we like to do. So thank you so much.