 Okay, first we'll start off like, what is a node? Well, a node is software that downloads a copy of the blockchain, all the history, all the state, all the accounts, transactions. And it keeps that up to date as blocks and transactions take place. And it also helps others run a node. So when you start up a node, you ask all the others for the history of the blockchain. And this is really important because the foundation of Ethereum is really like a network of decentralized nodes. And without those, you know, why are we here? I guess we could just build a centralized solution and have something quicker and yeah. So we'll go over four of like the main reasons why I tell people like, hey, you should run a node. So again, supporting the network. It's each additional node that joins is additional capacity to the network. It makes the network more robust, more secure. Again, easier for a new node to start up has more nodes to get the history from. Also, it's really important that we have people running nodes that are from different clients, meaning different node teams, different client teams. Right now, it's kind of a big problem. If you've heard of Geth or Go Ethereum, right now about 80% of nodes are Geth. And if there were to be a bug in Geth, that would cause quite a problem for the network. So we'd much like to have users run like Beisu or NetherMind. And yeah, this makes Ethereum much more resistant. And I'm sure it helps the Geth developers sleep at night as well. Okay, another big reason is to avoid lock-in. This has to do with like the problems of kind of the Web 2 that we talk about a lot, centralization. So having a decentralized network of nodes both helps Ethereum from being kind of like locked into maybe a small group of developers or teams. And it also, it enables like additional systems to be built on top of Ethereum and have these properties. So if you can build a system on top of Ethereum and if designed in the right way, a property can only really be changed if all the users and participants want that property to be changed. When we talk about forkability, this is what we mean. One other cool thing is kind of relates to the last slide is you get to vote on changes to Ethereum if you run a node. So let's say Vitalik and some of his friends create an update to Geth and say, we want one ETH every block and we're gonna send it to devs.eth and they all update their nodes. You can choose to support them by taking that update, essentially voting with their change or you can decide not to. And you can not take that update and just run the current version that you're running. So if a lot of users don't update their nodes, if the centralized exchanges and your wallet providers, like they don't update their nodes, then this update doesn't take place. But let's say like all of those actors do update, then it's most likely that this update goes through and if you don't have a node, then you don't really have a choice. You don't have a vote. You don't have a voice. Okay, and this is a picture from one of Vitalik's blogs. Again, talking about, yeah, so if there were to be some sort of attack on the Ethereum through this, like a new update comes in and it does something bad, it takes funds that would be considered like the attack we're talking about here. And all the users, all the node operators that decide to take that contentious update, they may end up on one fork and all the other users and node operators might end up on another fork. And he talks about, these are kind of like the three scenarios that would happen in this case. And so we prefer the options like toward the left. So we would want something like this to fail. Obviously, and however, even if it just ends up in chaos, meaning like maybe half the exchanges show one state of the Ethereum and maybe half the exchanges and wallets show another state of Ethereum, that's still like much better than the attackers becoming victorious. It kind of makes the attack like extremely expensive even if the attack doesn't as in victorious or as it doesn't fail, I should say, it's still extremely costly. And then an important question everyone wants to know is can I run a full node? A lot of people I talk to, they want to run a node but they don't know if they can. So here's some of the requirements. Your computer needs eight to 16 gigabytes of memory, two terabytes of fast SSD storage. This is kind of the biggest problem for people is this fast SSD storage. Even some of like what you might think is like a really fast external storage drive. Like it's super highly rated for like moving videos and in photos. It might not be fast enough for syncing a node. Let's see. Right now only one terabyte is used by nodes to store the state. This is growing about 10 gigabytes per week. Some nodes have options to use less. They're kind of, they're just beyond like the experimental phase. They're solid options but they have their limitations and don't quite maybe meet all of the use cases that people need. And then the CPU is not usually a bottleneck so most laptops that are within like five years old should do fine. Internet can be a little bit of an issue so you need about 10 megabits upload download and it needs to be lower latency connection. The data cap is, it can be a problem in the US. A lot of internet providers have a one terabyte per month cap. I've talked to some people here in South America and they don't seem to have that problem or at least they're not aware of it. And then definitely can't really run it on like a slow cellular or Wi-Fi connection. Okay, I'm gonna quickly talk about like the SSD types. Kind of the number that you wanna know is this like 10K input output operations per second. So yeah, nodes, they are essentially writing like tons of like small files back and forth reading and writing to the SSD. And this is kind of like not really a common rating that SSD companies tell consumers because it's not quite applicable to what most consumers are doing with their SSD. Most consumers are just moving at large video files, storing photos. Okay, internal SSDs, M2 NVMe, that's like very popular now within the like $200 range you can get for this. And then yeah, you probably just wanna stick with that. The other options, if you have them lying around, those might work, that's not gonna work. External SSDs, the reason why I wanna emphasize this is because I think there's a lot of people out there with laptops and don't have like a dedicated desktop or computer just for running a full node. And so I want people to be able to run a full node on their laptop, maybe like while they're not using it or if they have an extra one. So check to see if your laptop has like one of these connections, either Thunderbolt 403 or USB 3.2. Okay, now this is the interesting part because these are some of the upgrades or potential upgrades coming to Ethereum in the near future here. So when you hear pro dang sharding, that's EIP 4488. And actually in the worst case scenario, this would add two and a half gigabytes per year for node operators, which is just not really an option for at home node operators. So in one of Vitalik's write ups, he said that like when like if pro dang sharding goes through like we also need EIP all the fours. And what that does is eliminate historical data requirement from the nodes, which would save like 500 gigabytes and kind of like cut down the requirement on nodes having a store like all of this data. State expiry is one that is contentious again. What it does is essentially eliminates the requirement for nodes to like keep on to store certain transactions. Let's say like before a year or so and unless that state is updated. So I have a feeling this probably won't go through. So don't count on that. Stateless Ethereum is a really cool change. No storage would be required for the node. So it pretty much eliminate that two terabyte SSD requirement. It would still be good for like some nodes, some users to have that history, but it wouldn't be a requirement. So you could run a node and still validate all the blocks and transactions and really participate in all those benefits I mentioned earlier without the storage. But again, this requires like vertical trees and it's a pretty difficult upgrade. So don't quite count on that. Ethereum Portable Network is a really cool, actually like separate network built on top of Ethereum or to the side of Ethereum. It leverages like bit torrent architecture and would kind of enable everyone to run a light node actually like embedded in their wallet. So like most of our wallets right now, they talk to like infura or alchemy to get transactions and send a transaction. This would essentially eliminate that point of centralization and your light node would actually talk to other light nodes which would talk to full nodes whenever you send a transaction. So really promising, but quite a bit of work there. I think they wanna have, just for a time reference, I think they wanna have something out by like the end of next year. The fun part, how to run a node. Okay, could I get a quick hands like if you've heard of DAP node or Ethereum on arm, I guess. Maybe a quarter of the people in here. Okay, so yeah, they're great. The only difficulty with running a node with DAP node is you pretty much need a separate computer. It installs an entire new operating system which also can be a hurdle for people that haven't installed a new operating system on a computer. But they're great, they've been around for a while and I would say like are pretty battle tested. Option two is the command line which is for super technical users technical users who are familiar with the command line and yeah, don't mind monitoring their node from a flurry of like command logs. And then this is actually from ethereum.org's website. And actually Photoshopped nice node here, not Photoshopped, but like edited the HTML. So this was kind of like the vision for nice node was like hey, I think we need a third option. One that is for like the non-technical user. There's tons of people passionate in the ethereum community who wanna run a full node but don't wanna hit the command line, don't wanna buy another computer. Technically it's possible to just download an app on your laptop and run a full node. So why don't we have it? So I'm hoping someday when this gets to a more stable version that they'll include me on ethereum.org but we gotta prove it until then. So I'm gonna talk about a nice node which I am working on and so this is what the current version looks like. This is our alpha release version zero. And you can see this is just like an app running on, I think this is Windows and you've got both your execution consensus clients here. Super simple, stop, start, remove. You can kind of see like what is it doing here at the top? Like, okay, awesome. I know how much storage it's taking up. I can see like what's the latest block it's at. How many peers is my node connected to? And then kind of in line with this idea that like I want everyone to be able to run a node. I also want everyone to be able to like, you know, no matter what language you speak, we'll have a translation for that language. And all of these languages were translated by contributors, just people with a good heart who came out and said, yeah, I'll be glad to translate like whatever we can and into another language. So a nice node essentially sports translations. We just need people who speak all of the other languages to help out. Okay, hopefully this loads. So this is a design for our next version, much like cleaner UI. At first only the Ethereum node will be available, but I'm designing it to be general so that you can run other nodes. I'll talk more on that. So you pick Ethereum node and you pick which client you wanna run. We conveniently show you which clients are minority clients. You can select a few options, select where you wanna store the data at. Again, these are all things you'd have to do from the command line. And then this will actually take the screen. I think I'll show it to you later. And then we have to install some dependencies here and we just hit start and our node is syncing and running and we have this beautiful UI to see our node and everything is great. Okay, so this is kind of a key piece of information for a lot of people is like, can my computer run this node? No, you don't have to go to guides or websites to read through things. It's in the app. The app, yeah, we can see like, hey, is your CPU fast enough? How much memory do you have? Do you have an SSD? Does it have enough space? All that stuff we can do, so we do it for you. And this may differ by client and in the future, this may differ by node type, meaning the hardware requirements may differ. Some nodes may be used smaller on a RAM. Others you might use more storage. So we'll give you that green check mark if you're good to go based on the node type. Okay, a few more screenshots here. Yeah, just wanted to leave these up here so you could see them without the video. This is really important to me, being able to change the settings on your node through the UI. Again, to do this now, you have to go to the docs of the client team, try to find the right flag with the dash, dash, whatever, and hopefully you format it rightly. I don't know if it needs quotes. It doesn't get a comma in between or space. You don't have to do that with nice node. It's here. Okay, nice node is cross-platform, meaning it works with Windows, Mac, Linux. This is a screenshot of Windows. Looks like it's not gonna play. So yeah, again, I designed nice node to be as general as possible, meaning as L2s start to decentralize and provide nodes, maybe sync with sequencers, nice node, there should be very minimal changes to support those new node types. And actually users could open a pull request to nice nodes GitHub, and those new nodes would be in nice node in the next release. So for the technical folks, nice node is sort of a UI wrapper around Docker containers. So any node type that has a Docker image will be really easy to add to nice node. And yeah, eventually we wanna add things like staking as well. So this is a UI screenshot of what it would look like if you were to add validators. And then you can just kind of see like, yeah, Arbitrum does have a node out. I don't know if, I don't know how involved it is in their layer too yet. I think it might kind of just be like a replica node and not quite the same priority as they're kind of like their own. And then the end to beyond here is, okay, if our like web three dreams take off and web three infrastructure is really where we go to and the users control, we control the platform and control the data, then we're gonna want users to run some of these web three infrastructure nodes. So for example, like this video is being live streamed over live peer and they have a network of video transcoders. And then, so they transcode this video and that's any one of us, if you have a graphics card can join that live peer network and we can use our graphics card to transcode that video. So this is just one example of like a web three infrastructure that users can participate in and have more of a say in and it's something that I think we can support. And so we show it here. I think this might be the same video and that looks like the same screenshot. Maybe I hit it back last time. Okay, a little bit for our roadmap. So we're really close to releasing the redesigned UI UX and the super simple onboarding walking you through like the hardware requirements, other things like that. I wanna get more translations. We're gonna work on that hard, push on that hard, hopefully by the end of October here. After that, there's some internal changes that we need to make to support more node types for the future. For the technical folks, that's Docker compose. That means kind of like there are nodes that have contained multiple services. And so that will help those node types. And then additional features. I think I can show you these after. So yeah, node notifications. If your node has an error log, like we'll show you a notification that error log won't get like lost in your terminal and you'll never know about it. And then you can like search logs. Maybe if your internet goes down, we'll notify you that your internet was down for a brief time. And then after that, yeah, by February of next year, we'd like to add Layer 2 nodes and more Web 3 infrastructure nodes. So it is critical to Ethereum's mission of decentralization, censorship resistance, and resiliency for users to be able to run nodes. And this is extremely important to me because all of the other good things we talk about here will only last, will only exist, will only really be possible if we have a truly user-led culture of running nodes. And if the core devs continue to make it possible for users to run nodes. So yeah, if we want this dream of open global infrastructure, super low transaction fees for the world, open financial system, Ethereum for everyone, we need users to continue to run nodes. And nice note of the mission is to simplify node running. And thank you, gracias a todos. So yeah, I wanna open it for questions and let's see, I just wanna move it to this slide. So yeah, real quick, if you wanna help, we need everybody join our Discord, reach out on Twitter. There's a website here you can translate on which I'll get notified as soon as someone translates. So that's cool too. And yeah, question time. Thank you for your time, first of all. I've got this core philosophical question that I've had for a long time, which is I feel, and maybe this is a lack of understanding that full non-validating nodes are overvalued because in the end the state is only managed by full validating nodes. So why does it really matter that they're more and more non-validating nodes than the network? What does it matter so much? And isn't it easy for something in here to just deploy thousands of full non-validating nodes which don't need the stake key to overpower to have a cycle attack to be a non-validating network? Okay, so tell me if I understood your question right. So your question is what's the importance of non-validating, non-validating nodes like without ETH, what's their importance? Yeah, so it's a great question. And what it does is the non-ETH, non-staking nodes actually keep the validators. It keeps the ETH stake nodes honest. So yeah, if let's say some centralized staking service gets 75% of the validators and they want to push through a block that sends all the ETH to them, the non-ETH nodes will say, hey, that's a funky block that doesn't follow the rules of Ethereum, that's you're trying to steal someone's money, reject that block. I'm not gonna take that transaction and share it with anyone else. I'm gonna drop it and say that's invalid. So it essentially keeps them honest. That makes a lot of sense. But the monetary premium on cycle attacking where it's really low, like if right now you have 10,000 non-validator nodes, to push another 10,000 into the network is very easy if you know. So how strong really is the defense mechanism? Yeah, that's a good question. So like if someone were to on some cloud service just spin up like a ton of non-ETH nodes, I think it would probably be more costly than it would be, I think it still would be pretty costly. And I think even if let's say they have triple quadruple, the number of like honest, nice nodes, then I think the attack would still fail or it may in this case default to chaos. So I think I'm probably not the best person to speak on terms of like, hey, we need X number of honest nodes. But I think as sufficiently, so right now I think it's at about 8,000. And yeah, I don't know what that right number is. I was reading one of Italics blog and I think he even said, I'm not sure how many it is. It's probably more than like a few hundred, but I don't, yeah, yeah, I'm not the best person. I hope the court have thought about that. To nice node. Yeah. And you also talked about making this very simple for people that run on the Windows computer that don't have very much tech experiences. No, my father could run it. My mother could run it in their home. They don't do anything in the tech. So if they get all this setup and I show them what Ethereum is and they put all this money into it and now they have this money running on this Windows computer there and it has no battery backup. It has no, they just shut it down because they don't want it running all night. Obviously now they're getting slashed. And so you have a lot of people who don't know about these things. They don't know how to set up the hardware. Aren't you kind of concerned about that? Or maybe they think I want to set up two. They use the same contract addresses. They set up two and boom, boom, boom. They start getting slashed if you can't have two. Have you thought of like before people get into this? Yeah, that's a good question. Is like if we do make it easy to use like we need to also make it very clear like what they need to do and then probably also make it very easy for them to stop it or withdraw or notify them. So yeah, if we're gonna make it easy for people to onboard we also need it. That's a great point. We need to make it easy for them to kind of get off or help them get off. You mentioned hopefully it comes out during this website later like you edited the HTML for them there. I would think that would be more dependent on how responsible are they. It's a nice responsibility to do that for them to say, okay, this can be used for people to respond because it's not possible. Yeah, I think the quick answer is I would, in the app we're gonna just make it like super obvious, like lots of warnings like, hey, you need to have your internet on. You need to have this computer up. And yeah, hopefully our solution is a lot better than the alternatives. Like hopefully we're way better at notifying people when their node does go down, things like that. Yeah, no incentives right now for a non-validator node, yeah. So, and that's a great point. Like if you're someone who, like the SSD is like a big commitment for you or purchase, like maybe running a full node, I don't want to discourage you, maybe it's not the best use of your money or resources. Like there is no direct incentive at the moment other than obviously making sure Ethereum works and stays up. So, it is, yeah, that's a great point. It's a personal experience, like when the V-container just launched, it was also not the first possible. I thought it would be excellent data, it's a great way to do it. That's all you can think about. Yeah, I mean, certainly we want to make it as user friendly as possible and one thing we have thought about is like letting users opt in to automatic updates for their nodes, so wherever possible they don't need to do anything. And I think that, yeah, that's probably a big part of running your node is, yeah, just doing those updates and then having some sort of like alerting. In terms of like, if some other problem were to happen, like we would try to diagnose it as best we can, but I suppose that, like for an issue we can't diagnose, yeah, I don't have an answer, but it's something I'll definitely keep in mind. Maybe it's possible to have some kind of, yeah, get access to some kind of like command line interface and have a technical friend do something for me. Okay. And basically, so that the UI itself kind of. Yeah, the other thing I do want to have is like, if I'll show the command that nice node that I used to start the node, so you can just copy and paste that command and like leave the app if you want. And then you can just go to the command line and yeah, that's something I want to do too. Right here. Very quick, first of all, congratulations. I really like the new UI that will come. Thank you so much. I have a question that we're going to talk to you on all these challenges because these are like how to get people that's not taking up the ability to in this ecosystem right now. So I really like seeing this kind of UI, this guide into you and trying to get in this without basically not getting the right to say like how to do a one click application. My question is, when your team like build this, it's based on like, there is our waiters behind like for what kind of age or what is the, this kind of people that can't afford like that. This is easy to use because even if this is easy to use for us, maybe that kind of steps and select option and all this stuff that we talk for an album or even our job. There is a re-shirt behind that. Like this is like accurate with this age people or not taking up it forever. Okay, so just to repeat for the stream. It sounds like there's concerns that we need to make sure that if it is super easy to get started that we make either some guide rails or some just make it to the user aware that what they're getting into and so yeah, I mean, what I'd have to say those concerns is I think we could do something where instead of letting like the user, this is just something I thought of now, like click, yes, yes, yes, yes, yes. And then they're good to go like deposit, maybe having some kind of like speed bump, a kind of thing where like they have to either like demonstrate some technical knowledge of like what they're getting into, just sort of like maybe basic quiz or something like that. But other than that, I mean, yeah, did I address your concerns? Was there anything else or no, okay. Yeah, I think maybe some sort of speed bump just so they can't click through like super fast and get themselves into something they didn't know and now this program is taking up all their SSD space in the background. Yeah, absolutely. Right there in the white sweater. Yeah, I think you were first, but blue shirt. So if you don't have any ETH and you're not staking, no slashing, if you're staking with nice node and your node were to go down, it would be slash just like any other node. That's a great question. His question was, could this be a web app? And I don't think so as of now, I think there are limitations on the browser, which you can't basically run a command, a web page can't just like run an arbitrary command on your computer, but like an installed application can. So now the front end part of nice node, we could separate that out and put that as a web page. It's actually like mostly, the front end is basically a web page, it's basically running in Chromium, there's the underlying architecture for nice node is called Electron and it basically downloads Chromium and so it's like it's own little web browser there with extra permissions to interface with operating system. Any other questions? Here again. Right now, no plans. I wanna stay open sources as long as possible. We've been supported by First East Staker in a CLR fund and then GetCoin, two rounds of GetCoin and then we recently got a grant from CityDAO which funded the like improved onboarding experience that I showed you all today. And then hopefully we'll get more grants and stay open source. I've seen people ask that. I think if there could be in the future and I think absolutely, I think there are lots of groups or foundations maybe like East Staker or the Ethereum Foundation who would provide some incentive. I think the limitation here is probably like you need to prove that the person running the node is a human or that perfect humanity civil resistance problem. So I haven't thought through the whole consequences of tying your perfect humanity ID to your node but I think with that people would give out incentives. Other than that I don't know. I don't know how they would do it without civil resistance. If you're not staking or not validating there are no incentives, no monetary rewards. So CityDAO knows how you are like a local home. Where it's probably gonna prove you the city and how they're gonna think about it. You go outside there and you go to the capital. But CityDAO realize how you are running the node and you don't bother your mobile connection that you should have. Yeah, I mean that's something I've thought about. I haven't like quite worked on now but the app can know whether you're on battery, whether you're on power, whether you're on wifi, ethernet. Right now we don't have like any internet speed check but that's something we could definitely add. So I wanna, in the long term I do wanna make it so that yeah you can close your laptop lid, the node stops peacefully wherever you go next. You open your laptop, maybe just plug it in. You eat dinner and it's syncing like while you're, yeah and then also potentially like we get out of setting like while I'm working don't use resources like just run in the back or like just pause while I'm working maybe from my typical work hours. Anyone else? Okay, I think that's it. I posted the slides on the nice new Twitter. There's tons of links in here. So you can check out the slides there. Awesome, thanks everyone. Thank you. And gracias los organizadores y al equipo y a todos. That's it, thanks.