 We can go back through and take a look at those at the end. So Alfonso, if you want to start sharing your screen, you can take it from here. Thank you. So actually I'm going to share the whole desktop. You should be seeing like some slides and a terminal. Plenty of things. Cool. Yeah, great. So what I want to present today is the new after Madeira, we had a bunch of conversations with a lot of folks on how Sharding should look like in Filecoin. And this is the architecture that we have agreed on for now at least, which is like, if we want to start a new subnet, we don't call them Sharks anymore. I should like change this. If we want to start a new subnet, we have like the root chain that can be like the current Filecoin mainnet. And in order to give as much flexibility as possible to the users that want to deploy new subnets, we have this subnet coordinator actor, which is the one that enforces the hierarchical consensus. And then we have the, I mean, whenever someone wants to deploy a new subnet, what they do is deploy an actor that handles all of the specific logic that you may want to have in that subnet. Like because this is an algorithm that you want to use the collateral that you want to put in order to join the subnet and a lot of other things. So these new architecture, the goal is to give as much flexibility as possible for subnets and what enforces the hierarchical consensus protocol and the way in which like subnets interact with each other and so on. It's through this coordinator actor, which is the, it's a system actor that we already have in a RICO and in our implementation. And this is what I'm going to show today, a quick demo of this new architecture and also like something that we shipped last week, which is checkpointing to the pattern chain because in the way that like subnets leverage the security of their parent, if you remember like from my previous demo, like this is kind of how it looks the hierarchical consensus where you can start a subnet from any network and like child subnets leverage the security of the parent subnet and they interact with them through a set of checkpoints that include like cross-shared message and some, some verifications so that anyone that checks like this network can leverage the security and check that security is correct and the history is consistent. And I guess that you can see, let me know if like it's too small for you but here you should be actually let me guess to this you should be seeing my terminal and we have all of these implemented in a RICO. I'm going to start running two nodes to see all of this in action. Right, so I have two nodes I'm going to connect them to each other and I'm going to start mining like I'm going to start mining in the root chain like in order to make it easier in the root chain like we don't have the phycone expected consensus but we have what we call a delegated consensus which is like debug consensus where a single miner mines all of the blocks to make it faster. So right now like we have this root chain nothing special like we could interact with root chain with this root chain and that's it. We're going to do first is to deploy a new subnet that a child subnet over these root chain and sorry because in Eurika we added like a bunch of I think I showed this like in the previous demo day like we have a few comments to add a new subnet to join the subnet to list the subnet to start mining in a subnet, leave it, kill it and then these new one with which is the checkpoint which allows you to do a bunch of things with checkpoints from the child chain. So we're going to add a first subnet, we put a random name and we say that we want to start this subnet from root and with a specific consensus right now we only support two consensus in subnets which is a simple proof of work and these delegated consensus and this what it's doing is deploying the actor that handles all of the logic of the subnet. Right now we have like this reference implementation but in the like once FBN comes hopefully anyone would be able to do that and then comes hopefully anyone would be able to implement the subnet interface and like handle their own logic. Here we see that we have deployed the actor with this in this address and like the address of the actor that handles the subnet defines the address for the subnet. So now like up to now the only thing that we have is an actor we could like start mining that subnet but it make no sense because it would be an independent shape. If we want to register the subnet as part of the hierarchical consensus what we have to put is some collateral in the coordinate tractor. So what we do is we have this subnet at comment that join and we say that we want to join like from this address this subnet put into five points of collateral. Right, this is not my address. What we're doing here is like just putting two five points of collateral so that we have over the first ball of collateral in the coordinate tractor and we can register it so that we can start interacting with other subnets from these tiles. So if we look here like if we list the subnets we can see that the subnet is now active with this ID and it has two five points of collateral. We could even like join let's join from the other also from the other note so that we can see how we mine and sync both chains at the same time. So in this case I need to import some wallet and we're gonna also join with two partners. So it's waiting for the message to be final. And now like if we list the subnets we see that now we have foreign of collateral and the status is active. So we're gonna start mining from one of the I said that these subnets is a proof of work. We can start mining from one of the notes and we'll see that we're gonna so if I stop mining in the root chain we see that we are mining in also in the subnet. So right now we are only mining in the subnet and if I start the root chain we are mining in two different chains. Another interesting thing is that when we start mining in the subnet chain we start like periodically I mean by default we have a check period of 10 epochs. So every 10 epoch we will be committing from the tel subnet checkpoint in the parent chain in this case the root chain. And we can list like the checkpoints that are being periodically committed in the parent chain from the subnet with these checkpoints. We see that every 10 epochs we have a chain of checkpoints and like we add some information about the tip sets in the subnet and so on. And we commit it in the parent chain so that anyone can validate it. So at one point like we could use like this checkpoint validate command and validate the checkpoint for a specific epoch. What this will do is like take the checkpoint from the parent chain, check the subnet chain and see that the that is consistent with the tip sets that were committed in the parent chain and so on. And we see that again like we could change this check period but like if we list the checkpoints we see that the every 10 epochs we are committing a new checkpoint and these checkpoints are signed by a majority of miners. And as I'm running out of time I think they have like one minute let's leave the, we can also leave a subnet. Let's leave it from one of the miners. We can also interact directly with and send comments to a specific subnet. So for instance, we can list the file that we have here as we haven't like sent any funds yet to the subnet for this address. We have zero file points. And if we see in the root chain, if the root chain we have some file points. So we see that we have independent states. Also right now we only support like inter subnet transactions. So the cross chat transactions is what we are implementing right now but it should be, I mean, hopefully before or after Christmas we will have a demo of transactions that are going through subnets and cross net transactions. Right, so we saw that here like we're still committing checkpoints as long as we mine. So of course like I left from this miner we need to check it from here. We are still committed checkpoints as long as at least there is one miner and we are mining in the subnet. If we check like the subnet we see that the collateral is reduced because once a miner leaves the checkpoint it recovers it's as long as it hasn't been slashed which right now it can't be slashed because we don't have fat proofs it can recover its stake and it's collateral. And if we leave at some point we leave all of the miners leave or a majority of miners leave the subnet. What it will happen is that the subnet will be inactivated which means that as there's no enough collateral there can't be like checkpoints cannot be committed in the parent chain and it cannot interact like the subnet cannot interact with the rest of the networks in the subchain. And I run out of time but I just wanna run one last comment to show like how the network has been inactivated and it starts I mean it stops like interacting with the rest of the hierarchy because it doesn't have enough collateral. Thank you, perfect.