 So hello everyone, my name is Brenda, I'm a product manager on the bedrock team. And so shout out to my fellow bedrockers here, Lauren, DVD and Yvonne. So today I'm going to share a bit about Lassie, which is a new retrieval client that some folks on the team, Hannah, Rod and Kyle started building out back in January. So it's been a couple of months. Yeah, really excited to share kind of the progress that's been made and how it works and how you can talk to other folks in the ecosystem about it. So let's get started. So I don't know how you guys kind of feel when you talk about Flock on an IPFS, but I think sometimes when I share about it to whether it's clients or to just my friends or my family, you know, it's kind of technically confusing for them. And so for them, you know, maybe you're a client or maybe you're like a consumer and you're like, hey, you know, Falkland IPFS are pretty cool. But how do I actually know where my data is? And if I have stored on storage provider on Falkland, how do I know which one has it? Do I have to like track all these things down and remember it myself? So what if I'm a client and I don't actually know where my data is or which storage provider has it? And this is where we're introducing Lassie, which is a retrieval client that will actually find and fetch your CIDs over the best protocols available on both IPFS and Falkland. So just to show a little bit more about how it works with this nifty diagram. Shout out to Lauren. So basically on the client side, you have the CLI tool Lassie. And essentially how it works right now is that you give it a CID. In this case, there is this example, CID here, B-A-F-Y, you know, dot, dot, dot, dot. You just ask Lassie, hey, I want to fetch this CID. Lassie will actually go and query the IP and I, the interplanetary network indexer that Yvonne shared a bit about earlier and how are they serving it? So IP and I will come back with this group of providers, both IPFS and Falkland providers and essentially like which providers they are and what protocols they're serving it over. And so Lassie will actually go and ask these different providers, hey, like, please provide me this CID. And it will actually race these different providers and whoever returns the fastest. That's where they get your data from. So there's a couple of different Lassie modes that you can use it in. The first one being the most straightforward, which is a CLI. You basically download Lassie and you basically run this space. Very simple command, Lassie fetch, and then you insert your CID and it will return you your CID in car file format. So that's a CLI. You can also use the Go Client Library, which can be integrated directly into your Go app. There's also an HTTP daemon for integration to non-Go apps. And we'll talk a little bit more about this later. Some pretty neat Lassie features. It's very lightweight, but essentially the big one, it retrieves seamlessly from both Falkland and IPFS for you. What it does, it will find the content for you, or you can also specify where you want to get the content. If you know where your provider is and how to reach it. It also basically queries all these providers in parallel and returns the data to you from the passive source, as I explained earlier. And then optionally, you can see detailed progress information. So there's a snippet here that kind of shows, hey, this step by step of what's happening, you're fetching the CID, it queries the indexer for the CID. Here's the candidates that I found from the indexer and it's querying all of them and it kind of lists the progress of what's happening. So you can see where your request is. So Lassie also fetches and guards your data. So basically all data that Lassie returns to you is in car format, so it's verified data. So you know that when you receive it, it's exactly what you asked for. So basically a data provider cannot provide you with false data or give you something that is actually completely different from what you get asked for from your CID. And then basically the output that Lassie has gives you everything you need to verify the content as well. So Lassie, cute, but also it fetches and it guards for you. So really quickly, I wanted to share where Lassie is being used today in addition to just individual end users such as myself or other folks working at this company using Lassie and CLI, but actually Saturn at the centralized CDN, which many of you guys probably have heard about, essentially it cached misses to popcorn and IPFS and it's doing this via Lassie. So if you go to Saturn and you ask for a particular CID and maybe the Saturn doesn't, Saturn cache nodes don't have this, it'll actually go and use Lassie and ask for this content from IPFS and popcorn. And so it's being used today, which is really neat. And you can see just some basic stats that I pulled earlier today, retrievals both to popcorn and IPFS are flowing. So if anyone kind of claims to you like, hey, like retrievals are broken or retrievals aren't working, they actually are working. And so you can see here that a portion of IPFS IO traffic right now is being sent to both storage routers and IPFS nodes. And basically, yeah, over like 113 million retrievals, successful retrievals on both popcorn and IPFS. This is just over a weekly seven day period. And out of that, we know for sure there's at least 147,000 successful retrievals from over 63 unique storage routers. And yeah, possibly more because the way that we're separating this right now is purely based on GraphSync, which is a retrieval protocol versus BitSwap. And actually storage routers are also serving retrievals over BitSwap. So it could be more than this number, but it's hard to just differentiate that right in our metrics. So yeah, really exciting. This is just from like one project, the Saturn Vario project that's kind of in ramping on test mode right now. So just want to encourage everyone to try out Lassie and give us feedback. Have some links in the stack where you can have a base. You can go see basic Lassie tutorial. We have a GitHub that has more detailed information as well as HTTP stack. And if you have any questions, find us on Retrieval Help. And I did want to show you how easy it is to use. So for the purpose of this demo, very simple. I just downloaded like Lassie and I am running Lassie Fetch. I provide this CID. And essentially what I'm doing here is I also downloaded the card tooling and FFMPEG tooling. I'm basically extracting the car file. And then I'm going to play it over FF Play. And this video is basically a video that one of our teammates, Rod, had uploaded to Web through storage. And so let's see what happens. Oh, I thought about this thing. But here's a video playing. Very simple and easy to use. So yeah, let me know if you try it out. Find us on Retrieval Help if you have any questions. And that's it for me.