 on to our spotlights. First, Isaac, Kusunan here. Happy for anyone else to also jump in, but I just think we should all take a second, unmute and just do a big round of applause for everyone who is involved in the FBM Mainnet launch. This technically happened after our last end result ham, so please unmute and let's all celebrate this awesome milestone. Thank you all so much. This is big and super, super exciting to see all of the people who are now building on top of it. Lots of shiny logos that are now participating and lots of felt coin that's getting deployed, lots of accounts that are getting created, lots of new applications that are now possible. So it's big. Thank you all for being a part of it. Over to Patrick for the randomness. Yes, we ran the second edition of our Randomness Summit in Tokyo, the first being online only in 2020. Our goal was to interact with people building in the same space as us and get to know some other people working on cool random things. We had 45 attendees from a variety of institutions, notably lots of different ministry of defences, but I confirmed they weren't able to bribe us to break DRAN, so it's fine. Some of the cool follow ups that might be interesting are NIST are actually standardizing randomness beacons and threshold cryptography. So we're hoping to make DRAN other than the reference implementation, the first compliant implementation with the NIST standard, which would be very cool. We're planning to host another Randomness Summit sometime in the future, this time potentially alongside another slightly more hackery event so we can encourage more people to actually build on top of DRAN. All the talks can be found on YouTube and if you're short on time, which everyone seems to be, Renardo Davide from the University of Copenhagen give a wonderful talk summarizing everything you can imagine about randomness, fair faddle, secret sharing, VRS, PDFs, quantum randomness, randomness from speed of light via satellites, it's all there. So check it out, there's a blog post coming soon and also I forgot in the DRAN update to say the most important thing, we've got a new project lead, Eric, because I've seen this on the call, so welcome Eric, he's going to do lots of biz dev things and we've already taken DRAN to space, so hopefully Eric will be able to take DRAN to the moon and beyond. Thank you very much. Eric, over to our IPDX update. Hi, I'm excited to introduce IPDX's innovative solution to GitHub Actions Monitoring, as you know, GitHub currently lacks a comprehensive CI monitoring product, which prompted us to create our own. Our solution is quite elegant, we monitor weaponry events, store the raw data in a post-risk field database and use Graphana to generate insightful visualizations. Let's dive into a real-life example. Our main dashboard provides in-depth insights into GitHub Action workflows and jobs. By default, it displays organization-level information and groups results by repository. Users can easily select a specific time series or even reconfigure the entire dashboard to focus on a specific repository. With the flexibility to choose time ranges, granularity and grouping precision, our tool empowers users to gain unprecedented insights. Thanks to our monitoring solution, you can see that a week ago, LiDAR brilliantly optimized the Docker publish workflow in Cuba, reducing its runtime by an impressive 90% by eliminating unnecessary QM virtualization. Our GitHub Actions Monitoring solution offers comprehensive insights and customization options. It gives our tool person a dream, true superpowers. If you're interested in checking it out, let us know. Awesome. Nice update. Testudo. Hello. Hi. This is Matteo from CryptoNet. And what I'm going to bring on the spotlight in my list in a minute is the fact that Testudo, our new snar scheme, went open source. There's a repo there, and there is a blog post which I invite you to check out. It's tiny in the bottom left over here, but I also share in chat. And our design is there, and you can find lots of more details than what I'm going to tell you, but you don't know what Testudo is. In one sentence, it's a very fast, this is dark with a very fast prover, very short proofs, and lots of nice features. But the main nice feature, like you mentioned, is it's universal and short. And what does it mean for Farcon? That means that you got easy and fast applicability whenever you need it. You can do one single universal and easy setup, and it can give you fast purse while proving acceleration techniques are getting better and better. At some point, some design is going to matter. We're going to hit the wall with that. Testudo would be ready to plug in when we need that. There's lots of other things I could, I'd like to brag about, but I'd like to say, so what's happening next? This was the crowning of eight months of work. Kryptonite is not actively working on this, but we are looking for collaborators, external collaborators to improve on our implementations. And there's a paper coming up very soon. Thanks. Awesome. Alfonso, IPC. Thank you. So this is going to be really quick. I just want to call everyone to test the subnet. In our repo, in the APC agents, you already have some getting started guide on how to run locally or on SpaceNet, your own subnet. It's true that there's no, until the 20th, we won't release the cross-net message support. So in the end, you will be able to run different subnets, but not communicate between them. But it would be great if we can start getting some folks to test it and to please break it. We want to see what is wrong before we we release it to the public. So there are some doubts. There's a getting started guide in the IPC agent, consist of shipyard slash IPC agent repo. But in any case, probably we can share the links here and drop us a message in the IPC dev channel in Slack, and we can guide you through the first steps. The UX is a bit rough. So any feedback is more than welcome. We want to improve that. The first thing that we want to improve is UX. Like the tech is there, but the UX is a bit rough. Thank you. Yeah. So it turns out guy is sick. So I'm going to have to do it for him. Current situation, the Falcoin is actually vulnerable to a 20% attack, and you intuitively wouldn't expect it to be so because you only have one winning tickets out of five in expectation. But as it turns out, there are circumstances in which you can, if you can send different blocks, so with a single winning ticket, you can generate different blocks. If you send, if you send, if you generate and send a different block to each of, to each validator, then you can actually confuse people into preventing convergence and not building a chain while you keep building your private chain in parallel. So that is the issue that we're addressing. The solution is consistent broadcast, which just, which just means that you cannot send equivocated blocks, broadcast or send equivocated blocks to the network. And so that raises the attack bar to above 40%. And it brings you to the actual expected situation above. So what does this cost us? And the good news is that it does not cost us pretty much anything. The only thing that we need to do is to keep a cache of the blocks we receive and a buffer and wait two to three extra seconds before actually considering a block valid to start building on it. That also means that no hard fork is required. This is actually an entire client-based change that people can make. And that brings me to, well, next week to the actual announcement, which is the fact that this is already merged into Lotus Master and is on its way to production. There is a swipe bug that we still need to, to figure out, but it's done. And so Filecoin is safer. Thank you. Awesome. Over to Ian for Problab. Hi, I'm Ian at Problab. I'm going to give you this quick, so I want to see Hannah can hear me okay. Problab's mission is to measure the performance of Web3 protocols and evaluate them and propose improvements in their design. And actually that end, we run a lot of systems that collect data continuously. We monitor things like we call the IPFS network and the Filecoin DHTs. We monitor website performance. We analyze DHT access patterns and the performance. We have quite a lot of data. We kind of want to surface it in a better way, but we also want to surface it in a way that gives context to that data. So what we have put together is something just started. It's literally only about two or three weeks old. It's Problab.io. It's a place for us to publish the data we're working on and collecting. Give some context around that in terms of like methodology used to collect it, what it means, how to interpret it, what the limitations are in terms of how that should be viewed. We're putting in data from other systems. Some of the stuff we've got in Grafana and Peretius from other systems. We want your data. If you've got data that you think should be analyzed alongside the stuff we're doing with Problab, then come talk to us. What we got the idea is to bring this all together in a hub and around that, we're going to have all the different things we've got. We're already doing weekly reports and we've got the KPIs and the stats.IBFS network, which is an overarching place, a single point of access for getting to see this data. Come along, have a look. I'm trying to keep it simple, but it's going to expand over time. It's under a lot of work, work in progress kind of stuff. Thanks, everyone.