 Yeah, I'm gonna give an update on whispers. So a quick reminder. What is whisper? It's a peer-to-peer messaging system with strong metadata privacy guarantee You cannot like no one can read the content of your message and they cannot know who you're sending it to either So because of the way it's implemented You need a lot of bandwidth. You cannot really do video chat things like that The best use case is really to Distributes a message to several recipients and So like what would be a necessary or possible in in distributed exchanges? But you have some company like less like like status, of course who have who have implemented that as a messaging system So so that's that's really nice As a quick reminder of how it works imagine that those diamonds represent nodes on the network and Node on the far left wants to send a message to notes on the on the right. So what they do they just forward Oh, yeah, I forgot to say the blue lines are the network links so the the node forwards the message to their to its neighbors and Those neighbors in turn forward The message to to their neighbors and you can already see that the one at the bottom already received two copies of the message and the other thing is that One of the recipients got the message but to not be identified as the recipient They will still keep forwarding the message to their neighbors and you can see that one of the nodes already received three copies And that is a pretty simple network So over the last year we released version 6 I built a test net and I implemented a leapy-to-pea version of whisper Right so the leapy-to-pea version Last year in Cancun we we had to talk with parity with leapy-to-pea people and we agreed To try to use whisper as a test bed for leapy-to-pea simply because whisper is fairly independent from the rest of the of the network So so that was a nice experiment and I made a couple a couple Articulate a couple PRs one of them one of those proof-of-concept of work, so it's available at this address I have a test net of leapy-to-pea Whisperer clients talking to each other the problem is that Leapy-to-pea at least the go implementation is not exactly modular yet So we have to bring in 400 files. So that's a bit of a problem. So that's why it's not it's not available yet so when it comes to the Development that is going to take place this year first status is Starting a big documentation effort. So I'm joining in so kudos to them for for helping with that There's drive because parity has a slightly different Version of the protocol is not compatible. So I'm going to spend some time Trying to to make them talk offer a PR. Hopefully I'll get a t-shirt in in response and The other the other two things so there is a test net There are examples on how to use it, but people keep asking questions. So there's there's a need to to improve the communication on that So these are the easier things now. I want to delve a little bit more into the Leapy-to-pea changes. So this is a very contrived examples or representation of the of the current state with def p2p So on top in the red boxes, you got the protocols You have you have ETH you have whisper and then just below it. You have the library Let's call it the library so the server object the protocol object and then you have the fp2p proper and The fp2p does all the heavy lifting it does the discovery does all the connection connection things and And really down at the bottom you got the transport layer which is called our LPX It's got some some security issues So that's what's initially driving the potential potential switch to to the p2p Now the PR that I that is available the one I described earlier It's basically just putting another server right next to the def p2p server and Like you have something to almost independent entities Except whisper kind of still relies on the library layer. So it's a bit of a of a hack But this is not what we want to do for several reasons Well, one of them is that we know a lot of things about the def p2p Felix has invested a lot of time in in in that for example We can't just chuck everything and move to the next to something new that we don't really understand The other the other issue is that leapy-to-pea itself. I mean that that's that's a big change That's really an engineering problem here Leapy-to-pea has we started discussion with them recently it's got a lot of a Lot of modules that we don't need a lot of Redundant things. So I'm really positive really happy really enthusiastic about the work that we can do together But yeah, the goal would be to end up with this So we just keep def p2p for now to benefit from all the security We have so far and we just slowly phase out Rlpx and we use the leap the transport layer of flip p2p and over time We slowly replace components of the fp2p with leapy-to-pea if that makes sense And then they are on the horizon. They are more long-term improvements So one of them is the proof of work So whisper when you send a message you calculate the proof of work on on this message This is to prevent spamming Because if you remember when you send one message it gets Duplicated and sent over several times. So you need to make sure that you don't abuse the system the problem was that is that status is complaining that the proof of work is Draining the battery like calculation is draining the batteries of mobile phones So I want to spend some time Trying to find alternative proof of work algorithms that will consume less power and Daniel from from swarm Has suggested to use proof of burn, which is great for for preventing spam because it's your own money However, it's connected to your Ethereum account, which means that when it comes to privacy You are pretty much identified. So so yeah, that needs to be to be Improved and then we want I want to do some some simulations For try to not for forward the message to every every single node try to have a bit more Feedback between the nodes to not forward so as once again a contrived example if you remember this slide At the point where the node received two messages if you see that the same message Keeps going keeps coming from two different peers. Well, you simply remove Remove one of the peers. So once again, this is a very contrived example. We need to to make sure that You know privacy is a metadata privacy privacy is is ensured if we do that, but I think it's it's a good. It's a good Experiment to have in the coming year and the last Improvement I want to work on it's wasm. So I'm sure most of you have heard of wasm But just in case you've been living under a rock. So wasm lets you Take whatever language you have a program written in whatever language Compile it to a blob and that blob will run in the virtual machine in your browser or on node And wasm has a lot of nice properties because so far What we use is the remote procedure call call. So if you have a D app, it's running in your browser It connects to one of the nodes ask the node to create a private key for you to encrypt your message and to forward it Which means you you need to to trust the node and thanks to wasm now you all all you need to do is trust your browser Okay, I thought I thought people would think it's funny But ideally if you can trust your browser then it's it's much more secure Because Yeah, it's it's much more secure, but or if you run it on node on your on your machine, you don't have to trust anybody the only issue with with wasm at this stage is that The go for example the go compiler to wasm is pretty new a lot of a lot of the dependencies don't compile So there's some need to wait for the For the ecosystem to mature. So we're a bit Yeah, we're waiting a bit for that to happen So I'll end up with a roadmap. So the easy stuff first Documentation parity compatibility then around the middle of next year I hope to be able to publish some results about my networking experiments Maybe the collaboration with with lip to people will be fruitful and we can we can provide the some Some lip to be unable enable geth and then next year early next year wasm and the proof-of-work experiments So that was pretty much it. If you have plenty of questions, you can hit me on any of those platforms Or you can catch me and hit me for real and Yes, that's that was and that was all for me