 over to Aynor to tell us about Network Version 17. Hi there. So Filecoin network goes through a few upgrades each year where we upgrade the L1 protocol. The last one launched on the 6th of July, which brought some great new stuff in particular enabling the FEM as the canonical VM on the network. While the FEM are working on user programmability, our next step is to launch a bunch of upgrades to the built-in actors and the built-in protocol so that when people can write their own contracts they can do cool things. So the main theme of this is to support utility for user-programmed things. So there's a bunch of new capabilities and a bunch of refactoring to make things play more nicely. This is all in a big effort towards programmable storage which is sort of the dream for Filecoin where Filecoin, your network stores your data and then you can write applications on top of Filecoin as smart contracts or actors that can do stuff with that storage. So broker deals, retrieve that data, compute over it, do all kinds of automated replication and renewal and the kind of things that people expect to be built into the protocol but are actually not. And also the finance on top of the storage that sets up the economic incentives for a robust birth supply and demand of storage. So there's a big set of proposals that are in scope for this network 17. Most of these have been in discussion for a long time. I'm not gonna talk through each one here but there's a large set associated with the programmability of the finance or the programmability of doing deals or the programmability of the storage that will enable better capabilities for user-programmed contracts when they're enabled. We're not necessarily gonna get everything that we'd like into this upgrade. So the age of the scope here is just being negotiated amongst the core devs community at the moment. And there's also a set of, a small set of proposals around sort of network policy. And so the biggest one here is the, changing the reward distribution to incentivize longer-term sectors and stabilize the storage product rewards. And associated with that, there is an opportunity to clarify networks policy. Should we ever discover flaws in the cryptographic security of the application? This is a thing where we wanna discuss upfront what kind of policy the network would take. So that storage providers have some predictability over their returns and what risk they're taking when they make really, really long-term commitments to their sectors. We're already a fair way through implementation for these proposals. Some of these are being built by teams outside of Critical Labs, which is fantastic and I think we wanna continue to expand. So there's a couple of, you know, the formal flips for some of these still being written, but the plans are well known. In some cases, we do the implementation at the same time as the proposal because the implementation tells us a lot about, you know, we learn things from writing the code that then form part of the spec. But we're well on track for this. So upcoming work here is the governance process for these FIPS that are not yet approved, needs to work through. And then ongoing implementation down a few streams, the CryptoNet team and the Lotus team are all lined up behind all of these items so that we can have aiming to finish writing all the code in the next month or so. And then start winding up the network upgrade process that works through your test nets and integration and so on, towards the next network upgrade, which will be sometime, you know, sometime October-ish this year.