Community Call #13 with the Status Nimbus team about their low-resource Ethereum staking client

Transcript

[Music] [Music] so [Applause] [Music] [Music] [Applause] [Music]

[Music] [Music] [Music] [Music] [Applause] [Music] [Music]

[Applause] [Music] [Music] [Music] [Music]

[Music] [Applause] [Music] [Music] [Applause] [Music]

[Music] so [Music] [Music] [Music] [Applause] [Music] [Music]

[Applause] so gonna hop in live is that if that's all right with with nimbus team great um so if you point to me michael when you start the timer then i'll count down in my head and then i'll do the introduction is this call number 13 yes did you point hi everyone i'm super fizz from the eat staker community uh today is december 14 2020 and we are here with

east staker call community call number 13 and we are here with the status nimbus team who develops the nimbus beacon chain client and validator i'd like to introduce everyone really quickly and then we will get into the meat and bones of the call with me this morning i have um two of the eat stickers that is michael michael you know as as anvedica and patricio werthalter who is also the mastermind behind poep um and i haven't been involved with this but i assume we have for today right yes we do um maybe you should tell them how to get it which is uh paying attention to the private

messages great sure so during this call um patricio will be looking through the participant list and he will be sending you a private message that includes a link to coach.xyz and when you click on that link it will open up a page where you can claim your poep if you have any trouble with that we'll get you taken care of the best thing to do if you have trouble is to stop by either the poep discord or the east stake or discord after the call and so with that i'd like to welcome uh status or nimbus and um i see zahari sasha and mammy here this morning so sasha if you'd like to just kind of introduce yourself and share your team with us

we can get started um all right so i'm mainly on technical writing and user experience with nimbus and uh yeah i mean mommy's mammy and zahari are the ones that are really and the rest of the team are the ones that are really making this possible i'm just kind of the the mouthpiece but that must be how we connect it because i'm i'm just a talking head too like i i didn't mean that offensively to you but i i am just a talker so yeah um we're glad to have you uh zaharia miami oh i would say that uh sash is also the

person who makes it possible for us to have actual users because thanks to his effort great and uh can you tell us a little bit about so well let's let's say mamie hello how are you this morning so i guess it would be good good to begin with with what your role is what your individual roles are on the nimbus team um and so uh zarya would you like to give us an idea what what your role your overall role is well within the nimbus team we don't have uh much of a hierarchy and we are pretty flat as an organization both me

and mommy are just developers on the project um within everybody has developed quite a lot of the individual subsystems within nimbus i it would be too many to list them right now but we try to be responsible for the components that we have developed cool great um and if you wouldn't mind um so one of the things that we're always interested in especially like home users and home stakers is how you found yourself uh like what your background is that led you up to your because i know we have a lot of um a lot of aspiring developers who are

curious like how did you find yourself in this position like what's what educational background or what other jobs have you had that have led you to where you are well our project is unusual because it uses this rather exotic programming language called nim it's not very widely known but it has many interesting properties when you develop software with niem you can achieve the performance characteristics of languages like c and c plus plus and for example rust for example uh but at the same time you get to enjoy much more high level language products and you can create apis that

are very easy for others to consume so this language is not very well known but it's been around for more than 10 years and actually i was one of the early contributors to me i've been involved with the language for more than eight years now and pretty much that's how i end up in status when they announced that they will be making a new project it was very obvious for me that i should apply and should learn everything i can about lithium so i can help this project move forward and for status it was an obvious choice to fair veterans from the nem community and

that's what our team is so to speak we were able to hire the most uh productive most prolific open source contributors from the main community i've never worked on a team like this before where each and every member of the team has very strong github profile with many many interesting projects and uh just to get back on the uh aspiring programmers who wants to get into ephraim 2. so um the team started in january 2018 with a reddit post in the nim subreddit

jarrad the ceo of status posted a job offer and people applied and that's how the team got started and then so that's how i replied and i assume zary too and then zari recruited like half of us and we are about 10 now we have very differing background some of us like zari did game programming than compiler development myself actually that's my first job as a professional developer but i've been doing a development in neem for two years before 2018 and in the past i was a sysadmin in

finance and then in non-profit so i went into different areas and i have a mechanical engineering degree so the most important thing uh for us in the team is uh showcase your uh portfolio and show that you can develop application and project and you can do it step by step uh you you cannot start with something complex right away but show that you can deliver that's the most important thing i i love that i'd advise i i see a lot of uh of interested people who are so so willing to showcase their

ability but have difficulty actually delivering a product so that's that's excellent advice for anybody who wants to get involved with with any project thank you um so can you give us a background about uh what is unique about nimbus so you know we have four um i call them launch clients or four beacon chain clients available right now and one of my biggest interests in promoting nimbus is as far as i can tell right now it doesn't have as large of a market share as some of the other clients and my interest is in improving client diversity

and so if if i were to ask you to sell me nimbus how would you how would you sell it to me well a key differentiator for us i think is that um we didn't have so many foundational software on which we can build upon so we have to write pretty much everything from scratch so this means that we get to build the components in the leanest way possible they are lightweight we don't have any excess fat we get to know [Music] the system as a whole we get to optimize the different parts so they work

in synchron with each other and the end result is and we spent quite a lot of time trying to avoid complexity in the system so we put some additional constraints upon us such as working on a single threat that have forced us to optimize the software in different way than the rest of the clients and so the result right now is that we have some advantages when it comes to memory footprint we use less memory than the other clients and i think uh soon rather soon we'll be able to capitalize on our single thread architecture by introducing just enough just a little

bit of multi trading where where it matters so to get both the high performance and the lightweight design at the same time and that's that single threaded design is is pretty exciting or at least the light footprint because it gives you the opportunity to um install on a wider variety of systems and architectures what are some of the interesting um and so i guess i'm asking a leading question because i first became my first install with nimbus was on a google pixel phone and i it was i was delighted to see how how smoothly it ran

um can you share some of the other systems that might be a good match for nimbus so for now obviously uh arm 64 and raspberry pi are a main target but uh we don't want to exclude in the future things uh that like routers now they ran on maps and so there are a lot of mips hardware and even um in some smart tv there are some stuff like this i can't say uh you should run ev2 on that but maybe at one point there will be a need to just monitor the beacon chain so might be but

for now i guess i'm 64 and in the future it's no secret that in studies we really like open source open hardware and risk v5 is an open address as well so maybe we will look into that but yeah just as i said it's like maybe five years six years from now who knows what the future is yeah that actually that makes me curious like um and maybe you're not able or ready to disclose it yet but it seems like you have this very tight compact client that can almost fit in a smart toaster um so what what is are you able to tell us what what you're

aiming for in the next five years with that or are you are you literally just feeling it out right now um it will really depends on phase one and phase two but you can imagine that in the future you have a point of sale unit like they use to use credit cards we have the key cards or status and maybe we'll be able to install a small nimbus library to to serve as an endpoint if if two becomes something huge sure that's exciting because that that makes me think of uh there's a whole lot of product potential

so are there trade-offs have there been have there been sacrifices are there sacrifices in the beacon chain client and validator that make um nimbus work or is it as fully featured as the other clients um there have been sacrifices in terms of time because uh unlike for example uh some of our clients that already had a goalie p2p or rusty p2p we had to develop everything from scratch uh which we shortcutted by hiring a li p2p developer but we still had to develop everything from scratch

this has uh two implications one time it takes a lot of time but the benefit is we control everything and auditors in particular really liked that because they knew that they didn't have to dive into a tree of dependencies that couldn't be audited when you okay everything is there that's good that's exciting so i i get that it can run single thread it can run on raspberry pi um and it has a low memory footprint can you talk to me about the data as in the data storage as it compares to other

clients and then the bandwidth as it compares to other clients well i think in data storage in particular all the plants still haven't reached their potential i mean i know that we are comparing to compare can can be compared relatively well against the other rights now but even we are very acutely aware of how inefficiently we use the storage right now so this is an area that will be focusing in the next month and i think all the people in the community in the staker community should expect dramatic improvements on that front okay so um i guess if we're to rate these

categories in terms of processor and memory footprint nimbus is probably a leader and in terms of data storage you suggest there's a lot of work to be done how about in terms of bandwidth usage so just to go back on processor and data storage for example one of the issue that we have right now and i think most of the clients are working on it is we don't have pruning which is a problem if you store that up for three monthses or so and in terms of cpu i think we are pretty good on uh single thread but as many i've seen the sync report we are still have work to do for initial

sync uh six months is from now there will be a fast sync called weak subjectivity sync and this means that sync speed wouldn't matter but since we have we don't know uh when this will be available well clients have prototypes but we don't have a way to provide the checkpoint securely right now we are working on sync speed and this goes through multi-threading which is a pr that i'm kind of shilling right now in the nimbus uh discord channel and we hope to have this um like uh a week from now in devil and three

weeks from now uh released in mainnet hopefully uh and for bandwidth it's more of the area of zary so i let him respond to that well in the bandwidth side you can say that the majority of e2 traffic is the gossip traffic and i mean we recently brought some improvements and you can actually say bug fixes that reduce the traffic to the levels that the other clients are getting right now we used to be a little bit above them but i believe in order to improve the gossip traffic in general um this can only come with some

optimizations to the protocols which are more difficult to coordinate and a bit less likely to happen i guess so you guys have an open validator i mean when i say open um it's one that you are willing to disclose the index number for us to monitor the performance of it uh yes we operate uh validators i think i believe all of the client teams are running their own validators and uh surely we can disclose this something that we've been considering is creating a status page where you can see how our our fleet of validators

is doing right now and which statistics about their performance that's something the community would appreciate we we have the idea of collecting at least one validator of each client and and also from some staking provider is taking pro taking services um so so we can have some sort of dashboard and see how things are going so so if you ever decide to publicize this uh we would love to have access to that information yes actually thank you for sharing this i mean i'm always very interesting to hear like what are the perspective of the actual users and what they care

about behind the teams and we'll be working on that status page one other place where you can kind of compare class right now is on the pyrmont network which is actually much more heavier than mainnet and it's likely to continue to be this way for a while so you can always take a look at the leaderboards in the pyrmont network for example by scoping it to the last week or to the last day to see how the different clients compare there and there is uh if2.stats.wtf i think to get some resource usage statistics from people who like

who put some of their performance metrics uh uploaded their performance metrics thank you there are other validators that put um numbers in the group and and we did speak uh last week about on our call about putting in publicizing the the dashboard for our validators because i think as as mommy and zahari have communicated because we've had to build everything from the ground up it's the first priority was getting things working and and the second priority is is getting things uh to work fast and well and and and so

it's only really it was only really after the the uh or quite late in the day that the nimbus started working well and and and now the focus is on on optimizing and i think a lot of people in the community may have tried nimbus at an earlier stage where things were were not working um so well so um so i think it's important to to as you said have a resource where people can contract how the how the validators are doing and can see the improvements we've made and that's it's very interesting that you say that because that that is my purpose for reaching out like i i'm under the impression that status is

an equal contender um and i i kind of had a direction on that but i lost it i'm curious like about the installation um i one of the things that is still difficult for many end users is installation things like installing and then adding additional keys what is the workflow for nimbus right now in terms of documentation installation and adding new keys well our book um would be the guide that everybody should be using

right now to get started but this is actually an area where we've been thinking a lot lately we want to right now it's fair to say that operating a validator in ethereum 2 is quite technically complicated it is mostly possible for power users so to speak and we want to make this to democrats that ties it a bit a little bit uh we want to make it very easy to install the big note through for example the packages in your operating system and then we imagine that would be quite useful if you

pair your phone for example due to your nimbus installation so you can manage it and monitor it right from your account or your desktop are those tools available right now oh i mean as i said this is these are our aspirations okay okay okay sure um so you you kind of explained and it does make sense that part of nimbus's lower market share is a result of having to build from scratch where other clients had existing libraries and it seems like nimbus is is more or less on par with all of the other clients now do you is it a mission of your team to increase

market share or are you at kind of has made me said are you focused on that five-year plan where you where you're more interested in future solutions the only way we can survive for five years is to have users now so it's very important for us to have users now understand their needs meet them and uh also as everyone knows the best distribution of clients for everyone on e2 is to have an equal share for everyone so 25 percent uh for all four clients and when uh loadstar goes online uh 20 for everyone because this way if there is an issue

on one client only 20 goes down and there is no like big slashing and finality issues like we had in media or in altona for the old testaments sure yeah and that is i'm so appreciative that you said that because as a as we're here with the community now for people who watch this in the next few days and weeks if you're bringing a validator online nimbus is an excellent choice because uh they're ready they have what i've experienced as an easy installation procedure um and so will someone tell me what happened uh

and maybe you kind of hinted about this what happens if you're running nimbus which is a minority client and something like prism experiences and i'm not picking on prism one of the majority clients experiences some kind of fault what what does that scenario look like as for a home user who who chose to run nimbus rather than a majority client so what happens is that if there are many uh failures uh on uh either inactivity or wrong attestation or block being produced the if two protocol uh will consider that as an attack and then

the penalties will get very very high and so voles being penalized will have a large part of a stake slashed and the one who survive likely we'll slash them and earn more money as well sure yeah we know that even if you're not running a slasher if if you are an online proposer when a majority of the network is offline then your rewards will actually be more significant so if you're running a minority client when a majority client is offline you are contributing to the network health by keeping the chain going you'll have

greater block or greater proposer rewards um and it's it really is beneficial to the health of the overall network actually uh right now running a slasher is really a pro bono thing because only the one who includes the slashing proof actually gets the the reward but in the future i expect running a slasher would also a slasher would also get a reward and i i wasn't actually referring to slashing but and please help me understand this because i acknowledge that i i'm still learning a lot of this if if several blocks or slots are missed by what would be a majority client

and then a nimbus or a an online client then proposes a block um is the reward not higher than it would have been if they were sequential blocks and i it's difficult for everyone to understand so i i'm still learning myself i wouldn't expect you to have the answer offhand no i don't have the answer i would have to recheck the spec and everyone knows the best it is i can talk a little bit about this actually the more the stronger mechanism here is something that it's called the correlated failure so you want to anti-correlate yourself

from the behavior of the other nodes in the network because if many nodes are currently offline the penalty for being offline increases so by running a majority client you expose yourself to the risk that if there is a problem with this part of this client uh the portion of the validators that will go offline at that moment moment will be much larger than if you're running a minority plant so because of this correlated penalties anytime an incident like this happens you'll be suffering larger penalties now i believe there is no difference um when it comes to the block

proposal rewards and actually something that we have we discovered on the media network is that uh even people when people are offline during the periods when the network is not finalizing you are still not guaranteed that you'll be running on profit so the people in the community should really try to minimize the risk of the network experiencing any outages like this and again on media we learned that a technical incident no matter how trivial it is could knock the network out of finalization so i think there's a little bit of

responsibility here to keep the network in good health and i realize that was a shock to many users that they were running active validators that were continuing to attest and propose but because the network was in leakage they also had difficulty maintaining or keeping their same balance and it appeared that they were leaking as well there were some parameter changes after this following that incident um i think it was on altona or wheaty i don't remember exactly but the spec was changed uh this can be checked in in github

sure yeah and i i think if i recall correctly that that meant that if you remained online and were doing your job you would not ideally and you know it's you would not see a decrease in balance um is that is that your recollection as well that's what the parameters were trying to do but it all depends on the very specific way that the incident will play itself sure sure um i wonder um let's say that that someone is watching today i think we have we have quite a few users i think 50 or 60 users um if if one of these people is setting up a validator today

how do you have an outreach program going on do you have uh so i know about your nimbus discord um are you what is the best way for a user to find your community and um become an active learner or participant and that's that's definitely the the discord um i mean there's there's someone online basically at almost any hour of the day and we've split up the channels into quite [Music] detailed subcategories although it

doesn't matter if you get the category wrong but but there'll always be someone there to help that i'd say that would be the main port of call and and definitely check out the nimbus book i've i've posted that in the uh in the discussion but that that's sort of aiming to be a really fast principles introduction into how to validate and um and yeah if if i can if i can confess i i had difficulty when i was googling um to find installation instructions it seemed that there were several different versions of the instructions um so yeah so the trouble is is the documentation on

the nimbus front is spread out between the website the github and um the nimbus book and and it's it's not always and also we've changed the link to the nimbus book um a couple months ago so right now it and we haven't worked on search engine optimization at all so it can be hard to find um that that's something that i i'm realizing we need to do a better we need to publicize that better but basically everything is in the nimbus book which i've posted the link um here but just to read it out loud it is let me just get it up and that that from uh from our discord

is is um is linked so okay so it's status dash i am dot github dot io slash nimbus if2 uh but anyway that's so it's long it's long to remember i'll post it again and i think we'll we'll tweet it out more and and and make it clearer um yeah and so i would say if if you're listening right now uh if you can get that link one of the things that e-sticker wants to do is promote other clients to promote all of the clients and we really want to exercise exercise our agency when we can and one of the things that we can do

right now is is help to promote nimbus installation instructions to help their seo so if you're watching right now if you will find this link and tweet it or share it or post it somewhere in reference to nimbus installation so that we can do a couple things if we get this out on twitter today we're going to increase um awareness of nimbus and we're going to uh improve those google search results so that when people uh are looking for those they're they're going to get there more quickly so yeah we're actually going to i mean just speaking to you right now has been has made us realize how ridiculous the url is we're going to reserve a much simpler url today

and so that that that's what we should we'll get in touch with you and that's what we should tweet out okay so would you would you rather people wait then before no i mean i mean the both of them will work but but it's just you know i think it should be a lot simpler so and that really does meet the the goal of what we're doing here we we value nimbus in the community especially the fact that you run on light hardware we have so many people who want to run on light hardware but they they are only aware of the majority clients and so if we can connect uh their interest in running on something like a raspberry pi with a product that you have that is

absolutely designed for that then i think we can have uh a much more vibrant community so it's good hey so harry could you tell us a little more about nim the parameter language for example which is the most successful application using it well nim tries to be a general purpose programming language but there are some communities that are where it's already a little bit more popular you can say and so far i think uh the game development community has uh has much stronger interest and i see there is two reason main reason for this first of all

in the game development community it's always many games start each project from scratch so the development teams get to pick the their technology without being so [Music] kind of forced to use legacy solutions they get to select what to use for each project more often and as i mentioned previously nim has quite good performance characteristics and that's something that the game community as well values pretty highly and it has also this high development speed where you can work with very high level

abstractions and something that the rich and complicated simulated worlds that are common in the game development community also benefit from not knowing anything else about the language um it kind of makes me feel like a nimbus is likely the most critical application running it yes definitely i mean as i mentioned we are one of the first large-scale projects using nim and i think at this point we have proven that the language is capable of delivering production software so yeah are then you're afraid of upstream

vulnerabilities um we are taking this threat seriously and um it is something that the audit team actually pointed out that our in-house libraries are considered a higher quality than the standard library of meme that's what our auditors told us and actually it is quite common in our project that we even avoid the dependencies on the standard library we many of the even the low level components are developed in house with this character our security and um

yeah i was more thinking on on the compiler well the compiler i used to be one of the core power engineers for volunteers in the nim community but i was quite involved in the the compiler development and there are many the nimcom power is very complicated you can say because the language has many features but something that's good to understand is that the code generator this component which is dedicated which is given the task to produce c and c plus plus code because that's what means in compiles to it's somewhat more

sim more simple component which haven't been seen a lot of bug fixes for many years now it's relatively mature so nim wild and language has a lot of issues they tend to be on the um what is called the front end of the compiler something about things like uh the semantic analysis of your program the type checking when the what the error messages when you get to see when you use some name feature incorrectly but once the code reaches the stage when it must generate c code i think the number of bugs we've seen in

the last few years is not so significant this is very interesting um i don't want to extend very much we can't talk this any other time um just uh for five seconds uh since we generate c code or c plus plus code uh the auditors are checked also the c code generated for bugs and we can use all the debugging and sanitizing tools available for c in nim and what i was discussed when you said well the language is quite complex and box hasn't been found and it may just be that the incentives weren't there for for very intensive auditing

or very intensive back hunting but i i still consider that you must be very qualified professionals and you are awaiting all these risks and and eventually uh when ether is uh ten thousand dollars each so running a validator is more than a quarter million dollars maybe um more resources can be allocated towards a really comprehensive and div analysis to have complete coverage and visibility of all the stack and and although at the same time i don't ignore that all languages are also exposed to different vulnerabilities it's not only about complexity or or popularity um so so

something important because we have 20 minutes 20 minutes left these community calls are open to everyone who wants to interact with our speakers and with us so i'm going to try how we open mic on zoom position just to clarify just before on on your point we do control the compiler as a dependency and we are sponsoring the language and and kind of the best nim hackers are uh you know the people on the team were originally hacking on the compiler and so on so there are very few teams that actually have such a symbiosis with the language they are

using that's cool that's really cool um i have i i feel like i um i don't feel nimbus is in any way handicapped compared to other client because of the language choice um i'm computer science it's computer science and distributed systems are such complex fields in science that um you can't always have complete coverage and hedge all your risks and i'm sure you are doing your best to to have a reasonable uh threat modeling and and have coverage on the different possible attacks

i would like to so why was yeah i was just gonna ask something real quick cause i think it'll be a good segue into opening up to the community and i think it's pretty obvious uh across the length of this over this discussion that uh you we're lowering the bar by adopting nimbus in the sense that more devices will be capable of participating in the network so i guess extending that out sacha i was reading your article about thinking hard about validator privacy you know as as we get more adoption and as people participate more within ethereum and become validators that that brings up

a good good question about validator privacy you know it sounds like that it's all too easy to identify um people on the network so are there things you know asking you directly or sort of the team that we can do as solo stakers to sort of prevent accidental doxing or identifying ourselves or just general security tips that we can deploy ourselves do you want to take that mommy i mean i can speak more to um the areas of research we we might need to pursue and how the spec might need to you know how we may need to consider um the trade-offs between how it's

currently um works and and what you would need to have a stronger privacy but i think mami can talk more to to uh what a staker can do now okay so there are two areas of privacy i see in if2 the number one is your ip hiding your identity and number two is hiding that you are a validator and that you will have to propose a block or a test soon so number two needs to be fixed at the protocol level uh thinks that the ef uh is researching like a secret leader

election so that you only know who will be the leader or the proposer at the very last minute and regarding your own ip it's uh similar to how uh if you use uh other p2p application uh you can use a vpn for example but that moves the trust uh from your um isp to the vpn provider so you need to select the vpn that you trust for example because all your traffic will be rotated through it and it require visibility to it so there are traders uh we are deeply

aware of that and even as an organization uh status is very very focused on privacy first censorship resistance so even we will likely be using uh the research team that we have on uh private and censorship-resistant messaging to leverage and to provide the same research on each to privacy as well oh and i want to also mention that solving validator privacy was one of the aspirational goals of ethereum 2 when we were getting started

and i think only due to the complexity of evolving the lipid we protocols in time we didn't weren't able to get a fully satisfactory solution yet but the protocols should continue to evolve to evolve so we can get more kind of automatic out of the box solution that the individual validators shouldn't don't need to worry about let me say that's one of the trade-offs for shipping if two in 2020 yeah one thing i would add is is if you

haven't made a deposit yet is is to perhaps try and break the link between your if one address and and and your deposit you know so use tornado cash i think it would be cool as well to push for a 32 beef option on tornado cash i don't i think there's a hackathon prototype that someone did and i think that was originally the plan but they didn't for some reason didn't get around to to implementing in time but that would be really cool i mean right now it's like 110 or 100 right and 32 could be used by a lot more people i think than just um stakers so it could be useful and that would be a great way to annoy them on twitter um they

they did sort of tacitly commit to trying to get 32 ether out in 2020 a couple weeks ago but if you're a twitter warrior it would be great to add them and and kind of encourage them in an annoying way thank you for suggesting that that it would be so neat like that's something we all want and tornado cache is already a great product and that is a great product and a great use case that could be merged very easily uh with that i think it's great i i believe that everyone has uh all of the participants have unmute capability um if you can't uh that's fine we will

figure it out but if anyone has any questions we have uh a few minutes and i'd also like to talk about poep before we close but i don't want to take anyone's question opportunity away so we'll give it just a moment so i'll chat about poep if if no one else is uh is piping him with questions um co-op is the proof of attendance protocol and patricio worth halter is the developer are the organizer behind poap he's kind of a diffuse kind of leader and he encourages people to do uh whatever makes sense to them with

poep and it's one of the reasons i love the platform hoep is essentially an erc 721 token that gets uh delivered individually to people who can prove that they participated in an event and the delivery is free they are delivered to the xdye network which is a a side chain of the regular ethereum network um and that delivery is free so when patricio sends you a link and you go to the co-app claim page and you enter your ethereum address it will be delivered to that ethereum address on the xdi network from there you can you can leave it

there forever i leave a lot of mine there or you can actually migrate it to the regular ethereum network if you're interested in learning more about co-app you can go to uh well actually my favorite place to look at them is poap.gallery right now you can check out matricio's medium uh blog it's it's under poep xyz um or you can learn more at app.poac.xyz it's something that the east acre community has really gravitated toward um and if actually uh michael who you see heroes and vatica runs the ethereum studymaster.com program and the uh you can essentially participate

in taking reading 10 articles and taking 10 quizzes and getting a co-app to um to prove that you have some fundamental knowledge of eth2 so all of those things are really great and and we can make a little announcement and it's not really an announcement but it's a status update um we are in advanced conversations with ethereum foundation uh to give benefits to people that have certain co-ops like the medasha resuscitator and and the genesis validators and and maybe even these community calls so if you were a passionate community member that's

been dedicating energy and resources to ethereum um you may get uh from simple things like exclusive swag during devcon up to free tickets or or other interesting benefits on on the activities the committee runs so although pops are collectibles and the main value proposition is just giving you proof that you've been part of this um there are actually um branches or the benefits branch out um so so stay tuned uh follow it stay here on twitter and and pay attention to the channel on the instagram discord which uh if you're here i assume you know but in case you are watching on youtube

it's uh the way to get in invite dot shishi slash eth staker all together and and i guess that's it that's the the our kind of status update on what's coming so i i don't want to take anyone's opportunity to ask questions um but hey michael are you able to give us an update on the genesis poet voting yeah uh so uh later at some point today we'll have the uh e-staker website will be updated which is uh east acre dot cc and uh when that gets updated we will have the uh

poep genesis design contest event where we had something like 158 submissions uh individual poep designs from designers around the world that designed three exclusive genesis po-ops ranging from the depositing 32 eth as a validator to proposing blocks at certain certain time stamps so if you go to eaststaker.cc you'll be able to vote for the genesis co-op that you think should be

distributed uh for those uh various uh i guess i don't know categories for co-ops so um but again that it's just later today right yep yeah by the end of day let's call it uh 7 p.m central time that's 12 midnight but michael has done an extraordinary job um developing all of these tools for us and um so anyone who you know is itching to get those genesis co-apps please recognize it takes a lot of work to get this kind of thing up and running um and so i know petrucho has been laying the foundation for years

and michael has been helping to get this ready to go so i'm really delighted for both of their efforts i just put on the zoom chat a message to the gallery page of this event to see who got the pow up it's 58 people which is a nice number um but thank you very much everyone who came and joined and hopefully you also enjoyed it as much as we did we also have another community call i think it's in eight hours is that right that sounds right um seven seven hours and five minutes i think anyway that that call is with dave reagan dyke and we plan to talk

then about the next iteration in uh trustless decentralized staking pools so if you're joining us now you might also be interested in joining us for the dave rugendite call so status team or nimbus team any any final thoughts um it sounds like you have a a very well working client for light hardware that many of our especially raspberry pi stakers may be interested in using any closing thoughts i i think one thing that perhaps we didn't mention was

was the idea um is to integrate it with the status desktop app next year so you'll be able to monitor your your validator through the status desktop app that's that's uh something that's important that i don't think we've communicated properly yeah um also maybe some people knows that we have an if one client that is currently in progress and can sync slowly but to the latest channel um the plan with this is um many knows that we have to run uh geth or something uh we want to integrate that with if two so that you can have numbers as a wine

binary that can monitor the f1 contract and run if two that's something i'd like to poke at just a little more um so right now if if i run nimbus what is the best location to get that eth1 data is that am i using a private or i'm sorry a data provider or or are you suggesting well i'll let you answer the question uh no so for now use uh gef or maybe uh there are uh so i've been looking into maybe optimized uh clients that have less states because uh running f on uh if one might take 300 gigabytes

which is a bit of a problem for resource restricted devices so their research into having a better way to monitor the f1 contract and otherwise i think the never mind team has only takes 70 gigabytes [Music] to to have the full f1 chain as well and obviously in a crutch you can always use infra or alchemy and there's actually a full list at ethereumnodes.com and for ever anyone who listens i i do encourage running a full eth1 client that is best practice but i'm also about

doing what works for you and so it's good to hear that these data providers at ethereumnotes.com are also supported by nimbus because i feel like that should not be a barrier that prevents anyone from staking uh if if you can run a guest or if i'm sorry if you can run a full boat you can't you should but if you can't there are ethereumnodes.com that offer a bunch of endpoints so well there should be a little bit of disclaimer here that we didn't have the time to explore every possible atrium one provider out there we've verified that the most popular ones such

as infuria and i believe alchemy was also mentioned by mommy work we encourage people to try other providers for example on the test nets and they can report on their findings perhaps some issues obviously we are commuted committed to support all of these providers in the future but just our testing hasn't been zero enough yeah sure and i my assumption was that they all provided the same type of data but you're right it is it is best to practice caution and even when we when i encourage when we encourage people to um

to use nimbus for staking you should run it on testnet first and make sure that you're comfortable and confident that it works the way you expect it to before you deposit and try to run it on mainnet because the last thing you want is that that stress of not being able to validate when you thought you'd be able to so thanks again one one last thing is i i i think it's important to also note that it's not only for resource restricted devices right nimbus works well on normal devices and on a multi-core machine you can basically you can pin nimbus to a single core and have run gaf grafana and all the other stuff on the rest of the cores without affecting numbers so it really

encourage you to try it out on on all sorts of machines not just uh resource restricted devices sure yeah i think and i i i did focus on those resource restricted devices because i know that there is a large portion of the community that wants limited resource devices so thank you for pointing out my my blind side of this um it was it was great talking to you guys i learned so much i'm i'm looking forward to uh creating a state of the state today where i encourage people to check out nimbus and if you are a viewer i hope you will help us with um with sharing the link to the nimbus getbook um

and thanks again everyone for your time thank you for having us thank you bye bye