 Okay. So I want to like tell a super quick story about the recent announcements that have been done to IP&I. That is a major improvement for the user privacy story. So let's first like recap what IP&I is. So IP&I stands for Interplanetary Network Indexer. So what it's going to be used for. So it can be used for finding content on IPFS and Filecoin networks. So it's used in the batch of services already in a bunch of projects that have all go through in a minute. Basically the main purpose of IP&I is you give me content identifier. I tell you where content behind that identifier can be found at. So and like before going through the recent improvements. So let me just quickly recap how IP&I works. So it can be explained in four simple steps. So first step is we do have like a bunch of Filecoin and IPFS nodes that are connected to IP&I. So and they whenever they have a new data, they post announcements. So that's step number one. So whenever new data appears on the IPFS of our nodes, they post announcements to the, via the lippy to be pop sub topic. So IP&I is continuously listening for those announcements and whenever it picks up one, it would reach out to the to that node directly to the storage provider and would stage all the all the recent updates from it. So the unit of update is what we call it advertisement. So basically an advertisement is a unit of is a structure that contains a list of content identifiers in it. So by announcing advertisements, you tell the IP&I does. Okay, I do have these CEDs available at my node. So if you and I would fetch it, index it, and that's it. So then after the content is indexed, so per user would can use it to look up some data. So when user sense user would send content identifier request to request with content identifier to IP&I and IP&I would return it. Hopefully a list of providers where the data can fetch from and then the user would would go or would reach out to these providers separately and download the receive the data and download the cat picture. So why IP&I is awesome. So it's awesome because it has two properties. It's open protocol so anyone can can run an IP&I instance anyone can participate in it. However, it can be run as a centralized service and running as a centralized service provides some advantages. Specifically, the advantage uses can significantly helps reduce time to first bite for in the in the general content retrieval story. So one can find content on IPFS and file coin networks much much much much quicker. So what the problems we tackled with the with the privacy upgrade. There are two issues with the with record how IP&I is used right now. So let's start with the with the number one. So if there is a man in the middle that observes user to IP&I traffic so they can see in open what content identifies the user is after and they can just spy on the lookup responses to the to the user and they can just reach out to the same storage providers and download the same data and by doing that they can spy on what data is user after. So the second attack vector is the rogue IP&I deployment itself. So if IP&I deployment is malicious, someone can just it can just like spy on the request that receives and also can see what what data the users the users are after. So and this is obviously not good. So the way we tackled it is with recent upgrades of privacy story which is called double hashing. So what is double hashing? So in a simple words without going to any details. So now instead of like providing looking up the raw data in IP&I in open so instead of like using raw content content identifier the user would use cash over there this content identifier and in response IP&I would send a provider records which is encrypted with the original value of the content identifier. So what this means that in order to make sense of such communication of someone is spying on the users. One needs to know the original original content identifier but the content identifier is gets never revealed in the in the first place during such communication rounds. So that enables much better privacy story for the for our users. So double hashing is already running throughout so we're running a big IP&I deployment which is called seed.contact and I'm going to show you right now how the encrypted responses look like. So the one I have open here is the regular response. So if I can send a request to seed.contact if you see in my browser and it would resolve me a bunch of the records where the content behind that content identifier can be found as so it's essentially a list of providers with their repeat of the identities their addresses so I can just go through through this list established connection download the data. So if I do encrypted look up so instead of returning data in open it returns obfuscated gets obfuscated data that I cannot make any sense of without knowing the original content identifier. So if I don't know to the first place then I cannot decrypt the decrypt the provider records and I cannot spy on the on others communications. Next steps for us is to be initial out to seed.contact so currently we cover about 80% of the of the lookup request and this number is growing so we need to update the existing clients so the IP&I is used by a bunch of different projects such as last seed which is the file current retrieval clients such as Kubo which is the most popular IPFS implementation so it's used by this is last CDN like Soutern it's used yeah it's a lot of places so basically we need to update the existing clients and existing integrations so that they use double hashing by default so they don't send regular lookups anymore so we need to work on the we so-called write a privacy upgrade so write a privacy would allow publishers to advertise encrypted data into IP&I right now this data is still in open so we're protecting on the user privacy of the minors and yeah that would hopefully make IP&I even more awesome and even more usable so and if you have any questions any suggestions or you want to use IP&I or like you want to ask something please reach out to the IP&I Slack channel on the file going slack yeah and that's it from me so thank you a lot for listening