 This is a recap of the concept that we made in Dubai. We are in 1922 joining the World Team. And it's here in the German eye dragon as an external guest. So we had a lot of discussion and like all the future plans of the concept of the SLAB in 2022. And also product as a consent, so our environment presence was very valuable. We often, with receiving an overview of the SLAB plan as it stood in July 2021 when the group was found. And we're basically following the same plan. And we are first refining it on as we go. Then we had one join. The initial idea was that one joins in person. But then he joined the Zoom, giving an overview of basically how concept of SLAB projects stand in the big picture of our plans. So we focused on unique hierarchical consensus, FVM and computer data for each of which you will hear something in the rest of this summary. So that is particularly useful given that Ted is joined recently as Mr. Gigi Nier in January. But they joined actually during the team meeting in Dubai. And Sergi is joining in April. And Sergi and Nierce were also planning to move. And yeah, so now you'll hear about the summary of which of the sessions and each of the sub-projects that you have. So for the hierarchical consensus project, one of the things that we were planning for the final MVP, to wrap up the MVP, is that not fixing, but coming up with a solution for the design of atomic executions and the problem of atomic execution between different subjects. So in this first session, we introduced the problem because then we had a very good session to see potential solutions. We did a retrospective of the project on the roadmap after B1. B1 is the proof of concept that we will wrap up at the end of Q1. The third execution, it will include like process messages and all of the basic framework for character processes. And it would be really good that this is something that we are targeting but that we cannot come into, try to lure the back allowed project to be one of our use cases in primary consensus so that we can have the POC with these use cases, the first use case in the framework. After this, we plan the kickoff of B3. B3 is maybe like once we have the basic framework for character consensus, the idea is to translate it into a VM so that we can move towards production. And if what we're going to do is take what we have in the MVP and translate it into a VM so that we can go to potentially that doesn't have to start working into making it to production. And hopefully the plan is to give it to the next slide. The plan is to have immediate action items is first wrap up the B1. The MVP is the design of the atomic execution protocol that we have trapped, that we will include in this framework for the first implementation. We are targeting to publish a working progress paper of the current process framework in the VM NPS workshop. And we will have soon a low level plan. So right now we have a plan of like having B3 so the duration is the VM for end of Q2 but we will share a low level plan soon once we have like all of the pieces in place. And regarding the atomic transactions or the atomic execution, we find itself on an initial theoretical specification of how this can work and the properties that we want for this protocol. We discussed several implementation of how this could be integrated into the current framework. I think we have a quite solid first approach maybe it needs refinement but we have a quite solid approach that we can implement. And yeah, basically that's it for pulling in future demo days and future talks. We will share the specifics of the protocol. Thank you. So earlier this week, I presented our project V2 about checkpointing to Bitcoin which now has the super nickname Pikachu. Basically I did an overview of the POC that we decided to the newcomers that didn't know about it. Then we discussed some of the scaling ideas that we had and especially we came to the conclusion that scaling this project was more of a long-term research that there was no, like obviously to do it let's say. And so we may try to outsource this to a team of researchers in the future. What we are going to do right now is write on the project by finishing the implementation and the benchmarking and then the plan will be to submit the paper once we have all this. And next we also want to start an open discussion on this topic because we found that there are a lot of teams that are working on very similar project. For example, some folks from Cardano that Dragon knows as well as some folks from Stanford. So we would like to be more open and start engaging with them and then maybe together we can see if we can like get a longer nice scaling solution for this project. All right, so now something about consensus in the summits. So Dennis implemented first integration of the pandemic consensus protocol that could be used in the summits of the hierarchical consensus. And he recorded also presentation and a demo of what is done. And what they're still to do is benchmarking this pandemic implementation and seeing what is the over-heading post by Utico when the pandemic is part of Utico. And then we'll need to create a PR for the code and get some reviews on it and integrated with the pandemic. Sorry, with Utico. We need to perform some basic testing. And we also want to see how it reacts to faults in the system when some notes actually crash. We would like to have it running, flashing some notes and seeing how the protocol reacts and what the performance implications are. All right, and then we in general we want to have a efficient subnet consensus and then in an abstracted away manner that should be clubbable. And so the master goal is to use merely a T slash ISS which is a very recent state of the protocol here in the Eurosis Conference this year coupled with the Narwhal or Narwhal style Mempool implementation which is also presented in the same conference. And we want to have all this develop, test it and integrate it with Utico to be ready for a test and test the documentation I need this year. So for the action items, we need, we want to overlap. We will need to find the overlaps of this project with what Dennis was doing in the pandemic and try to integrate what can be integrated to avoid the working work. We want to implement also the Narwhal Mempool and we want to have a production ready integration with Utico. All right. Hello. So short update on G1 for the execution of wasn't in smart contracts. So we reached the first my thing which was basically really in the state of the app for smart contract production. So we discussed several approaches that have been proposed so far like using STM like runtime or using system analysis. And so after that, the first my thing the content strategy is going to work on the architectural design for all this smart contract production. The idea is to first take inspiration from the STM runtime. So meaning the technical computing transactions runtime and executing parallel of those that commit, those that have no conflicts and then serializing those that are conflict. The first step will be to assess the performance game that can be expected from parallel accesses to the IP list in the store. And for that, what we're going to do is write first description of the experiments and execute the program and contact the person in charge of this company in a game in the store to see with how what's the best way to start this. All right, fantastic. So on the topic of crypto economics we have this very fruitful call with the crypto econ lab team. And basically we've been already working async in terms of defining both the questions and the way to go about getting answers. But we use this opportunity to basically prioritize the questions that we actually need answered. In particular, even if we want to go public and create the fit and the test nets in like three or four and we want to have answers to the questions that we know are going to be asked by the stakeholders. So we have this call with crypto econ lab. We decided that, well, first, I think we settled on an interpretation of the questions and the assumptions. So we're on the same page now. And we decided with respect to the path forward to one set up a recurring call and two to actually do another week in sprints, a two week sprint with both teams sometimes in the near future, I would say number two where we will try to make significant progress and actually have this early answers to the empty zero questions. All right. The other topic we discussed was, of course, working in the open and also the transition issue to the PLV8 world. And of course, I mean, we already have a lot of our planning in the open and a lot of our open issues. But what we decided is that we are actually going to move all of the stuff that we currently have in private repos to our public protocol, especially Census Lab repo. We will be using it both for its issues and discussions. And we want to be really liberal around this. So, you know, even if you have a new form of idea, you can post it, we'll have a specific tech product, our thoughts. And then once a month, we will have a triage call in which we will go over this and see what actually needs more work in terms of curation. We do have a pretty busy plan for this year already. So, you know, the fact that we're creating an inventory and the back walk of open problems does not mean that it will be taken in the short term. But, you know, it will be important for us with our longer term planning. The other thing that we are doing, of course, no, actually, still on the bit of aspects. One thing that we discussed also with Dragan was basically the field protocol dense approach to actually proposing changes. And so we also have a fairly good idea of how we're going to go about actually communicating and socializing more mature ideas with the community using the proper channels in the following and the GitHub reproving with the Filecoin Foundation. And so basically, you know, issues, not issues, discussions in the community followed by presentations to coordinate, of course, we'll coordinate with the other stakeholders when doing this. And then, yes, the other thing that we are doing is moving off the VL Slack. We will be setting up home in the Filecoin Slack, a channel that will be consensus and will be repurposed from an existing channel from business days. And that will be the primary home for all communication with within and with consensus as well. I just want to go back quickly. So also mentioned already that one of our goals is to go support some new educational data called a yellow project. Perfect. So this is an interesting project that wants to do arbitrary computation or rate the story of the IPFS and Filecoin. It might be separate token, it might be the marketplace for like, you know, if you want to do market use type computations like two does it for what price, how long does it take? And basically when you do such a computation, you might want to spawn some ephemeral communication on the road. So this all builds as a nice use case for Unico where you can build this marketplace for arbitrary computation in L2, ephemeral, I'm just throwing this out as a sketch. So ephemeral subnets on L3 and so on. And for these reasons, actually it seems that computer data is a nice customer of unique one, basically one really, really, Filecoin make a use case for character consensus. We started discussing this in Batalla in last week. Then we start on Friday. This was a very frontal discussion and basically we're going to support and basically try to convince Batalla to use Unico as their home for this project. So this would be really, really nice use case. So we have some action items that are likely to fall off. Not too much, I would say this is not when you need just too much, but we are going to support all the Batalla team as much as we need. So, and to summarize next slide. So in some ways, all of this, we had a really important session with Dragon on productizing all what you hear so far. So far, by the way, you look at the diamonds here. On the next slide, I will just stop briefly. You will see our link, you'll be able to see our roadmap, but all what we discussed here is more related to the next two quarters. So Q2 and Q3, and here we are mostly Q4. So this is mostly about spawning a testnet in Q4 where we would be testing in practice in public and in practice hierarchical consensus, even consensus in sublets. And whatever we have ready by that point, we would roll out on the testnet in Q4, whatever comes later we'll roll out on the testnet as it comes. But basically this is transitioning to in our planning to the before project that's related to this testnet. And Dragon gave us really detailed overview of how things work. Since experience with step-deal subgroup, we tried to schedule things that are cardboard or network fabric, we'll try to combine them with as much network coverage as possible. It seems that this is one and not more, I think. And then we will be pushing things, posting users face to face if you want as a software. So basically you support new consensus protocols. This wouldn't require an upgrade from basically five point minus and CPs, right? But you couldn't, of course, if you want to support new protocols and so on. So we discussed this. This is supposed to be rolling out in Q4, this meeting the testnet with preparations, a lot of preparations for us in Q3 and of course with inputs from other sources. So just next slide briefly. Okay, so go to GitHub and we'll try to, as George explained, we'll try to keep everything in public. You already have the timelines for the projects discussed here on public GitHub. Use consensus at five point select to contact us so we can email others and so on. Thank you for your attention. All right. All right. All right.