 over two hour spotlights, starting with the shark upgrade. Jennifer. I have a shark to release. If you are wondering why we called name the Nahuca 2017 Upgrade Culture, a core contributor of this Upgrade and Ground Serial decided to pop in one of the one who was super casual with me saying that, hey, I've been surfing with some sharks in my vacation time. And I'm like, oh, great, cool, those two bad. But anyhow, there's a lot of amazing flips will be included in the Nahuca 2017 Upgrade. So we are enabling beneficiary address for storage providers, which is one way towards a better landing market for SPS. With FBM, it will be even better, I believe. Sextree Kuba, we are resolve a significant weakening of following Polar Security guarantee concern in this Upgrade as well. We are focusing on enabling programmable storage market towards it FBM launch of the 41 and the 45 are for that special call out to the decoupling for Queen Plus from Marketplace. This is our star, our blue heart of this Upgrade. So we are making data cap and the Q&A brings to the sector to start kind of a store stuff to actually be associated with the data itself instead of the deal. So now you can base the client or anyone who cares about the data that's stored on Valkoin can have the term on the data cap and extend that term if they want. So that storage provider will store that data as long as possible on the Valkoin network. It's a huge step towards user program, both storage market and yes, we're introducing our first fungible token contract. It's a data cap actor, it's gonna be one of the beauty actor that will be shipped in this release and link the fungible token standard and the token contract library in the slide. If you are interested in, it's very early stage so we're gonna iterate over the time but if you have experience on that please participate in the conversation. I don't want to forget about the 44 which is thanks to Ayush, we are enabling any metadata authentication for user defect actor. We are trying to set a good foundation for a lot of use case that can be deployed with FBVM before the next network upgrade. So that's our goal. As mentioned, FIP36 currently is being pulled out right now. If the community, the ecosystem decide if it is accepted because of the time sensitivity we have, the core that have agreed that if you were accepted, we will include that in the network in the factory upgrade and because it's extending the sector max lifetime we also want to make sure our power lifetime security is secured. So we are considering finalize of 47 as well in this upgrade. Rough timeline we're still targeting mid-October for the calibration upgrade and early mid-November for the main upgrade. Thanks to San Juan, Enos, Cuba, a huge job for all the development also shamelessly parking where do you unload this on morning and friends summit. I feel this one on the run with the second the whole team will be there if you have any question about the shark. Last time we will be there. Awesome. Over to magic for ceiling as a service. So yeah, finally after a whole bunch of discussions and a lot of implementation work, we've landed basically all the code that's necessary on the Lotus site to support seeing services. This is basically just a few new APIs. What they allow Lotus to do is to import sectors which have been sealed externally and also they may have been only partially sealed. So miners can pay some service to do pre-commit one and two for them. And then they can download those sectors and finish the ceiling themselves. This basically allows miners to optimize how they use hardware. This allows miners to pay other services to the ceiling for them. Maybe in the future, we can extend it so that you can have service providers run all the compute needed to run a Falcon node and you would only store data locally. This could let us deliver the mine Falcon web and us on your desk use case that is possible. It's just not right now. So we can do it. Yeah, the other other use cases that can emerge from this work is seeing compute marketplaces which could morph into more general marketplaces later. This is also something that back allow could provide in the future and integrate with this. So yeah, there's a lot of very exciting features emerging from this seemingly simple Lotus feature. And yeah, a lot of these things that are not possible with this is thanks to the design discussions that were had for quite some time. So yeah, if you want to check out how it was designed then maybe they'll have more input on it. Check out that good discussion can hang out in the fail, sink and the service sectional. Yeah, that's that's in the service. Awesome. I know people have for a long time wanted to be able to be participants in the Filecoin economy with devices with less GPU capacity. So that's super exciting and also super exciting for all of those poor proof of work miners who now no longer have a home in Ethereum who can maybe come and bring their services here without also having to invest in a lot of storage hardware. They can partner with existing SPs and just provide their like GPU ceiling services to help scale our community here, which is awesome. And so thank you for working on this magic and excited to see it come to fruition. Passing over to Steve, speaking of the merge. Yeah, you bet. So this is not necessarily new announcement versus last week, but it's worth repeating, right? LibP2P is securing Ethereum's main net, huge milestone here. And one of the things I love about this is just that it is very much a long term effort, right? So there are talks back from DevCon 2 where David and Juan were already starting to beat this drum and talk about how they could integrate. We had great notes and ideas being brainstormed, getting a, we had a, you know, connected with Parity to do a rest implementation of LibP2P in 2017, 2019. We got into the Ethereum networking specification where there was a whole bunch of community management work and, you know, implementation management that had to go on that Raul and others were helping lead. And there was key new functionality that had to be added like Gossips, but which happened in 2020. So there's been a long journey. I love that we were planting seeds six plus years ago that are now really bearing fruit today. So major, major props to folks in the past like Raul, David and Juan. And also the current team, you know, there's been a lot of work going on behind the scenes to make sure LibP2P is secure and ready for this, you know, the big moment of the merge and it's been successful. And so now we see, you know, multiple LibP2P implementations helping secure a network of over 400,000 validators. So great job to the team. And yeah, excited for more good times ahead. Awesome. Over to you. I'm definitely last month at least, FEM. FEM, so what's happening? There's a ton of news across the board. I've structured them in kind of like the working groups that we have in the FEM team. First, a bunch of updates from engineering. We have, others have announced previously, we have a new test net that is live, that is operated by factory solutions. This is Patrick. It is a test net that is updated roughly every week because we are conducting incremental delivery of the roadmap of FEM M2.1 for the Selenium release. So this is the release that went out two weeks ago. We had 63 smart contracts deployed on that network with this new release that went out last week, which is named Copper. We had 23 smart contracts deployed on the network and we're expecting to put out a new release next week. Hopefully everything will go well for this one because it's a huge one, because it's going to add full JSON-RPC support, Ethereum JSON-RPC support to Lotus, which is then going to allow unlocking downstream, a lot of downstream testing effort and integration effort with native Ethereum tools like MetaMask, Remix, Foundry, because all of these actually access functionality in the Ethereum or EVM compatible network through that JSON-RPC API. And also we're pushing for feature completeness of the EVM runtime, so which we're codenaming FEBIM by adding support for more op-codes that are still missing from that implementation that are currently panicking. Now, there are several architectural changes that are going into the Filecoin network to actually support all of the changes that are kind of like all of the structural changes that are needed in the model to support things like addressing native addressing in the Ethereum network in EVM contracts, and also to support things like native Ethereum transactions that are emitted and issued from wallets like MetaMask, Wallet Connect, and so on. We want to support those out of the box. So there are two key changes that are going into that we're proposing for inclusion in FEM 2.1, that's the F4 address class, which Jennifer already mentioned a little bit about. This is a hierarchical, delegated address class, so basically there will be address managers on chain where the first one is going to be in the Ethereum address manager, and this is going to be able to provide different addressing identities for actors on chain, such that because normally just to back up a little, the FEM is built as a polyglot runtime that is able to accommodate runtimes from other chains to make that integration of contracts from those chains easier and simple. And in many cases, those runtimes actually come with their implicit assumptions about addressing, this is usually the case. So having a way that we can in the platform protocol work with those addressing assumptions at a native level is pretty important. This is where F4 comes from. A contract abstraction allows us to validate Ethereum native transactions in the protocol within user space without actually having to modify the protocol. That's why that is important. And then finally, we're also starting the work stream on the EVM storage footprint optimization in partnership with Consensus Lab with Akhosh. Now on the developer experience front, we had a ton of success with the early builders F1 program which focused all around the native tooling. There's a link in there with a blog post on everything that they built. We're graduating the F0 cohort in the next weeks and we're starting a new cohort. This is called F1 and this one is going to focus all around EVM and Febham use cases. We received 55 applications. We have selected 31 of those and we've divided the participants into two groups. The core group, which will get very close apart from the FEM team and the peer builders who will be kind of like community oriented. Now we're also incubating the developer forums and the docs. That's a provisional URL that is going to be moving to a file.com.io domain soon. Hopefully Matt also published a Twitch stream deploying contracts, demoing how to deploy contracts on wannabe together with Jim Pick. Jim Pick is also on fire. He's putting out a ton of walkthroughs on observable HQ with like every release that we put out there. He's the first one to just grab what is on top of it, just experiment with it. It's just awesome to have that energy in early builders. On the product front, we're pushing for deciding what's going to be a new network in file, it's a new fine coin network, which is designed to be a canary network as a spin off economy from Mainnet. So this is a network that is going to move from Mainnet and it's going to basically allow users to experiment with early technology such as the FEM before it's actually released on Mainnet by using real value. We're planning to launch Build-A-Net if everything goes well by November the 8th. So this will be just after the Lisbon and all the events in Lisbon, Lab Week and so on. So there will be, you'll hear a lot of drumrolls and a lot of presentations around this as well to pave the way. Addy is also conducting a ton of interviews across the org to collect input around use cases that people want to build immediately on FEM. Remember the goal and the success of FEM, it's not just shipping the technology but actually building, enabling the building of the use cases that people are just, have been waiting and dying to build for a long time. So we want to make sure that we're able to provide, that we understand what those use cases are, that we provide guidance to these teams. It's likely that we're going to be putting out solution blueprints going forward for some of these use cases to kind of like provide like guidance on how to build things like for example, computer data networks or how to build L2s or how to build stuff like perpetual storage and things like that that people really care about. Now, if you have a use case and Addy hasn't reached out to you yet, make sure that you reach out to Addy so that he gets a chance to put it on the radar for us. This is also very important because a key epic and FEM 2.1 is actually re-engineering the built-in API, the public APIs of built-in actors so that they're able to cater for all those use cases that people want to build. On the audits front, we're booking two external auditors for Febham, preparing security audits. We're planning to involve the PL network at large to come and vet the code base. So there's going to be some cons that go out there. We're also assembling an internal red team. So if you want to participate in reviewing and auditing the FEM code base as it gets closer to being prepared for production, then reach out to Dragon here and he'll add you to the list of potential auditors. We're also going to be inviting the research, the security research community at large to participate in reviewing. So we're scouting if you have really talented security researchers that are potentially working in academia or other places or maybe like more amateur or whatever that are not really going to conduct a formal audit but there could be acting as white hackers trying to break a test net that make sure to speak to Dragon as well so that we record them in our candidates list and we reach out to them. And as for upcoming launch plans, the current projection for Mainnet is February the 8th. If everything goes to plan, build a net. If everything goes to plan, it's scheduled to be launched on November the 8th, as I said a few seconds ago. And also we're preparing our presence in Lisbon. So expect the FEM team to be there to meet with all of you, to chat with all of you about everything that you want to build. And to do a ton of knowledge transfer as well. Awesome, super exciting.