Web3Pi: Running an Ethereum Node on RaspberryPi for Privacy, Decentralization, and Fun.

up hey everybody so welcome everyone uh we are going to talk about uh web freey um which is a community-driven project uh supported by Golem Network um that focuses on making a the ethereum ecosystem more decentralized and accessible for everybody um but before uh we kick it off I'm going to talk about uh the team first of all so I'm going to present uh gentle our gentlemen here in from the team so Robert is our Hardware wizard Network specialist and python developer um ukash has extensive experience on uh blockchain um including solidity and Python and T also known as blue there you go uh he a senior software developer he combines vast experience in Python and blockchain solutions and my name is yakob and I'm product manager of U the web 3p project you see agend yeah okay you can see the agenda first of all so basically uh quickly through let's go through the agenda I'm going to talk about the um let's say the values uh the um the vision the impact on the product ideas sh is going to talk about uh who is this for right and different points of view and he will cover also the important topic of staking all right then Robert will uh dive into Hardware topics and uh note deployment and uh monitoring and then ukash will walk us through the software section and at the end we have also planned a Q&A session all right now in an our goal is to simplify the hassle of running your own node all right where the The Other Extreme will be using the third party Services um with all the limitations pros and cons you can see the uh such a small device it's it's really really capable and how do we want to um how do we plan to to change that approach uh that has been uh present in in in our in our ecosystem in in the blockchain space we want to provide battle tested uh Hardware specifications based on Raspberry Pi we also um deliver the automated simplified deployment uh procedures and node installation uh processes then we were uh we offer a number of solutions uh software Solutions like RPC reverse proxy admin panel and transaction firewall and um these features will allow you to interact um with ethereum network without external limitations on RPC calls which is super super important while ensuring the uh the privacy and security features so um before we go into details who is this for and how we can use it actually I want to talk about the core values behind this project which is uh the topic that is really close to my heart um so first of all um the independence topic that means you don't have to rely on big companies right to to manage your data and apps and with web 3 Pi Project um you actually you actually uh control how you interact with uh ethereum blockchain you don't have to rely on thirdparty Services third party centralized Services which is really important for us then decentralization is about spreading out power so that no single group or legal entity is in control and then the the ownership me that means that you own your own your data your interactions and your role your role in the um in the network so with our solution and it's future ecosystem um you'll have the tools to take that control back that's that's what we what we plan to do and um there are couple of benefits of uh using this uh this approach so first of all everyone may have their own preferences in terms of benefits and um but we find those here listed uh on the slide really really important so first of all we really really cherish uh our private privacy in terms of interaction with ethereum node um secondly we really really appreciate the reduced uh Reliance on third parties I really talk really much about it that's rally important um and we want you to be censorship resistant and at the same time improve the centralization of the interium network and last but not least when you run your own node nobody controls the numbers of uh RPC calls you can perform every single day right and that's really really cool because uh We've uh tested our our our setup and we had uh amazing results we reached uh 100 million RPC calls per day right iner certain set we uh even reached uh 200 Millions which is amazing but at the same time other service providers centralized service providers they they offer you like 5 million per day so if you if you compare those two right like 5 million versus 100 or 5 million versus 200 which is amazing this is really really uh fantastic project because like in such a small device uh with such a small device you can actually um virtually have multiple and uh unlimited uh numbers of calls per day so and you can share them uh with with your friends with your colleagues at at work and so on right so that's really really really really cool really um I would say fantastic project I'm really excited about it and um that's just the introduction to to our uh presentation and now I'm going to hand it over to to Blue there you go so hello um so who is web 3 pi4 um so despite its minuscule footprint uh and that means both in terms of physical dimensions and power requirements but also in terms of uh the initial setup overhead that's needed to run such a device device uh it's web 3 Pi still allows almost anybody to round their own full ethereum node in the most straightforward possible way and it's the perfect gadget for anybody who wants to interact with the ethereum blockchain uh without relying on external service providers so without pay subscriptions and um yeah without any external dependencies and now I'd like to show you a few use cases for the types of prospective users of our device so uh if you're a decentralized app developer uh your personal full ethereum node uh running on Rasberry Pi becomes uh an unlimited playground for you uh which you can use to run massive amounts of queries and transactions as uh W oh as showed you uh and that means you can run various experiments with your apps you can develop your apps without ever worrying about running out of subscription quotas without relying on external Services similarly if you're a decentralized app operator or any other entity who wants to run ethereum nodes for your users uh you basically got the same benefits as as a uh decentralized app developer but on top of that if you need more power more more uh more capability you can easily Bridge multiple devices and we give you the tools to do just that and our uh the web through by proxy um allows you to connect multiple devices run them on a single address at the same time load balancing the queries and um giving it tools to control that usage for power users of the crypto ecosystem we give you the independence and security that you need on one hand by running around full ethereum node you gain certainty that the results of your queries have not been tempered with on the other hand um and that your work is not visible to anyone else but on the other hand uh our tools such as transaction firewall uh give you additional layer of safety by ensuring that you can only interact with the contracts that you have previously white listed and that you can verify the details of the transactions that you sent to the network before you do that and finally what I think is maybe the most sexy uh aspect of the device is the perfect gadget for solo stakers um and it's small form factor um uh it's still the device in includes all the components uh required to run your own staking note that is the execution client the consensus client and virtually basically as many validators as you need and all of those components have been carefully selected configured and we I must say positively tested uh to work seamlessly on the recommended device setup and thanks to our uh to uh thanks to the work of of our team uh we give you we give it to you in a form of comprehensive package ready to be launched in minutes and now I'd like to pass voice to Robert our Hardware hacker and M magician who will introduce you to the tiny Wonder itself okay let's dive into the hardware topic web fre piie was designed for Raspberry Pi single board computers uh the Raspberry Pi 5 is powerful enough to run uh a full ethereum node on a single device but you can also use two Raspberry Pi for units when one serves as a execution client and the other one as a consensus client we choose Raspberry Pi as a hardware platform for several reasons first of all it has globalwide avability and Broad network of Distributors uh it has been well known in the market for years and has built a large active large and active Community Raspberry Pi is a cost effective and offers a wide range of accessories that exchange their capabil capabilities uh for example nvme uh adapters uh for for storage cas is displays and much more it's very nice ecosystem the heart of the Raspberry Pi is energy efficient arm processor the whole setup consumes less than 10 wats of Power with C current electricity uh prices in Poland it cost worth about $22 us to run your full ethereum note at home per year uh the complete Hardware is compact enough uh to fit in any corner and and this device can operate 24 hours a day 7 days a week without any an issue did you know that with the web freey project you can build you your full ethereum note in less time than this presentation yes that's because we have significantly simplified the entire process by creating a dedicated image for Rasberry Pi by developing a fully automated installer providing step by by step instructions offering detail detailed uh documentation and support and the list of compatible Hardware tested in a bottle with web Frei anyone regardless of their level of expertise can set up their own full ethereum note at home as I mentioned earlier uh you can use either a single Raspberry Pi 5 or two Raspberry Pi four units version five is powerful enough to run both the execution and consensus clients on a single device this simplifies the setup and reduce Hardware requirements for version four it's recommended to use two devices one serves as execution client and the other as a consensus client this configuration ensures that each client has enough resources to operate efficiently without overloading a single device on the right side you can see the raspberry 5 with an active cooling uh USB 2 terab storage and official power supply that's all you need to run web fre piie and you your full ethereum note here you can see uh example of dual device setup uh it consists of two raspberry pies with Al also active cooling uh two external storage over the USB those are SSD drives network switch and the power supply that's that's all in a moment I will discuss the deploying process but first let's take a look at the recommended Hardware requirements of course you will need Rasberry Pi 5 with 8 gab memory 8 gab is required uh smaller version uh will not work uh you will also need two terab of fast storage for ethernet blockchain copy uh and vme or SD do not use HDD they will not work uh it can be either the m.2 storage in which case you will need appropriate adapter uh or just an USB 3.0 storage as on the previous slide both option are supported by web Frey installer you will need of course relable cable internet connection with unlimited data um active callink is necessary the synchronization process UTI 100% uh raspberry peace resources generating a significant heat from from both the processor and the search uh active cooling is required to manage this we support automatic fun control speed to to keep the no as quiet as possible uh you will need uh a Micro SD card 32 or gigabytes or bigger uh for our image by the way our image is based on the new ubun 2 244 LTS uh and as always uh proper power supply is crucial as the processor combined with big two terabyte storage can have uh significant current drow during the peak usage we have created a comprehens comprehensive documentation and the list of compatible Hardware so please refer to it for more information uh and this is uh what the entire setup might look like after the assembly uh please notice the colorful display integrated into the dis enclosure this is our own modification uh using a 3D printer you can print a custom cover that allow you to mount a colorful LCD display which shows you the most important note and the operating system um parameters in real time uh we provide uh both the fre model and open source source code uh you can just download it from our GitHub page uh here you can see the web freie development deployment process in five steps as you can see the whole process is very easy uh all you need to do is down on the web Frei image uh flash it on a Micro SD card then assemble the hardware which consist of Raspberry Pi power supply micro SD card and of course the storage and connect the power uh then the automated installator will do everything within 15 minutes uh and start the blockchain synchronization the blockchain synchronization on Raspberry 55 um took where about 19 hours uh of course we have tools which I which give you an option to monitor the installation process uh from the very from the very beginning through the through your browser uh and also you can watch the synchronization process uh through grafana also from your browser uh here you can see our custom grafana dashboard uh considering the limited resources of the Raspberry Pi we develop a service that queries uh notes for statistic in the way that is uh less resource resource intense than traditional solution built into the execution and consensus clients uh on this dashboard you can monitor the key information about the note and the operating system like the CPU usage with history uh synchronization status chain head Ram swap storage usage and a couple more information uh okay let's assume you already have your atum note synchronized what's next I will hang it over to my colleague blue so hello again um so along with the device itself we are provide our in our ecosystem we are providing a couple of software components that makes uh that make the usage of this device more uh easier and more versatile and one of them is uh web through by proxy or the RPC reverse proxy so what is very core it is a reverse proxy uh listing on a given most likely public TCP port and public address and forwarding the requests to one or more um ethereum nodes that it has connected uh the proxy itself contains a load balancing mechanism uh that which distributes the queries to uh specific nodes based on their utilization and it keeps a health check with each noes so it disables and re-enables uh queries to specific nodes based on their Ava availability and even more interestingly it's also able to parse the Json RPC requests receives to keep track of the types of those requests the volume of those requests and the potential uh utilization of the device that caused by those requests and those metrics can then be used for data agation for statistics purposes and also to control the usage of the device uh to control quots and so just a quick uh quick um view at how you use the web through app proxy and it's uh it's straightforward you install the package uh Define the end points uh that of your notes with the ver Environ environment variables uh and then you just run the proxy and once it starts you get the address of the proxy uh you confirm that it's connected to the devices and you get the administration uh panel address with your own personal to that you can access to uh to manage the device and now I will pass voice to ukash who will tell you about the proxy and other software tools that we give you yeah thank you okay um our ecosystem grows and it contains many components um admin panel actually is the front end for RPC reverse proxy it is used to manage this this component that uh uh blue was describing this page uh is actually the the single play uh page of the admin panel it will be replaced with a more friendly dashboard in the new future but still it is an excellent place to talk more about our Concepts and directions directions in our future development um and we I will focus on that uh the primary primary goal here is to manage and control access to Connected nodes according to defined policies whatever these policies would be the over overall principle is to make this functionality easy to extend to remain open adaptive to let others add their stuff to this to this component and um yeah to to remain open for for future [Music] needs um on for the moment uh we can check the state of connected nodes it is the right side of admin panel uh first we have the status wherever connected nodes are healthy active or disabled because of failures or maybe out of sync because they are delayed with blocks the status of connected nodes are detected live by the proxy and updated in admin panel we have also basic stats in term of of uh the number of calls processed by a a note uh in terms of um traffic volume processed by a node having at least two end points you can see how our load balancing is [Music] working um we will add Dynamic nodes management there will be buttons to add to remove to disable activate new end points during the Run and we'll add more info on notes um condition for instance an a processing time of the requests how how uh effective nodes are and there is more to expect in this in this section for instance differentiation on archive nodes and not archive nodes priorization uh of nodes defining backup nodes connecting via tunnels to nodes that residing in internet without public IP um this also how shows how we are thinking about this component on the left side we have users management users actually are any entity that make calls send calls uh to the RPC endpoints uh so we have uh API Keys each user is uniquely identified by um by its IPI key and this concept actually is similar to those that we can find in other RPC providers meaning that uh the IPI key is a part of access URL that can be used in DBS a management consist of um adding removing and updating configuration of users configuration the configuration of users contains the limits the limits of calls that can be processed by by a single user and the limits of uh traffic volume for a user these are simple quantities for now uh what we are planning to provide is quite obvious billing payment methods user front end keeping in mind keeping in mind uh that it is particularly important to remain flexible um yeah and we want to use this infrastructure from web free user perspective um let's do do a basic thing and connect a wallet to a reverse proxy and just it's it's simple right uh here we have metamask metamask is also uh obviously just an example you can use any other wallet as well it shouldn't be any difference uh in the demonstration we create a new network it's a copy of mainnet and only thing that matters then only that is specific for us is the RPC URL and this is the address of delivers proxy along with users API key and that's it we can also connect web Shi nodes directly it is just a matter of setting the right RPC URL in this in this place well we click uh we can click save and use this um and use our infrastructure in a web browser having this this network uh what next let's connect DBS we have a wallet connected we can collect DBS in this example we connect Unis swap we are not any particularly con related to uh to to Unis swap you can use you can try any other DB as well the routine is quite obvious here ensure that metamask switched to the correct Network the network linked to web free infrastructure and connect the the wallet to the to the app when it is done when everything is set up we can perform some operations and in admin panel just to generate traffic just to send some RPC calls and in admin panel we can check that the usage starts increases so the whole round works and that's it too far another example at scan uh there's not much add here there's not much to um talk about here just uh it is done and and it's working but um this is an occasion to tell about a possible change in DBS what is what would what change it would be quite often dabs developer rent RPC end points from big and stable very often Central ize etherum RPC providers and developers provide these end points in V DBS so DBS can run smoothly and this is very often thing the change in this paradig would be to allow end users to choose the RPC they want to use within a Dap particularly they could choose webp infrastructure the key word here is trustless of course there's other implications and there is a lot of space to discuss but still the the idea is valuable and Worth to discuss in the future well no privacy privacy uh no privacy and that's it this is another component let's let's switch to another component which is called uh transactions fire wall plant um a general purpose is to increase security it acts as a proxy between a user and infrastructure and it inter intercepts transaction and force additional confirmation in case it detects some sensitive or suspicious transactions operations it is still in very early development so far a primary scenario is as follows first you need to configure and uh run the transactions fire or you can specify authorized uh addresses you can specify known contracts you you can specify ABI here and um one of the configuration elements is the back and ethereum RBC endpoint on front the transactions firewall exposes its own RPC interface and acting as a proxy as it should now a user sets the transactions firewall address in it wallet or a web page or a script or a uh tool any client that is capable to send RPC calls and from that point every user's action goes through the transaction firewall as a source of transaction doesn't matter the transaction firewall made to decide to ask for ADD confirmation and this is the example of such a situation well we plan to integrate this tool with other components there is some software around with similar functionality but the point is that we want to keep it flexible expandable having in mind the whole our ecosystem to Feit this in a bigger picture and I will pass voice back to back to Blue who will tell more about other [Music] components well actually maybe not components but use cases so uh staking uh if you have thought about embar embarking on this uh exciting Journey that is solo staking on the ethereum main net uh we have I think wonderful news for you uh it's perfectly possible to run not just one but as many validators as you need on web 3 pi and generally uh with solos taking uh you you gain uh control full control over over your Stak um without relying on staking pools or on liquid staking services and in stake uh instead uh you stake your ether uh by yourself in directly in a deposit contract and you use your own full node to to control your stake to to to run your validators and best part of it is that not only we have provided the necessary setup um on the device itself but to confirm uh we through pice Readiness for this scenario we were able to conduct some desks using an impressively high number of validators or all running on a single device on the ethereum main net and we are happy to tell you that the results we've seen are simply impressive so just a quick recap on how you would embark on staking uh with uh we 3 Pi so you start with a fully sync note so we have to wait until your device sinks after it starts then you basically follow the Launchpad this is the official website that allows you to St ether on your own uh two steps are most important the gener generation of your validator keys and the using the the interface to deposit your 32 ether into the deposit contract then there is a weight um um associated with the processing of the deposit by the Bon chain you can always check the status on the Bon chain status website and it can take several hours for this to happen but in the meantime you can add your validator keys to Nimbus um and um you just restart the Nimbus service and you wait for uh the contract to process your deposit but anyway voila you have your own staking note controlling your own ether stake as simple as [Music] that uh now I'll talk about uh for a moment talk about the staking performance so our researchers were able to conduct long running tests on the ethereum main net and we're able to test the device with 200 validators we think that likely many more are possible and it all runs on a single raspberry 5 device and the best thing is that they there were basically no attestation loss uh so you don't lose any either because of any issues with the device so um yeah while while we perform our tests the CPU and network load remained moderate the entire test setup consisting of the staking node running on Raspberry Pi 5 the auxilary helper node uh running Raspberry Pi also which was running Lighthouse and was used for additional tuning of those tests the metrics to be running on Raspberry Pi 4 router and switch all that takes less than four 24 wats of power so not too much and you gain your own full uh full staking node and some other components this is the exact setup that we used so if you want to reproduce it you can uh you can verify that um that uh your device is up to par and as you can see this is the the screen that Robert showed you earlier and this is uh the the statistics for the device uh while it's running 100 validators as you can see the CPU load remains low because it's it's not even using one CPU core and so the device is just running uh normally also the network traffing uh was moderate the peak was 200 megab combined upload and download and and maximum 18800 connections um so yeah these are the statistics for the attestations this is the data for 60 validators collected over 28 hours 99.94% hits uh then we have data for 75 validators collected over 17 hours also 99.98% of attestation heads some really negligible loss and this is the most important bit of data we were able to run 100 validators over 120 hours so far and the uh attestation hit ratio is close to 100% still no issue for the device and even better we we were able to run 200 validators over 31 hours so far and the adapation is with the rounding error 100% so yeah maybe there's it's still not a limit um as an interesting side note while performing the main at staking tests um uh the device um experienced an internet downtime and while the validators obviously lost their attestations during the event itself after the return of the connectivity uh the device was able to sync and to to recover fully without any issues and was best while it was rebuilding the load was very high it was close to maximum but the still the attestation loss was [Music] negligible so the conclusion here uh is I'm going to quote a 2022 study by Adrian Sutton exploring adh2 of adding validators he in in his research he found out that the first 64 validators that you add to a node are quite expensive in terms of CPU usage and network traffic but if you can run 64 validators well then you can likely run thousands of validators well because you're already processing the bulk of attestations so given that we believe that quite impressive number of validators is possible on a single web 3 Pi node and now I will pass voice back to yakob who will tell you about the next steps in our project thank you blue so let's talk about our road map as you can see we are in the PO phase at the moment um but we have really really impressive um future in front of us at this point we have node installer monitoring uh reverse uh proxy and admin panel buil and tested including staking as you can see and as blue was talking about and upcoming months you can see the next stages of our project um a channel and prox here will uh will be done in in upcoming months in the MVP um Vision one we we want to improve our admin panel um metamask Integrations and and we want to uh do some additional benchmarking and then if you think about the next stage MVP uh version two uh we want to um include public IP U mapping services so basically you can um manage your nodes uh we want to also um include uh additional Hardware uh setup and config ations and recommendations of course with the uh the documentation and and and um and Etc and then um at the end of of this year we plan to have a uh payment Gateway uh in its uh MVP uh version and also of course the end user management so if you think about these uh things that we have already uh talked about like the admin panel and and the things that uh W was talking about basically that was something that was uh done from the perspective of a note provider if you run your own no at home or the office uh whatever but then like if you think about end user management you can create you uh accounts for external users like your friends and others right and that will be also the P payment um Gateway and uh at the very very beginning of 2025 so basically uh uh q1 we want to launch um the web 3p platform which is basically uh the entire full-blown um let's say uh product with with um the U uh end users as I said like staking uh public IP all the all the features that were we we are going through the the the entire road map developing there we want to go to the market with that in 2025 the exact date will be provided of course um but that's that's our um let's say plan for 2025 so once again we have we P platform go to market and further uh further funding um so if you want to join us because we are we are the open source uh project you can uh scan this QR code and we simply go to the uh web free web f um ksub and then um you can also look at our website web3 pi.

and you can join our our our Discord this is our uh QR code for for Discord and by the way tomorrow at um 2 p.m we're going to run DIY workshop and we are going to assemble everybody will be have uh have this opportunity to actually assembly like set up the the um Raspberry Pi from scratch like with some welcome boxes and um yeah like please go to the uh Discord write your your name you want to say that you want to join tomorrow Workshop the the spots are limited please bring your laptop all right cu you are going to need it and yeah that's time for questions and I'm not probably able to answer all your questions but my colleagues probably will can you back to 100% obviously that one I can actually answer quickly yes sir so my question was about the D actually like because you said that you are running an image just based I the the latest one I mean the the I mean is there any reason for that because like I know that actually many other you know like images that much suitable to Rasberry P like for example diet p is like quite uh you know resilient and also optimized for the raspberry pies and you may gain a lot of you know uh performance though uh I think you is very Universal and Everyone likes it uh and Ubuntu from version 244 I think is quite s table for Raspberry Pi and I think optimalized Yun to announce that it's uh ready to run on Raspberry Pi uh products uh I I make some benchmarks between uh official Raspberry Pi operating system and Ubuntu and difference in performance was where about four five% maybe in single task uh perform benchmarks there was a little bit bigger uh difference but still it's um 10 12% in a single single uh treat task but in the multi- Tre task it's worth about four or five% of difference uh like will it be possible to like tune this uh configurations for example I want to run my uh different uh could you repeat the last sentence like the question is basically like uh like do you have all these configurations and images open source so I can tune and change the configuration yeah of course the the whole uh project is open source you can find it on our GitHub uh um starting from the creating our image you don't have download our image you can build it your yourself uh we have tools for that uh of course uh you can watch see our code uh totally uh you can twe tweak uh properties parameters for G for for consensus client by the way uh we one of our optimalization is to use uh nimus as a uh consensus client and we found that get plus nimus is a very good tandem for low resource devices it's very stable uh solution uh and we we prefer it we recommend it but you can use our config file maybe this is quite interesting thing for you you can choose uh at the beginning when you write uh flasher SD card uh for those which are familiar with Raspberry Pi there is a config file when you can set some parameters we use that config and uh inject there our parameters so from this uh from this simple uh config file you can uh choose if you would like to luse for example Lighthouse or nus uh you can choose on which network PKS they will you know talk to the others uh and some other parameters uh and then when you save it and put it in the Raspberry Pi the installator within right now 7 Minutes uh we'll configure install everything uh for you uh and start the synchronization process so yeah you you have uh full access to everything amazing thank awesome other questions mention previous previous version of U we have some problems with previous version of but the latest version of works like can you back to slide with uh ethereum St because on your website I didn't find yes this is a hot hot news and you are the first to hear that which uh back configuration yeah yeah yeah back more again yeah configuration one one one more one more we can we can talk about later on if you want like I can give you yeah you want to make no no more more this one so yeah I have a good news for you tomorrow tomorrow we will have workshops and we will go through this procedure in come to the workshop once again we have a workshop at 2 p.m. tomorrow like everybody's invited right and we can sorry yeah so everybody's invited just come to the workshop and we'll uh like uh first of all as I said assemble the the the device itself right then we run the note and then we go through all these uh um blows and whistles and we will uh play around with uh with with the software itself right just one one caveat is that the first point is you start with a fully sync node so it's not really possible to start on the workshop with the staking because the synchronization process takes like several hours but uh we will show you how to do this on heski uh test net and you can do the same on on Main net if you wish but you will need 20 uh 32 it of course one more question is about it uh uh will not give away yeah I can I can uh use staking not and and uh RPC on the same device yes yes why not you you you can answer yeah any other question yeah go ahead are you thinking at all about other networks based on that what do you mean by that that like2 not at this point we are focusing on on ethereum at this point first of all we want to you know like build the entire the entire product itself like a platform focus on that we want to support uh ethereum Network first of all and the centralization of this network which is really really important for us and there are some discussions but nothing written in stone at this point check check when there's questions can you just make sure to uh repeat it into the microphone cuz I want to capture it in the we want to capture it in the stre thing yeah anyone else here do you want to yeah take your mic all right uh can can you show a slide with uh with uh road maps with a road map okay yeah let me look for that uh this one right uh right now we still here November 24 September uh there you go but but I already got that you have MVP you know yeah I mean we are in between we are still testing some some um you know features that were already tested there are some uh things that we are still still improving right what we are showing you right now they are basically uh the POC stage of of the uh the maturity of software right but we want to get into the this the place where we are going to have this um all these features well tested and mature enough to go to the market itself I don't know it doesn't answer your question uh yes but I I I I want to understand your goal uh go to market market uh what what do you think how how much it it will be Market it's going to be huge no but but maybe no really I we we don't have uh numbers that I'm going to share with you at this point right but first of all what we want to uh what we want to actually address is the the the decentralization of the uh notes providers ecosystem and that's that's our main focus at this point I think that not so much people uh can buy raspberry uh deploy or node and bring to to ecosystem I I think but I ask you what you think maybe you think that everybody will do it I don't think everybody will do it and welcome decentralized World should do it but everybody should do it yeah exactly maybe not everybody will do it but everybody should and at the same point at the same time I think that um you know there are certain benefits of running your own note it's not about decentralization only right if if if if we go back to um you know like early St stage of this presentation the couple of numbers that you think about when you think about them like hey like I can run so so like so many millions let's say of RPC calls per day without limitations so like when you think about um web 3 users right and Technical um let's say do developers right or um people that want to interact with the with the blockchain in a private way in a way that they actually own they the interaction the way they interact they don't want to rely on the uh centralized entities these are our Target groups that's this is a target group that actually we want to address thank you thank you okay all right in the back yeah once again what what's up dog here so I guess if I buy a bigger drive I can easily put an archive note on that p uh AR of have question to Robert I do not try this already but I think uh it can be possible with a big enough uh Drive um I know you guys are I don't know like how's your energy do you want to rrap like I you there's so much coming at you right now uh if you can please just one more slide go back please I had to I had to um yeah this is great this is great please continue if you want I'm happy to run around whoever like please keep it going here you go dude so I have a question about performance tests you said uh 200 million requests per day uh that's more than 2,000 a second a very impressive number for Home usage but my question is uh what Hardware uh configuration did you use to reach these numbers and what are the requests that you tested uh okay I can say about the hardware and colle my colleague ukash will say about uh the itself uh the hardware is of course Raspberry Pi 5 uh with 8 GB memory and slight overclock uh we use we usually use 208 uh 2.8 GHz uh clock um we use nvme uh Drive uh for the storage blockchain blockchain copy uh and that's all this is a Rasberry Pi with two terabytes and VM storage and the client was running on another machine and you use the network interface right yeah the client which makes text yes it's on other device and one gbit normal interface yes speak about it yeah about the 200 Millions it was a peak the the the highest value we we achieved and of course everything depends on the setup of Benchmark right um what is important here with this 200 Millions is that we use keep alive for connections so each call were using previous connection and the the the device did not have to create a new connection on operating system that uh save a lot of resources and a lot of time uh so it's a peak and um obviously not every call is uh the same does not uh take the the same time uh we picked uh get locks of a benchmark and each call was asking for a different block just to avoid cash caching right and that was The Benchmark this way we achieve 200 Millions we have different setups here right that we can talk about more yeah yeah so without keep alive we drop to 3.

5 million uh yes yes if uh each uh call um establish a new connection uh drops to 3.4 Millions but if we uh put an uh Interceptor between um in terms of proxy uh the the the the uh the the performance increases why because proxy uses keep alive by itself connecting to to the to the node so even if the Benchmark tool is creating a new connection each time the proxy handles it and using keep alive connecting to to with the device with the Raspberry Pi okay thank you so basically maybe quick uh um kind of a summary of that like raspberry p with no keep alive it's it's that's that number which is not really impressive but if you add the reverse proxy on top of it you have you have 95 million right so that's really impressive anyway of course like I I was talking about these uh these numbers and I use the uh 200 U as a peak number right but that should be a stable number we are still in the PC phase so we are going to test it of course right but this is these are the the um the numbers that we are achieving in our uh performance test at this point of the uh of the development stage of of P MVP uh phase of this project any other question and one going once going twice sold to the p man yeah thank you everybody [Applause]