Your Wallet Isn’t Safe by Dr. Sebastian Bürgel

hello hello [Music] and welcome everyone my name is Sebastian I'm founder of Hopper this is my third time at East Denver and I'm exceptionally excited to be here probably the most excited I've been now it's been three years that we've been working on Hopper and today is the first time that we are actually going to launch the first commercial product on top of Hopper and yeah I'm going to talk about that and I'm very much looking forward to this Workshop before we dive into what we're building now let me start with a quick recap for the ones who are not familiar with what we're building with what this infrastructure of Hopper actually is so the hopper Network let me try to start this short video here so the hopper network is basically allowing you to transmit data privately and securely so you can use it for any type of data exchange between two parties on the internet we might be wondering well what is different from Hopper compared to other Solutions an important thing is we focus on metadata right so what we do is the hopper protocol is actually breaking down packets into individual little pieces that look indistinguishable from one another and then they're being sent through a large network of data relayers that's where the name Hopper kind of comes from and each note is mixing up these packets that's why it's also called the mixnet so nobody knows where data came from and where it goes to and that's how Hopper provides transport level privacy so if you want to check that out you can go on hoppernet.org protocol and find out more about what this protocol actually does um it's incentivized so we have a payment Channel implementation where the individual node Runners who are relaying data packets for others are earning Hopper tokens when they can provide a proof that they worked honestly so there's kind of a unique innovation of Hopper and it's what we call proof of relay now this sounds a little bit abstract and I know many people here are into like D5 and nfts and stuff so I'm going to take you through a practical example before I get started can I get some hands up on what sort of wallet users we have in the room who here is primarily using metamask hands up okay as a lot of people who here is using block wallet yay privacy friends thumbs up good job who here is using rabi okay well I'm gonna show Robbie today but then Robbie is underrepresented here who's using frame okay A little bit of frame love in the room good all right so um what I'm going to show you is first some awareness for where ethereum wallets today are leaking private information that might not be so obvious to some folks here in the room so we built a tool called derp and if you want to play along you can totally do that you can take out your laptop it's going to be more fun on a laptop than on the phone although in principle it probably works out on the phone as well you navigate to derp.hoppernet.org and what derp is is basically a proxy that relays your ethereum like requests that your wallet is exposing to RPC providers and what we set out to do here is to really visualize what is going on in your wallet under the hood so I'm going to walk you through this setup here and as I said I'm gonna show Ruby here today um just because I think it's a nice wallet that is very clean and has a focus on privacy as well so what I'm gonna do is I'm gonna set up derp so derp is basically visualizing these RPC requests on any evm chain so since we're friends of gnosis and the noses ecosystem I'm gonna show how to use this on gnosis chain so I'm gonna copy this um RPC URL so you see it's basically a custom URL just like any other and then I'm going ahead in rubby so I've set up my rugby ball but again this works on any wallet including metamask I'm gonna add a custom RPC and I'm going to configure it for gnosis chain so as soon as I do that you see this table which was initially empty down here is populated with metadata now the second I connect it like I didn't actually use my wallet yet right I just configured the RPC endpoint we see that it did already a bunch of requests and you're saying yeah okay it needs to know which chain it is on it needs to know its time right of course it checks the block number and so on but already now you see a bunch of information that discloses personal things about me like it tells you I happen to be in Denver you see my IPv6 here you see the individual requests are being sent like from a user agent that discloses I'm using you know some Linux system and something about my browser and you know many of you might say hey I don't really care so much it's going to get worse than this so let's actually start using the wallet because again all this is exposed to your RPC provider before you actually start using your wallet so again by the way none of what I say here is meant as a dunk on Rabbi Rabbi is an excellent wallet this is something that is intrinsically happening in any evm chain and in fact in most peer-to-peer networks out there so we're talking about fundamental privacy issues and yeah we set out to change those and I'll get to that in the next session so in rabi I have a wallet connected it's the hopper daf Bank we use this to fund accounts as we go ahead and you see as soon as I clicked on the wallet there's a bunch more requests being being sent out so um at the first demo I'm just going to send some eggs die to myself it's a bit pointless but you know just to make a point so I'm gonna I'm also a bit cheap that's why I sent myself 0.1 US dollar sent now this is kind of interesting right so before I send this transaction there's a bunch of further requests that are being sent first of all there's this if get code why does Robbie do that well Robbie does that because he wants to find out who he's sending money to are you sending money to an eoa or smart contract in this case it found out well there is no code on this address so therefore I can submit this transaction with a default 21k gas the next one that it does is it does the get transaction count on my on my address because that's required for the transaction right if you want to format any theorem transaction you need to know the nons and that's why it it queried that one from the RPC provider so at this point I have not done any theorem transaction but the RPC provider knows already my IP address it knows some things about my computer and it can link that to my ethereum address and I found it pretty profound even though nobody talks about this why imagine you're doing everything right so you're using a hardware wallet right you're using maybe even a multi-sick like something hypnosis safe you might use different devices right you have like your proper hardcore device which you use for these transactions that you only do very rarely chances are you use it from home right and chances are you're on the same Wi-Fi network connected to the same router as your you know random fund aping around account now these two accounts are linked and the primary identifier is actually not your ens you know I'm a big fan of tornado and proper on-chain privacy Solutions but the primary identifier that people are going to use is going to be your IP address your IP address is the primary identifier that tracks and links your accounts As you move across the web 2 and web three and that is a fundamental issue okay so finally let me sign this transaction so we'll see what happens here so the final step that was just missing is the send raw transaction so I just you know send a transaction on gnosis chain and we see everything that happens under the hoteer by the way another reason that I use rabi and not some other wallets is rubby is pretty clean it doesn't sound like a ton of requests out all the time you see it only does what it actually ought to do in order to function properly now to make this a bit more interesting Beyond this you know blatant linkability between my ethereum account and my IP address I'm going to do some D5 um so I'm going to spread some sushi love here I'm going to use Sushi swap and yeah so I'm gonna go ahead and switch like one cent of X die for gno and just to see what's going on I'm gonna put this next to each other um yeah so the last thing that was sent in my Rabbi wallet was um what's this transaction to myself okay cool now let me initiate a swap here at this point there's a bunch more things going on this is interesting right so what's happening here it's an estimate gas let me make this a bit bigger this is an eth estimate gas like I know there's many ethereum people here in the room so there's nothing new right why does it need to do it because the dam wallet needs to find out how much does it cost what Sebastian does but let's look at this from a privacy angle before I send a transaction I disclosed a whole lot about myself I disclosed for example from where I'm about to do something and to where I'm sending a transaction let's check this one out on those scan so what's going on here unsurprisingly this is the sushi swap router right okay so the RPC provider at this point knows that Sebastian from address 0x24 something is going to use Sushi swap but of course it doesn't stop there right so let's look at this function ID by the way one super useful website is this four byte.

directory which allows you to kind of decrypt like this function identifier and we see this as a swap exact eth for tokens so what I'm going to do here is I'm going to swap the native asset to some token okay and again all that information is available to the RPC provided before I made the transaction all right so that reveals a bit about me now let's see what else is going on here so I see something back here that does look like suspiciously like in ethereum address right so let's check out this address what's going on here oh this is the WX die token right the wrapped X die token okay so now RPC provider knows I'm going to spend some X die on Sushi what else there's another thing that looks suspiciously like in ethereum address here let's check out that one and again pretty much totally unsurprisingly this is the g o token on gnosis chain so you know everything that I'm about to do on this chain before I made a transaction right so maybe there's some Searchers here in the room that's information which gives you proprietary insights to front run the mempool so you can say Hey you know again these RPC providers I trust them and that's fine you know I don't think that inferior and Alchemy are bad guys but I don't think this is the trust assumption that we should build the web 3 on more importantly there's extremely smart folks at inferior but also at other projects such as pocket Network working on decentralizing this RPC stack if there's not a random dude on the internet are you going to trust them with that information that I just disclosed here now that we've seen that you know basically Mev is a billion dollar industry that's pretty juicy information that you can actually use to front-run the main pool so my punchline here is and now I've been dragging this on transport privacy is a fundamental issue that needs to get fixed to have the web 3 safe and secure for everyone but also to really enable us to use these amazing truly decentralized applications that very smart folks are working on all right so since that is an issue um what can we do to make it better what can we do to make things better so and at this point let me make this full screen I would like to introduce to you rpch as the only private blockchain Gateway so what we're announcing here for the very first time is an RPC provider that is provably private yeah so and I know that there's a bunch of folks that try to build something that's a bit more private by proxying RPC requests what I'm talking about here is leveraging the hopper Network this packet relay infrastructure in order to build actually truly hardcore private RPC services for any wallet out there so um just as an overview you've seen this demo here on derp that's what we seek to improve right so effectively we want to open a new dimension in its RPC space from you know just being centralized to decentralized we want to make this private right so how does it work and make this a bit bigger so on the one hand side you have your favorite crypto wallet your favorite crypto wallet is now augmented by an SDK of rpch now you might wonder why do we need this well we need this because the underlying transport infrastructure is not HTTP which again uses basically TCP it uses the hopper mixnet so unfortunately wallets don't talk Hopper natively and that's why and that's something that I will show next we need a connection infrastructure between your wallet and this Hopper Network and the same thing on the other side we have this exit node and the exit node is then kind of taking this payload forwarding it to some ethereum nodes and sending the response back and in that way we have entirely decoupled your wallet from the RPC provider not just by a single VPN or a single proxy in between but by multiple um in between nodes that decouple your IP address from on-chain information cool so let's look at how this works in practice so I'm gonna try to access our PCH here so there's two options how we can use rpch today this is not a demo that you know works at some point you can literally try this right now yourself so um the simple way is I'm going to go first through the more interesting way because I know this is a deaf event so you know let's check out the way to use rpch on any wallet on any evm chain so what you got to do is you got to download a Docker container and this Docker container has an API secret for now this thing is totally free of charge so you know I don't I don't care if you troll me and just screen screen cap the secret here and I'm going to run this Docker container which is this connection element that we mentioned before which on the one hand speaks Hopper and then the other side exposes a standard ethereum RPC server locally on your computer so that your metamask your tally your frame your whatever wallet you're used to can connect to now I'm just gonna paste this in here you don't need to see too much in here I'm just gonna gonna demo what it what it does so since I have been running this on my computer already it doesn't download the container if you run it for the first time otherwise it would download the docker container and uh yeah install it so it might take for you guys who who want to try this out it might take a few seconds longer so the next thing I'm going to do now is I'm gonna go back to rabi and the other thing I still have open here on my on my Rabbi is derp right so now so we see these requests which Robbie was sending to an RPC provider and what I want to show now is that when I connect rebby to the same RPC endpoint but through rpch we won't see any further requests so let's see if this works so what I'm going to do here is I'm not going to use the default provider which is suggested here but I'm going to use exactly the same provider that we had before this dirt provider which I which I've been using there so I'm going to go into rubby again custom RPC and I'm going to prefix it basically so what we do here is um we basically run you see this HTTP localhost 8080 so that is the docker container it's exposing an ethereum RPC provider on port 8080 and we pass it the exit provider and the exit provider is the one who actually serves you ethereum requests right and again it's exactly the same thing what we've been using before but now it's being relayed through multiple intermediate Hopper nodes cool so I added that one and we keep a close eye here so it was checking some last chain ID um perhaps Robbie come back so customer RPC yeah this is prefixed properly so let's see if this works wish me luck I'm gonna copy my address again I'm going to start with the same lame example of just sending myself some funds and now what's going to happen is this request here we see there's nothing popping up right at this point there was already kind of an estimate gas and stuff like that and what we actually see Happening Here is there's a whole bunch of things that you know we can't quite understand happening in my terminal here what's going on this is basically just some debug logs it's maximally verb is here that is relaying these requests through Hopper nodes so let's see if this works I'm gonna sign this transaction and it's gonna send now like again through multiple nodes it's going to send a transaction and yeah so I just made the first actually private noses chain transaction using rabbit wallet with rpch so cool very happy that the first one worked thank you guys um okay I'm 50 less nervous now so um let's go for some more interesting example I'm by the way gonna shut down my container here and I'm gonna start it again with a little bit like you can in the debug flag here you can set what you want to filter I'm just going to filter some of these very spammy commands out there so we're going to see a bit less stuff going on here okay so let's go back to Sushi how about some private sushi so um I'm gonna again swap some X die for Gnome I'm gonna swap it and we keep this open and keep a bit of an eye what what happens down there I'm gonna swap it so there's the first request going out right so what was it doing it was doing an eth get balance yeah okay well that was sad um we're gonna try that again um yeah so it didn't eat get transaction count it didn't either get balanced that went through here so so we're doing some estimate gas cool that worked we've seen updated gas price that was delivered we see this big payload of my signed transaction and yeah my signed transaction was submitted yes cool let's see if that worked yay I swapped some X die for gno nice so let's take a quick look of what happened here um we see that it received a request so this was the request going out right so this is now the end point taking my request for each get transaction receipt it sent a payload along and this payload is end-to-end encrypted for the recipient node here so that's why this doesn't make a whole lot of sense to us now and eventually we should see a response yes this is the response down here and you see the typical response of an ethical transaction receipt which is this here let's compare 0x f68 f68 indeed unsurprisingly that is the transaction hash which has actually been sent cool nice now this was using rpch using Rabbi wallet again this can work on any on any ethereum wallet on any evm chain because basically you know we are a bit opinionated here to the ethereum um ethereum RPC specs but you know we're interested in going beyond that and potentially next looking at what happens in the cosmos ecosystem and you know see what's what's going on there because privacy is something that is not just needed for ethereum cool so um this was a bit quirky right so this is like this Docker container is a bit painful you know you might not want to trust my Docker container here I totally understand that so let's look at the more normally friendly way of using privacy on ethereum so the second way you can interface rpch today is through block wallet huge shout out to our friends at block wallet who have been working with us on this very quirky first release to get this in there so really appreciate that now in Block wallet you have two options you can download it off of Chrome web store so again this is something that for you know all our you know moms and dads and you know whoever are a non-native crypto folks works I have that one already installed so you can install this block wallet rpch experimental version um if you don't trust us you know because in the end this is a crypto wallet you shouldn't trust us you can also download it from GitHub right so you can download our our Fork here of um of this rpch clone and also of block wallet and look at it yourself do your audit and then load the unpacked extension in Chrome I'm a brave fan because again privacy right so you can you can unload that here so let me show that quickly as well you see I have a bunch of wallets in here um I'm going to disable Robbie sorry Robbie and I'm gonna start the experimental version of block wallet and let's see how that one looks like so I configured it with the same deathbank account now this one is not going through my Docker container I said this is the more normally friendly way to interface rpch so I'm going to just shut down my Docker container here so what we're going to look at instead is and that's something that I find really cool in Chrome extensions you can look at the service worker that works in the background and we'll check out what's going on here with this with this block wallet extension so this keep a live request is just something that the extension does by itself and as soon as we start doing something it's going to get quite busy here so let's look at it so we see we're hitting some messages endpoint okay that looks interesting what is going on here under the hood so what happens under the hood is I you remember in this over architecture overview I told you that we have this connector inside your wallet that's this rpch SDK that connects you to the hopper Network and that talks Hopper so to say so talks to the hopper entry node and talking to the hopper entry node it sends end-to-end encrypted payload and his payload you might remember from the video that I showed all the way in the beginning I said we break payload down into indistinguishable little packets and we can see exactly that here in the browser console let's look at this request um it's a bit small let me try to make it bigger yeah so what is this just like a very brief intro into the message format that we use for encapsulating the RPC payload the first one here is just random ID you know so that the recipient knows which pieces Belong Together the third parameter just tells us how many individual packets belong to one um belong to one request and then it's just a counter right so this is the first packet and the next one is going to be the second package and then it's just like a bunch of um yeah hex encoded payload which we don't understand because again it's end-to-end encrypted and the next thing that you see is you see the recipient and this is the hopper address um of that node which forwards it the exit node to the actual ethereum um node and what we see is that this request went to uh some Hopper node that starts on 4V in the next request goes to a different one yeah so even though that was very technical I just want to like take it the take-home message here is this is way more private than a VPN or a proxy because for every single request you're switching up the notes through which you're sending it yeah so that's why rpch is already today in its first Alpha version way more private than you know existing solution that you might be used to um today yeah so that was a quick demo here actually let me do a let me also demo on this one here a quick Sushi swap yes so I know how Sushi deals with rugging the wallet and injecting a different wallet well seems to be doing well good um I'm gonna scroll down here we're gonna see this one getting probably a bit busy um I'm gonna swap again 0.01 x die for gnl yeah we see a ton of requests being fired off because now again it does all the dance right like get get the gas price get the nons and so on confirm it now again this one takes a bit longer because of this multi-hop infrastructure that we're running here um and waiting for confirmation I'm just blaming it a noses chain yeah that was not so successful huh um I'm gonna try that again so it might be every now and then that as more and more people connect to the entry nodes that these entry nodes get quite some load and then you know in this early Alpha version where we don't have a ton of entry in exit notes that there's some load issues uh with that um transaction is pending so what I'm going to do in the meantime is I'm just going to check out this account on oh it seemed that one did that one did work yeah cool so it did work out so it did send a transaction it did receive some gno and exchange so check that one out yeah all right so that was a brief demo of how to use rpch on block wallet or using Docker whatever you prefer um and with that I would hand it over to my co-founder Rick who will tell you a few things on how you can use that and what other great things you can do with rpch let me just try to find my slides back so by the way before handing it over of course there's a poab so please scan this rpch launch event Pro app and over to Rick thank you Sebastian don't worry he'll be back in 10 minutes good so thank you very much for this part uh while you scan your poab and claim it and you're going to be amongst the first 1000 developers on planet Earth who a saw the demonstration and B have the opportunity to use it by yourself what are you able to do now you're the developers of the web3 you're the Forefront of what's coming next you're deciding what the billion users are going to use the next time so that's the reason why you are able to not only try out this early Alpha version by yourself and also hey it would be lovey if you give us feedback test it and tell us where the quirks and the problems currently are we tried it on various wallets but of course the more people help us support try it out get private transactions currently for all the developers no matter if you use it via block wallet on kenosis chain or via Docker it's all for free have fun test it and enjoy the ride of a truly private transaction and be one of the first 1000 people to use it but you're also able to do and that would be truly amazing if you would send a GitHub issue to your wallet everyone here has a preferred wallet everybody loves the wallet a little bit more than the other one why don't support a true private transaction which they will build in for you in order to use it on a daily basis or even better come with us to Istanbul what we're doing here in end of April there's going to be the first ethereum conference around privacy and Hopper is going to sponsor people who are integrating rpch into various wallets they'll get the hotel and the accommodation for free and why not suggest this to your favorite wallet tell them that you're going to integrate it with your friends into the wallet and then use it on a daily basis tell your wallets what's possible how many developers do we have here today who's developing cool who is working for a wallet love you cool good so we're talking a little bit about the commercial part um then we're talking quickly where rpch comes from and then Sebastian is going to talk to you about the roadmap and what's coming up so the pricing rpch is a version which is for Enterprises we are offering all the wallets out there the opportunity to offer this one to their customers and we're not only talking about all the wallets we're also talking about D5 protocols in general sushi and you name it this means that this is our core focus on developing rpch for the future in order to make it for all the D5 protocols and projects out there easy to integrate rpch and use it but there is a side effect to it which might be interesting to one or two of you if you are able to offer your customer a premium service and you're not only offering a customer Haber better than the other wallets and there's 136 decentralized wallets out there with approximately several million users why don't you suggest your premium service to your customer for a fee you as a wallet are able to gain money because how many of the developers here are using a wallet and they're using a VPN who is using wallet transactions and uses VPN do you see these are old people who are currently paying for a freaking VPN service why don't have a dedicated service which is much better straight in your D5 protocol straight in your wallet it's much user friendly it's better Safety and Security and it's total privacy for all your users it's not only a USB for the wallets it's going to make web 3 better and this is what we said out here and of course for all our degens and developers who are here you're able to use until end of March minimum the rpch service for free try it out give us feedback we're thankful for every feedback we're giving remember this is an alpha version it's not a version which is out there since years today was the launch event where Sebastian did it live on stage and we're not focusing on the crypto end users we're focusing on Experts and Enterprises so where does rpch come from if we go a little bit back to what Hopper is Hopper is a layer 0 transport layer which is enabling 100 full stack privacy so there's all the amazing unchain privacy projects out there all the CK projects which are truly amazing but what's missing in order to have 100 full stack privacy and to truly resilient web 3 ecosystem is how do you send these data from A to B and therefore you should have something like Hopper you should have a mixed net which is hiding your metadata such as your IP address and rpch is only the first project of all these projects which might come why rpch if we think of what's most important in the web3 ecosystem what is like your shoes when you go on the street or when you take an aircraft when you go to the next continent the most important thing about the web 3 ecosystem are wallets no matter if you buy or sell a token if you swap something if you're voting for something if you delegate rights no matter what you do on the blockchain you need a wallet the wallet is the most important infrastructure part of the anterobat 3 ecosystem in order to do anything on the chain now we believe if we are able to make all these transactions truly safe and private that only you decide who are you disclosing your transactions and not then we're walking into a direction where the web 3 just became a lot more resilient and this is one of the core values of the battery ecosystem so rpch is helping all the wallets to make their transaction private and therefore hopefully grow the web 3 ecosystem into a stable future we had this idea in September than we were drafting um then we had the first ux web 3 hackathon our metamask calls it with Francesco from consensus in Zurich where we had amazing designers in a hackathon in order to think about how could we integrate rpch into metamask will the users pay will the wallet pay will there be a different system will it be a pay per transaction model so we first started with an outline together with metamask in order to think about how could we use the service after we had the first drafts done I guess some are not as nice as our marketing material we of course went to Defcon and we participated as sponsors in the small hackathon infinite hackathon which was happening during Defcon in Bogota and you can see that Steve was working day and night in order to get this stuff ready in order to start working on the first idea with block wallet frame and tally together in order to set at rpch here you can see the three guys which have been coding for us as a team together and as every lucky story usually starts yes they did a fantastic job that's the reason why we offered them jobs in the rpch team so these three guys Diego come here and Luis are now working together with Steve and now we have Martin's another devops who's worked together on that project in order to make bring rpch from the Alpha version to the better version and to everybody out there and yeah this is how usual business now looks like they've been working really day and night in the last two weekends consecutively in a row in order to make this happen it's really amazing to see that the team is so motivated so thank you very much for the entire RPC age team for making this happen and this is where it ends at the end of the day we're still Hopper we're still going in the direction of growing and making the web 3 ecosystem more resilient but what it helps for Hopper is we are bringing sustainable protocol Revenue to Hopper and this is important because at the end of the day we need to pay the rent we need to pay the people they deserve their money because they're doing a great job we're paying insurances we need to pay the stuff but in order to bring protocol Revenue to Hopper rpch is the first product and um what do you think if you look on coin gecko you have a little bit more than 12 000 projects out there who are listed how many of these projects already have protocol Revenue 10 100 a thousand two thousand five thousand six thousand guess fifteen twenty three come on 12 000. okay good so here is a little projection of course ethereum is the number one and then you have various chains and uh yeah so our projection is that we're going to be amongst the top 100 who will deliver protocol Revenue by mid this year and yes currently there is 94 projects out of 12 000 who do have sustainable monthly Revenue and this is the moment where I hand over to my beloved founder Sebastian in order to tell you a little bit more about the roadmap thank you Rick so yeah protocol revenues is a big thing because if it's not protocol Revenue it's going to be revenue for JP Morgan so I'd be happier if that goes to decentralized networks now for the ones who have claimed their uh their pull up um okay I don't know okay I'll be I'll try to do this one-handed um the last thing I wanted to show you is to just walk briefly through the roadmap through what's coming up for rpch so we've seen that this first Alpha version is you know in a quirky way available to the more technically capable folks like all of you here in the room our Normie friends will probably have a bit of hard time this far unless they're happy to use block wallet on gnosis chain that is so um the roadmap of what's coming next is let's first start with what we have already today right so what are the components that we have this far we have the SDK that's integrated into block wallet and in a Docker container we have this connector that I showed we have entry and exit nodes and these entry and exit nodes this far are exclusively operated by us why because I didn't want to crush it to this to crash even worse than it did this far so um that's the next step in the beta version we will have third party node operators which will be entry and exit nodes in this network and the other thing is we have a centralized funding service so as I mentioned behind the scenes the hopper network is incentivized but these incentives right now go through centralized funding platform so in the beta version of the next release please don't ask me for timelines we will have anybody of you who wants to run a hopper node can be an entry in an exit node and you know earn returns for providing services to wallet users like all of us we will have what we call an honesty score so you might have seen somewhere in my debug logs that you know every now and then there were some um we look for that one there were some failed requests right so for example from this node six of the packets were delivered successfully like there were zero where they try to cheat that's good but two were just dropped and package drop is something that happens in decentralized networks way more frequently so that's why we have a scoring system where the client itself without relying on a centralized scoring service can itself decide on uh yeah what's what's actually correct and finally um in the next version we will have multi-hop routes so in this current route you have only an entry and an exit node which directly communicate with one another like for the next releases we will add multiple intermediate hops again the reason that we don't do that this far is because we want to launch this in a somewhat useful fashion already in this very limited Alpha version of rpch we are as we've seen way more private than RPC providers today including your VPN but yeah it's only going to get way more private from where we are here and ultimately the long-term goal is of course to make this trustless we should not rely on centralized platforms like the funding service that we have in place or the discovery platform this is information that your wallet has to be able to establish itself it's a long road to get there we have a ton of plans on light client verification on ensuring you know that the underlying system is secure and yeah lots of work left to make the web 3 private for all of us one last project that I wanted to point out that we worked at at Hopper is also on the consensus layer also unfortunately the ethereum consensus layer is not very private so we worked in a project to analyze and point out an attack Vector um that allows you to de-anonymize ethereum validators today so one next goal that I guess I can Alpha leak for Hopper is we want to not just make ethereum while it's more private we also want to make the consensus layer more private just as an outlook for where we where we headed here I want to thank you so much for coming here again I'm tremendously proud to show off the work that our entire team and our community has been working on for the past three years and if there's any questions Rick and me are happy to take them after the session over here thank you so much thank you Denver [Applause] [Music] thank you thank you [Music] [Music] thank you thank you foreign [Music]