NimbusAvadoSpaces

    2:19PM Nov 6, 2023

    Speakers:

    Kaushal

    Bernd

    Keywords:

    client

    staking

    validator

    nimbus

    run

    device

    stefan

    blockchain

    network

    home

    people

    node

    consensus

    execution

    libraries

    easy

    solutions

    create

    numbers

    process

    Hello. Hey, this is Kaushal here. Have you

    Ms. punnets. From from Avado

    Yes indeed. Sponsored cover you, welcome.

    Thank you. Thank you doing fine.

    Excellent. Yeah, not too bad at all. And I can see we've got burned as well so, but I've sent you the speaker invite hopefully you should be able to access that soon

    Fantastic. Thank you for making time sponsored and burnt. I think. As with all spaces so far, I know that it takes a few minutes for people to roll in. So we can we can we can wait for a few more minutes and let the music run in the background for a few more minutes.

    Okay, sounds fine.

    Turns out, I can't quite get the music to start again. That's alright. But I'm just checking that you're able to speak and you've got access.

    Yes. Can you hear me? I mean,

    yes, we can hear you. All right. Thank you.

    Great.

    Excellent. Thanks. What timezone? Are you in abundance? Pollock? Just start a curiosity.

    We're yes, we're in the Central European Time. So and Bernd as well,

    I guess. Yes, I'm in Switzerland. So it's noon, right here.

    antastic. It's always a bit tricky to find the right the perfect time for for the spaces session. Someone's someone's gotta pick the short straw, I guess. But this is exciting to have both of you on, on the node ops with Nimbus, you know, for November. So maybe we can make a quick start. And I'm sure there are a lot of people wanting to join, and will join soon. So let's, let's make a quick start, I think maybe just by way of introduction, my name is Kaushal. I look after all the ecosystem development activities at Nimbus. And I've been with numbers for a few years now. And, of course, English has come a long way in this in this timeframe over the last few years to be one of the more compelling and production ready consensus clients. Also working on an execution client. And we will get to talk a lot more about this. But maybe we can start with your introduction, Bert and then we can go responded.

    Yes, happy to. So my name is bound. I'm in the blockchain space since 2015. I joined the Ethereum foundation because I live in Zook and they, they were founded in Zook. So I was able to just walk over and participate a bit. So then I had other projects. And in 2018, Stefan and I created avato. And later on, we'll explain what avato is now, over and over to split.

    Yes, I've been in the Etherium space or in the blockchains. In general since 2015. I started, when actually, when Aetherium launched their main net, I was a, I was starting my first contract developments. Again, so to get the current with the swarm city project back in those days, and it also led us to believe that that there was a need for Yeah, for these notes that people could read at home, the how to run all kinds of stuff, not related to things that run on the blockchain that's next to the blockchain. So back in those days, it was more like indexing data and so forth. And that slowly evolved into so that turns into advanced first, we provided nodes for people to run blockchain infrastructure at home. And then we're staking came along, this sort of pivoted more with a focus towards staking itself. But maybe there's already too much as an introduction for myself. So I'm doing more of the technical stuff, at Avada. So the maintenance and also development of of new packages. That's why I'm also very excited to to announce support for the Nimbus client. That's

    fantastic. I think both of you have a rich, rich set of experience, very closely working with the Etherion protocol and network and the ecosystem. I think it's gonna be a fantastic discussion today. So can't really wait to get into it, actually. In terms of how we want to use the time, we have roughly about 5045 50 minutes. And of course, I've got some questions for both of you, and Pandem and sponsored, I'm sure you've got questions, too. And I'm sure that people listening in also have some questions. So I think why don't we spend some time just going through some of the questions we have, because I think the history of Eduardo and Bavaro brings is quite interesting. And especially now with the Nimbus client on it, I think it opens up a whole lot of opportunities. So quite curious to talk about those. And maybe we can leave some time at the very end, you know, when others want to chime in and ask questions. Also important that I don't forget to mention that there is a giveaway of two avato devices. And I think Ben will talk a lot more about as we as we conclude this session. So yeah, hang tight, and I think let's enjoy this discussion. benify May, very curious about the history of avato. I think you've touched upon it briefly. But how did avato happen? And you know, what's, what's the journey been like, with Eduardo so far?

    Yes, thank you for that. And also, thank you for mentioning the the giveaway, because I think if people understand what avato is, they will be happily participating. So in 2018, as Stefan already mentioned, we were at many conferences, and we were sort of also developing stuff ourselves. And we saw that running a client is necessary to develop things on a blockchain, but actually running the client is a lot of work and maintenance, and so on. So we came up with the idea to really support developers by making it much more easy to run a node itself. And this was actually a project we helped to, to create was called Depth nodes. And we I was in Switzerland, creating the Association for them. And every time we presented the solution, because that node is a software solution. We had a computer there. And I remember at the deaf Developer Conference of Ethereum, and in 2019, in Prague, we we presented the solution and everybody took up this computer and said, Can I buy this? Can I buy this computer? We said Yeah, well, you can download the software. And so we everybody was still asking, Can I buy this computer with the software, so split and I, we sort of took this on our shoulders to create a mini PC, like a hardware that had the software involved. And then we we found some elements of the software that we wanted to change and we spun off from from that note and created our own solution with a software that was even more focused towards non technical people. So we are hiding all the blockchain stuff sort of under the hood and try to make it as easy as possible for anyone to to connect with the blockchain and over time, so in 2021, when staking came along, we focused on staking so But what I've added us actually is, so I said, it's a mini computer. And you can participate in staking crypto on several blockchains. And it really makes it easy. So you connect the box to your home network to your router. And it does all the technical stuff for you. So it's as simple as using your smartphone, you don't need any coding or technical knowledge. Just connect the device to your internet and plug it in to electricity. And then the integrated App Store similar to an app store on your phone shows you the solutions to clients, we offer an hour, it also shows you the newest client. So you can use Avada to join and contribute to various blockchain networks. And it's like a personal assistant who does all the hard work for you. So if you want to earn by staking eath, it just makes it really easy to choose your execution client. And now you can choose numbers as your consensus client, and all this with just a few clicks. And we take you through the state process, how to generate the keys, how to deposit your eath, and so on. So Apollo is your ticket to join the exciting world of staking without the need to be a tech guru. That's in short, but what about us?

    That's, that's fantastic. I think. It's, and like I mentioned I've been with him for so number of years now. And in the very early days of Nimbus, I think a constant feedback we would get from people wanting to stake and run a node, or validator is like the complexity. And even today, I would say it's solved. It's a solved problem. But I think we've come a long way, in terms of making it simple enough. And I think avato and app node have clearly contributed to solving that problem in a in a large way, you know, so well done, I think, to the team for pulling this off, and to make it really easy and lower the barriers, right for people to come in and join the network.

    Absolutely. So maybe I can ask a question to you. So we have several consensus clients, we have taiko and prison. So what what makes Nimbus send special in regards to the other clients that we have? Sure.

    That's a great question. So my mama Max talked with just a bit of a history for numbers, right? Because I think that's, that's helpful in case. So Nimbus is in some ways a bit of a late entrant in the network as a as an option for consensus client. But having said that, I think the way Nimbus is designed and developed is quite different to the other clients. For one Nimbus was developed on the NEM language. And when we developed Nimbus on the name, language, name language is not obviously as popular as the others. But what that also meant is that, you know, the team had to actually didn't have access to a whole lot of libraries, which you would otherwise find in other languages. And so Nimbus is written, the Nimbus team have built some of the core libraries themselves. And because we build these libraries ourselves, from a performance point of view, they don't carry any extra baggage. The libraries are designed specifically for very acutely for this purpose, right. And they've been written custom for this purpose of running a validator as effectively as possible. And so we don't carry a lot of the extra baggage that comes with libraries when you use generic libraries. The other aspect is from a security and privacy point of view. Because these libraries have been developed bottom up, we've been very mindful of these factors from day one, right. And so a lot of the Nimbus development has really focused on how can we make the client as lightweight as possible, but as as highly performant as possible, with the lowest resource consumption. And I think, back in the early days of this is going back like 2018, early 2019, when the client was still being conceptualised, I think there was this aspiration that people will absolutely be able to run many, many validators from home devices, right. Of course, now, the eath price is significantly much, much more and therefore quite a bit of a barrier to you know, run a full validator, but I think we are seeing a lot of liquid staking protocols emerge which are trying to lower that barrier and solve that problem. The problem Nimbus now solves is that there are multiple benefits of running Nimbus. So first of all, it was it started with the idea of creating the simplest and the lightest client. And with simplicity, what I mean by that is if we currently you know, use any other client that sends a slide, you now have to set up an execution client, then India consensus slide is beacon node validator client separately, you know, there are multiple components to manage basically that talk to each other. The way Nimbus started its designed was to make sure that no, we could simplify the entire consensus slide as much as possible for the staker at home. And what that meant is the beacon node and the validator client was bundled into one and simplified. So with one simple setup, you can set up your beacon node and the validator client is done. So that was the goal going in. Over the over the time, there have been requests to pull out the validator client and offer that as a separate component for other operators who want to have the flexibility of mixing and matching different mica nodes in different validator lines. Nimbus has done that last year. And now that is also an option available. But for solo stickers, a large proportion of solo stickers running, you know, Nimbus, whether it's in rocket poll, we have a big community there. Now also in STATA Labs, which is great to see that these these people generally enjoy the fact that there is simplicity in the client, the final aspect of running Nimbus. And why it's quite interesting is that from a performance point of view and resource consumption point of view, it is one of the lightest clients in the market. And in terms of the options available, and, you know, by a factor of a third of you know, what some of the other clients might, might end up consuming. On a day to day basis in the regular kind of kind of validating business as usual, it doesn't really make a difference. But when the network is under stress, like we saw, a couple of months ago it was and when the network is under stress, when the client actually requires to consume a lot of bandwidth through lots of protocols sipping. That that's when I think it needs a lot of processing power. That's where being low footprint, low resources, client actually becomes really helpful. Why because that means that whatever device you're running this on, whether that's at home, you know, staking device, or an enterprise grade server, running many valid many, many validators, the validators are unlikely to run out of resources, run out of bandwidth run out of, you know, compute power, basically. So these are some of the reasons like it's a bit of an insurance policy by running Nimbus, that when the network is under stress, you know, the validator will continue and not be affected because of the higher resource requirements of the network at that time. Finally, I think numerous is a minority client. Right. And being a minority client, I think people running, especially people running, staking from home and running validator at home. I think it's important really to understand the the the effect that correlate correlation penalties can have, right. And I don't think these are these are very well understood, but the fact that if there is a bug with a client, and if there are sort of penalties applied, slashing event occurs and a penalty is applied. And it turns out to be correlated penalty. In which case, you know, everyone running a majority client gets penalised. stakers, running a majority client can actually end up losing all of their state, right. And I think Nick's off from it. staker recently did a poll. And it was surprising that, you know, not a lot of people in the community actually got that right. Which was, to a degree a bit boring. But it's a good reminder that as much as this is about getting sort of good balance of representation of each client in the network, in every individual running a dog from home, must do their own due diligence or homework, right. In terms of thinking about what happens, should there ever be a correlated penalty, or a slashing event like that? So yeah, these are some of the reasons I think I'd say you're running them. This is quite interesting at this point in time.

    Great, but it also answers a lot of questions of why home note or home stakers should run numbers and not as you said, Not majority clients that everybody runs. So that's, that creates just a bigger risk of you if you run these. So that's that's really,

    really good. Yeah, thanks. Shutting up.

    Yeah, maybe. Maybe Stefan can can also add. Yeah, why were we added? That's right. Besides forsaken?

    Yeah, I think a lot of the reasons I've already been mentioned, I think we also want to have disclaimed diversity on our platform. So we, I think the first client that we implemented was the prison clients back then it was in data the other by a big buy big little majority clients, then we had to take when we also like stimulated people to like to move over, or at least, to make the switch to t equal so that there was like a healthy balance in our community as well. And that's like adding members is the next step in that in that process. So we always try to make it easy for people to make their own choices. So we will usually create these, these YouTube videos, these tutorial videos on how to set up your available for example, with prison or take or with Nimbus. And so that makes it easy for people that want to switch. So all the parameters, so if you're already running a certain execution client, for example, you can still change your configuration. So that different beacon chain, or different validating clients, so we just tried to facilitate that. So I think that's in that regards, a lot of our goals are, are the same. So we want to, first of all, make it decentralised so that a lot of people can run it at home. So people that otherwise wouldn't have the technical knowledge to do so. And then when they take the step, to run it at home, that they still have the choice with glein to run, I think also in our community, people also tends to stimulate people to have that client diversity. And to say like, if they're running prison, is there some some issues with it? So why don't you try, and other clients like Diego, are liking us right now. So I think it's also a little self regulating, or at least self educating that community. So that's a very nice side effect to see as well.

    That's that's quite fantastic. Actually. Curious if I could if I could ask one more question, Stefan on that, in terms of the community, we know, I mean, prism was one of the earliest clients, and there's a huge sort of following of prism and people using prism. And I mean, people have also done a fantastic job right. Of, of keeping keeping up the sort of client experience and in some ways for for, for individuals, and for also the larger operators. But curious in terms of your community, Bert and, Stefan, do you feel like people understand and they want to switch between clients? And they do that actively, and Nevado actually facilitate that?

    Yeah, I think yeah, at least we facilitate it. So we, so we come back to your first thing that you said about prism, I think the reason that we added prism in the first as a first client was that it's already came with like a web interface to manage and adds validators and so forth, like the super user friendly. But since then, we've evolved to an own user interface that is unified across all these, all these validator clients. So that means that whether you use prism or take or Nimbus, you can always use the same UI on the Avada. So it just uses like an API, that's the oldest Klein implement. So that makes it very easy. And so the only thing basically, that changes for the front end user, is the law that's displayed on the top when you're running this staking on either your members or your prisoner are taken. So at least we try to facilitate it and make it as easy as possible for people to switch better than if you want to add anything to that.

    No, I think that's the reason people use certain software, or also hardware is the convenience factor it allows, and that's what we try to support in any way is making it easy and convenient for the user as possible. So that you don't have to accommodate with a new user interface. For example, it's like switching from an iPhone to an Android phone. You know, that's, that's terrible. And in some points, both phones are great. But when you switch, you want to have the same sort of user experience. And it's not given. It's tiny things and this one user interface showing to the consumer, no matter what client you run, makes it much more easier to switch. So that's that is our at least our opinion on this. And convenience is always the reason people choose something in the mail in the first place.

    That's yeah, and I mean, having seen the bottle and no, I mean, the convenience factor is definitely there. I think that's like that's like a big attraction of running avato and being able to switch things easily without having to, you know, go through the full setup, and familiarising ourselves with another set of documentation. As client leaves, we spend so much time on documentation Right. So I can imagine people having to switch from one to the other. It's like a nightmare. So I think you guys are doing a fantastic job.

    That is not only that, it's also, for example, the updates. So every time, of course, we have to be realistic. That's like all old pieces of software, that that are needed to run the validation. Certainly now, it's a DVT opinion, all these different liquid staking providers, which of which we also try to support the bigger ones. It's, of course, always a struggle to keep up to date with all the latest developments in the in the latest versions. But that's at least something we also try to take out to the hands of our users. So that's that, that store that that bent already mentioned, it's automatically update. So whenever there's like a new version coming out, so if there's like a new Nimbus version, then we from our stripe will see that and we will create, like an update of the package. There's like any configuration changes, we also implement, like the migration thoughts from, from the older version to the newer version, that's what we tried to do all of that automatically. Then it's pushed to, to our app store. And people can opt in or can opt out of these automatic updates. But there's also usually a big part of like the sort of maintenance of that. So if you look at sort of the DevOps aspect of running a validator yourself, its first guest setting it up and reading all the documentation, but also keeping it up to date. So I think that's also certainly a factor worth mentioning, where we try to increase convenience for the end user.

    That's, that's fantastic. I'm sure. I mean, there's a lot coming down the pipeline, isn't it? Isn't it, Stefan and Ben. So, I mean, this reminds me that there are some really interesting aspects of Nimbus that we are working on right now. Like, I think we don't want to I don't mean to create more work for you, in terms of, you know, more capabilities, more releases to plan and integrate back into back into avadh, of course. But there are some really interesting aspects of the Nimbus CLI, which might be worth looking into. And maybe generally useful for people listening in as well, if they're planning to run a client. So just if I could mention a couple of them, right, like I mentioned that they are already working on an execution client. And one of the intentions is, of course, to make the whole process really simple between setting up the execution client and the consensus client. And below, make it as simple as possible, just as we did with the beaker validator client, I think that's the intention to get to that point. We're working through the performance optimization of that so that we can get the same level of performance of similar level of performance from the execution client, as we would from the consensus layer, and noting that, of course, execution plan requires a far more, you know, far greater resource footprint, particularly the memory space. So there's some work going on to optimise for that. But the there are a couple of new features in the consensus client, which might be useful and interesting, right. So the numbers were validated client now has the capability to talk to not just one beacon node, but multiple beacon nodes. And in addition to that, the Nimbus consensus slide has the capability talk to not one execution layer client, but to execution experts. And so this is starting to offer an open up a set of you know, opportunities, like particularly when there are stages where you need to upgrade the Okay, I think a lot of this detail would be hidden away, abstract away for users of the avato. You know, package. So all of this happens sort of behind the scenes in a way. But there are some of these new interesting features that are coming up right? In the database consensus slide. So if there is an upgrade, or one of the execution layer clients can use the other one as a fallback. So there are some interesting things coming through. Also curious, Stefan burn it you know, what, what's coming in the pipeline, like what's going to be new at avato Very soon.

    Let me just maybe comment on what you just said for these difference that you can point to like different execution clients for example, with opens possibility there is it's usually people who want to start staking they need to wait for the total execution claim to be synced which can be sometimes a lengthy process. And there it might be interesting to just point to an existing than more centralised of course already think Execution note somewhere and then when your own noticing that that it just takes over from there, so that might be an interesting use of that feature that you just threw that in for the? Yeah, I was just gonna say that. Maybe they didn't you can take Yeah. So

    I was just gonna say that that's very true. I think, you know, people have to wait such a long time. And I mean, that's one of the sort of, you know, from a user experience point of view or needling factor, right. So, clearly an opportunity to potentially address that sort of user experience, right, when they're setting it up for the first time. You can speed the whole process up using some of these features.

    You want to take sick as Christian? Yes,

    absolutely. So I mean, what we always look for is to give more to to our existing communities. So we want to improve your your earnings in many ways. So and DVT. And liquid staking is definitely, these are solutions that are up and coming and they haven't already baked, but we believe this will be even bigger. So there's many things that will come in the near future on a model that combined DVT and liquid staking. So So you have to watch out in this space, especially for lotto, and we're in Istanbul next week, or this week, actually at the sticker awards on Friday and Saturday. So reach out to us talk to us. And we have we will definitely have great topics to talk about in the near future. I cannot go into detail yet. But we were looking for investments and investors. So if there's anyone that wants to talk about more in more detail about that topic, again, we're really integrating DVT and liquids taking on a level that has not been there before. Yes, and I see some some hands rising. Should we take some some questions already? Or? Or talk about the giveaway? Yeah, I

    think I think let's talk about the giveaway because I'm sure a lot of listeners are quite eager to hear about that. So why don't quite a current take us away, man.

    Yes, great. So we we want to together with news, we will give away to devices that are really to get started in staking in home staking to be precise. And we want to really make people switch from a centralised exchange from from an exchange like Coinbase or binance or wherever they are staking with to make the step into solo staking home staking and as you as you know, we have several solutions on our platform already that doesn't require 32 eath. But you can start with a lower amount. But definitely you can also stake 33 on our platform really go solo and with Nemesis is really really easy now and and exactly those are the reasons that already have been mentioned is why we give away the i Five model because it's it's a model that is perfectly suited for staking and we'll run numbers perfectly on it, it's it has a high five CPU is two terabyte of storage and 32 gigabyte of RAM, which is enough to synchronise the chain, run the chain and validate your stake. So these will be given away to people that are willing to take the steps to from a decentralised exchange to staking on avato. And we want to monitor or show this process to maybe guide other people to that it's really easy to stake from home because of these clients because of DVT because of solutions like avato. And yeah, hopefully have a like a lighthouse model. You could be the lighthouse model for others to take a step to have you want this device and we monitor or communicate about your process from switching from an centralised exchange to running your own nodes on the bottom. So that's that's sort of the process. And the the way we want to do this is we have like two weeks timeframe from today on. And we want you to explain what is the benefit for you to make the switch? Why would you rather stake on an on your own node than on a centralised exchange even though you did it before but you can also explain why you did it and what you hope to accomplish by by running it on the bottom. So just tweet about it. Tweet with a bottle and numbers tagged and really say what what yeah, what motivates you Have to stake first of all stake at home that later on, and why you made the step to come to a decentralised exchange first, but now I willing to take this new step. So we will take the winners of this, we'll just whoever the conference is this best motivates us most to will get the price is not it's not about getting likes or anything. It's just simply telling us from your heart, why you want to do this. And we'll give away two devices. And then again, we will closely monitor the process and communicate about it to make sure that other people understand that it's really an easy process to do and that more people hopefully follow your your lead at the end.

    That's That's great. Indeed. I mean, that's an exciting two weeks. And I'm sure we will post a tweet outlining the entire process. Subsequently, after the spacer session. So I'm sure there are a few people listening in from US data labs community, a few people I can recognise or rakibul community. And, of course, a few people, I think, who we know have been running numbers. So that's that's quite an interesting mix. And I think, as you said, if we can motivate and encourage more people to pull the data out of centralised exchanges and and run that from their own home. And if this giveaway or this little incentive can can help move the needle that direction. I think that's that's a fantastic thing to do. So quite excited about about this. Yeah, I think two weeks from now tagged Nimbus, and Eduardo will handles. And, you know, tell us why why you think you want to stick from home? And, and, yeah, and we will pick a winner in about two weeks time. So there are two instruments being given give be given away. So exciting times, indeed. Great. I think we're doing well for time event. So one of the questions I had if you can move back to questions that I'm sure a lot of people have requested an opportunity, so we'll go to them next. But one, one question I have is like, what can we really do to you know, like from a Nevado point of view? You know, how do we decentralise the network even further? Right? Because I mean, Nimbus and avato. I think we've seen operating in the space, we've seen that there is a tendency for the larger operators to accumulate and, you know, become much, much larger operators and sort of concentrate the number of validators. How do we encourage more people simply simply stating through centralised exchanges, or even through other protocols, you know, to kind of, you know, take the initiative and, and know, run that run the node from their own home and decentralised network.

    Yeah, so I mentioned this before, it's mainly its convenience. So we have to create solutions that are so convenient that you don't need a centralised entity to take your hand and guide you through this. This is mainly what what happens if you use a centralised exchange or a centralised, even staking service that takes you through the process and takes away the load of the technical part. The Yeah, knowing the technology and so on. If if you compared to web two, the Internet was also decentralised at one point. And but the convenience made people go to centralised solutions. So at the end, Facebook is the most convenient way or Twitter is the most convenient way to communicate with people. It's much much you need much more tech knowledge and knowledge of the underlying protocol to if you use blockchain or web three technology and this is what needs to change. So this is why we try to do this with avato You still need to buy the hardware but this is like your router that you buy. To access the internet you have to it's like the same comparison. You buy this device and this gives you access to the to the to the blockchain and this is what it's all about. It's the blockchain needs a blockchain needs to be decentralised otherwise, all the the attributes we put into it will not work. We will always be at the realm of someone else to dictate what we can do or what we cannot do if we can access our funds or not. So you should if you want to use this technology you want to use cryptocurrency. You should also take the step and really make it decentralised. And this is sometimes scary in the beginning, because it's so different to what to applications or solutions. But the better we build the systems, and a lot of is really trying to make it as easy as possible, the better we do this, the more people will make this change. And this, this really allows you to be in control of your own wealth of your own assets. And at the end, staking can be an income for you. If you stake especially now with probably the upcoming bull run with a tweet that we all look for. If you stake 30 to eat or even less, this, the rewards from this can be an income for you. So you can really live from this without touching the underlying asset itself. So you can just skim off the the actual rewards that you receive without touching your your base asset that you that you sort of staked and this is really, really interesting. It really allows you to be independent. And so decentralisation is the only way to make this to create this independence. And if we don't decentralise or keep decentralising the systems if they get more and more centralised, then again, we're we're being dictated what we can do by third parties. And this is exactly what the blockchain actually wants to solve. If I

    can, if I can just add to that. So I think a very interesting narrative, also, probably, that we will hear throughout the next, like there's a whole bull run that we that we're all expecting, indeed, is probably that, that DVD so now we can also splits the sector who generates also who is actually providing the capital and wants to do the staking, up to until now also had to run the nodes to to actually do that. And now with that technology, you can sort of split those roles. So you can just assign the shares to a node operator, that just runs a share of a of a validator without the need necessarily to invest himself so they can just do the duty. So I think there's two things that that need to be that you need to overcome as a solo stakers. First, you need to have the right incentive thing, so looking at the rewards, but you also need the capital to start staking. And so the the my opinion, sort of like breaks those, those two things apart into the two different roles. And I think that is super exciting, because at least from the point of avato, it makes it even easier for people to enter into staking because the only thing you need is basically the device itself. And then there are some some key shares and get allocated to you that that should be enough to already start earning with your device. So again, that's like a new evolution where I think that's the boundary threshold is lowered to participate in that. So those are very exciting things for us.

    Quite quite exciting. I think. What What about those accomplishment? I think going back to summarising the point around convenience, you might think that's such an important word, like, take the box out of thing, you know, connected to the internet. And you're off to the races, right, because the rest of the configuration process isn't quite technical. It's it's really simple. And I think I think that in itself is a game changer. I'm hoping that as people hear this and explore more of our dough that people get excited about participating in the giveaway as well. A bit of a challenge for each individual right to to see how they can contribute to the network. So quite excited about that. And the few people have requested an opportunity to speak. I think I'm going to unmute some of the participants and see if they have a question for us. We will start with with St. Maxwell. There you go.

    Okay, I have enabled a few people to fellow speakers. Please go ahead.

    What's up everyone? What's up? Yeah, so yeah. I wanted to know, how have you been?

    Sorry, we might have just lost you there.

    Yeah, don't mind me. I wanted to know, the challenges that we face in this market. And how we've been building I've been over called overcoming them.

    Alright, Michael, can you please go again? And can you please run through your question again? Please Marvel? Yes.

    Sorry. Hello, can you hear me?

    Yes, we can. Okay, thank

    you very much for bringing me up to speak. So I just like to ask what I'm actually inspired the creation of your project? Is that a particular problem you're planning on solving? To inspire the creation of new approaches?

    Right, is Is that a question? Is that a question to borrow or two numbers?

    So, yeah, the numbers on I don't

    know. Okay. So Steven, if you want to go first?

    Yeah, so I think in the introduction, I already mentioned that. So we were we were running the swarm CD Project, we were in looking for a solution, which wasn't there at the time, for people to run computations of chain like indexing data, and so forth. Back in those days, like the old theorem, ecosystem was very small and nascent. And that sort of inspired us to restart experimenting with the idea of providing hardware and enabling people to run notes at home. While we will take care of the software, so that it will be that people there only contribution would be to run the device, and then be able to earn something for the service that they provide to the network. So that's where it's all started. And then like, after some years, it pivoted to to staking. So that's where we are coming from.

    Thanks to fun. Then, Michael, I see you got your hand up. Do you want to go next place? Yeah, yeah, bro.

    So I think I'm a coin. Okay. Anyways, I wanted to know,

    how serious the security you take your security is? And how do you try and make the yield on these various channels like legal, state and arrest very profitable.

    So first, maybe on the question of security, so the way that that you set up this device is that you instal it behind your router. So that means when you run it on your home network, it's already behind a firewall, which is, which is your router. And by default, all the ports towards the divisor close. So the only ports that the device opens are those peer to peer ports, which are necessary to synchronise the blockchain and to communicate with a peer to peer networks. So that's how that part is shielded off. If you want to dial into the box remotely, we also support that to a package we call remote connect. And that provides a fully encrypted tunnel from your device that you that you use to access the advanced it could be your phone or your laptop, towards the device itself. So that's, that's part is completely encrypted as well, on the site of the staking so the only thing that you need for staking on Aetherium is your your delegate your validator key. And the validator key is only used to like to sign at the stations and to sign blog posts and so forth. But one noteworthy thing is that the the withdrawal address, so if you stake 32 Each, if you would unstained, that the address where that's those phones are sent back to is already determined beforehand. So there's no way that somebody can sort of break into your device, steal your validation key, and then run off with your 30 IDs. So the only thing that could happen is that they use your your validated key to do falls at the station and so far, but I think that is already a very, that would be a very advanced hack on your device itself and might even require physical access to it. So I don't know if that's release any of your concerns with regards to security.

    Thanks, Tom. That was quite a comprehensive response, which is just great to hear. And yeah, I mean, it's interesting this has come up in the discussion. This led but of course, quite a quite an important important topic to cover. I think we have time for perhaps one more question. Oscar, I see you requested to speak. You may want to raise your question.

    Hello, can you hear me?

    Yes, we can.

    All right. My question is actually to member. So I just want to know, what are the what are some of the specific techniques that Nimbus uses to achieve its light weakness?

    Okay, happy happy to take that. This is a great question. I think in terms of the the engineering of the client itself, like I said, we have been very, you know, pretty selective in terms of how we've engineered the client, and I think, touched upon this earlier, maybe if you weren't here earlier, but I think one of the main points to make here is our choice of using the new language for numbers. And the fact that because we've used the blank, which, which isn't extremely popular in the community, but I think it now has a very growing and exciting community building around name language. As we started to build on it, some of the libraries, you know, which we take for granted in other languages, named did not have those libraries. And so we had to custom design and write these libraries from scratch. And when we wrote them from scratch, we designed and wrote exactly just just exactly what we needed to write, right? For the client. So these libraries are very tailored, they don't carry any extra, you know, fluff extra baggage. In terms of, you know, the libraries itself. And because we use these tailored libraries, specifically written for the name in the slide, they are very, very lightweight and very efficient in how we use grunt, run the code, basically. So I think at a high level, I think that'll suffice to say, the way it's engineered, and choice of a language has an important part to play in it being very resource efficient. And I think there are a lot of design trade offs. Like, it's not just about the language, like, there's also the design trade offs of what we choose to do and how we choose to do things. So I think the lightweight or making sure that we consume the least amount of resources, something that's baked into every engineering design decision right along the way. So I think this is a, this is a result of a cumulative effort. And also, you know, sort of the design decisions that have been made along the way. So hope that answers your question Oscar, but it's a combination of the choice of the language, the the having to do very bespoke and tailored set of libraries, which don't carry extra baggage and therefore are very highly performant. And then the sort of trade off decisions that have been made along the way in the design of the consensus slide.

    All right. All right. Let's get to the answer you gave. Okay. I just want to know, like I, I have another question, which is how fast can we synchronise with the general blockchain?

    Okay, very quickly, I think Ben and Stefan also touched upon this, like the consensus client can use snap sync, you know, in terms of syncing, it's really the execution client, you know, that takes time to sync, right. So that's where that's where the sort of bottleneck is, and depends on which execution slide we use and how and whether you do steps in or not. So I think there are those sorts of factors to consider in terms of how fast it can sink. It's less about speed. It's really about how much time it takes to sync in terms of the node itself, with the network. So I think that's probably where I'll pause. Noting that, you know, it's not specifically about a client in terms of speed, I think every execution client goes through the same sort of thinking, you know, of course, there have been studies done by mega Labs, which is part of the Barcelona supercomputing centre, and they have compared the sort of time and speed and resource requirements of all of the different clients. So if anyone's interested, you know, you can please feel free to look it up in terms of the different comparisons of the different consensus plan. it across all of the parameters of resource consumption. So bandwidth consumption, memory, CPU, speed and time to seeing things like that. Stefan, I see you got you. You raise your hand. So there you go. Yep.

    Thinks if I got kicked out?

    Fair enough, I must have no problem. I'm gonna press the wrong button somewhere along the way. Look, it's been exciting. I think we're almost out of time. So first of all, note ops with Nimbus back in November hasn't been a great, great experience to having discussing both with, with you, Ben and Stefan about all things evolve. And how hard was trying to make a difference? Do you want to very quickly again, for those who have just joined us recently, you want to just very quickly summarise in conclusion about the giveaway and what next steps will be?

    Absolutely. So Avada is a mini PC to stake. We make it really easy to stake and we and nibbles together give away two devices. It's an i Five device. Perfect for staking and running numbers. All you need to do is explain to us why would you change from an centralised exchange, to staking at home, do this in a tweet, tag numbers and a battle. And you have two weeks time to do this. And once we draw the winners, the winners will be monitored or supported by us. And we will communicate about the process of them switching from the from the exchange two avato and how they experienced this and what the benefits are, or also the downsides to be transparent to other users. And by doing this, we hope that more people follow your lead and also change from from an exchange from a centralised exchange to staking themselves at home. So this is really something where you can support the whole network, the whole ecosystem, the whole community, and lead the way and show them how this works. So again, about our numbers are supporting this with each giving out one device. And all you need to do is explain to us why why do you want to change from an exchange to home staking? If you're interested in avato, just go to java.do. And check out our websites. You see us in the conversation now leading up to the to the Twitter spaces. So you have our Twitter handle. Communicate with us ask us anything, even after this Twitter spaces on on Twitter on x. I don't know how to call it today. So just just keep communicating with us. We're happy to hear from you. And again participate in the giveaway. All you need to do is really come from an exchange and steak steak at home.

    antastic thank you again, Ben and Stefan for your time. And thank you to all of everyone who's joined us today. It's been fantastic. Not opposite Nimbus is back getting and we'll we'll be back in December hopefully after def Connect. But yes, the Nimbus team will also be at Def connect, like Ben mentioned. And yeah, feel free. If you're in Istanbul, within you know this week later this week or next. Please feel free to drop us a note and we'll make time to catch up. Thank you again and have a nice rest of the day everyone.

    Okay, thanks for having us. Bye bye. Bye bye