 Thanks, thanks Patrick and Yolan. Good afternoon, everyone. I'm Hongyu from StoS with and yeah before my presentation I would like to send a special thanks to Jesse and Patrick and Yolan. Thanks for your invitation. Yeah, the people, so many people present the, from the critical graphic protocol level, I would like to introduce from the application level of time knock in encryption based. So this is the idea comes for time mask. Yeah, so let's go to the next. Yeah, about those with, yeah, as Patrick mentioned, we are a member of Niko of Fonsori and the first D-Round and Relay Loads joined from China. Yeah, last year we talked with this guy, Yolan and Patrick about the requirement of D-Round implementation in Rust. It's a good idea and from the security side and before that we still participate in the community only from the load setup perspective. So when we get the topic of D-Round in Rust, we need to put some research and some research in workflow. So okay, so we go through all the process, workflow of the D-KG and the random list generation and prepare for the D-Round in Rust implementation. Yeah, so here, yeah, of course we have a prototype demo for the Rust implementation. Yeah, here is a demonstration about the Rust implementation from the prototype level. Yeah, we set up a need load with the Golang version load and the member load in Rust version and connect them, combine them together for the prototype verification. Yeah, so the code base is still working in progress. So we still a lot, we have a lot to put it into the GitHub yet. So after we make it up and then merge it. Yeah, most of the work of us are focused on the engineering side. So we participate in the file calling ecosystem contribution, yeah, since space race. And we also participate in the building act of gas optimization before FVM launch. For some use case, the gas optimization, the gas optimization can improve the DTB. So sorry, yeah, some optimization method will reduce the gas consumption by 65%. Yeah, it's amazing. So it's very important to contribute for the TPS. Yeah, and we also take some optimization for the pre-commit phase one with a member pool optimization for the file calling and we each have the 35% improvement with the same hardware, especially for the memory. Yeah, of course, we also take the task loader's work in Rust implementation. It's in this method, in the FFI side effect performance. And we also contribute for the multi offline signature wallet for file calling. That's also from the engineering side. And we also participate in the FVM space swap impact evaluate with the moment swap project. Moment swap, it's an interesting depth. We call it NFT Instagram. You can check it. We also, we're also zero-logic cryptography experience player. And we are one of the the price competition winner of the project. Yeah, it's very interesting from the engineering side of it. Here is the agenda of the whole topic that I would like to introduce today. The first is about the depth builder. For time knock encryption, it's a great idea. Yeah, we want to bring this idea into our life. So we want to make people build the deeper, more easier. And then, the participant, we get the benefit or would like to contribute more on the platform. So that's the purpose of the first item. And the second is about the governance. The people participate in the marketplace and they have the power to take part in the governance of the marketplace. And the third is about the data analysis. Yeah, it's very important for the incentive model. We can take the analysis on the depth builder side and the end user use case aside. And then take it as the important stuff to engage the incentive mode. Yeah, the last one is about the incentive mode. How does the depth build get a reward? So first, about the depth builder, we use the low-code platform. Never really the low-code platform to enable users to build the depth more easily. Yeah. So here is the process of how to use the low-code building with the time lock encryption. Low-code is a visual approach to software development that enables the delivery of application through minor hand coding. And with the graphical user interface and drag and draw feature, platform also automates aspects of the development process and also emulates dependency on traditional computer program approaches. And yeah, the most important is about enable the depth building without the need for the professional experience on smart contract programming. It's amazing. Yeah, the people only need to drag and draw and focus on the logic of the business. The focus of the platform is more easier. The input data and the encrypt with the time lock encryption and then get the result. People also only need to wait the time lock released and then get the data and get the result. So that's the platform to make the depth build more easier. Yeah, this is an overview of the depth building. We customize the time lock encryption component and also the story, the IPFS storage component and also provide the near-to-pass-free encryption component. We provide these components in the platform. People only need to drag and drop and then preview the business process of the depth and then compile and then deployment check and then deploy. It's easy workflow. People don't need to care more about the detail Of course, we can also display the code detail of the depth and the people can check from the security side. We also provide some building depth. For example, here is an online example. From the teacher side, they can write down the exam papers and then upload it. Then we can have the near-to-pass-free encrypt to encrypt the data and then we add on the near-one the time lock encrypts. Then put the data into the IPFS node and get the CID. We encrypt the CID and then mint with the NFT. Then the process from the teacher side, we are finishing the process of this workflow. From the student side, it's the opposite of the workflow. They get the NFT and fetch the info and decrypt the data and then start the test and upload the result. There, the time out, the system will check the whole results and then the people can go through all the check and all the results and the exam. We have another building about power voting. We also supply some templates from the use case of power voting. Make people only need to connect the use case from the template of the component and then integrate into the, drag it to the workflow of the business and then build the depth. Yeah, it's also a simple logic about the power voting. Yeah, similar workflow. Yeah, it's an interesting topic about the time capture. How to make a wheel and how to make a secret. For example, the older parents want to leave some wells or some secret to the children and how to use the time lock encryption to make it happen. Yeah, we also need to encrypt some video record declaration and signature from the data and use the passphrase, the near to passphrase encrypt the data and add on the time lock encrypt and put the data into ipf and mint the fd. Yeah, of course, we can use the add on some rounds, round the loop during the workflow and make it more close to the real life. Maybe if some older parents make the wheel too long, need to break from the middle of the duration, we can use the server round to make it happen. Yeah, and more friendly, more useful to the use case. Yeah, it's about the governance of the time mask. It's important to the marketplace. We have the credit system. People can invite a new player to get the credit. And also get the credit by recombination, income in commanding people to buy and use depth. Yeah, and also get a real world where we are interacting with the depth in the marketplace. We also encourage people to use, especially for the depth builder, use the analysis tool and then get the credit. And the last item is about the from the under user side. Under user also can also get the credits by creating ticks with the depth. For example, from the teacher side, the teacher created the exam papers and he will pay some the token for the gas consumption and also get the credit by this action. Yeah, user can exchange the token on blockchain with their credits and this token has the voting power. The power decides if the depth available a lot in marketplace and also decides if the depth of new feature upgrading a lot. And the rule changes on credit in CCT and operation. Yeah, here is a marketplace rule map about from our side. We split four phases. The first is about the initial version. We enable the low code platform and the building with time lock component enabled. The second phase is about some building depth. Enable building depth with the online example power voting testament and so on. The third side is about the third is about enable in CCT rule with marketplace. The last one about the governance. Enable governance with marketplace. Yeah, let's go ahead. Data analysis on the dashboard with marketplace metrics. Here is a depth oriented analysis. Depth as a rating people can comment to the depth. And we also need to analysis about the depth of depth. That's the original of the revenue. And the third is about the statics on the daily or monthly active users of this depth. That decides the value of the if the depth is valuable or not. And the last one is about the recommendation. High quality depth to the under users and so on. Yeah, another side about the under use. The under use, the platform can track the number of the visitors of the depth as well as those where visitors come from. And what pages they are visiting and how long they are staying on those pages. Depth tick is the number created by under use and the value contributes static ticks. Yeah, it's from the user side perspective. This information is very important to the depth build to how to improve the user experience of their product. Yeah, the last one is about the incentive mode. Depth build can get rewards from the depth building on the platform. We have four dimensions about the incentive mode. The building, the fee allocation, and the depth rating and some airdrop. Yeah, builders can be rewarded by platform according to the number of depths or other contribution. The number of depths they contribute to the platform. They build more and get the reward more. And another aspect is the fee allocation. For example, if the builder of the online exam, someone creates the exam papers and then he would pay some cost to the ticket. And then this can be rewarded to the depth builder. The third is about the depth rating. The depth is used by people more and then it contributes to the platform more and then he can get more fee allocation and then you reward it. The last one is about the from the platform perspective. If the builder contributes to the platform more from the platform side, we give more reward to the builders. It's not a fix the activities, more flexible. Yeah. Oh, the last is about the idea brainstorm. I think the time lock encryption is a great idea about the random from the random list, random side. So we want to bring this feature to our life. Here is a more is a real use case of in life auction. All the people, so many people take part in the auction. If they don't, if they load each other, the price, then maybe the activity will go into a worst case. If the people write down the information and then open the words in a fixed time and then maybe have more more fail. Another is about the guessing game. It's a more interesting topic. Maybe you have more good use case in life. We can also bring it into the platform. Okay. Thanks. Thanks for your time. Yeah. Thanks so much for your talk, Hongyu. I had a question about that. You mentioned several examples of DApps. And I'm curious how how your companies found the rate of adoption among developers in China. Is this something that's very popular today, or is it really bleeding edge and just getting started? Yeah, it's very popular in China. For these ideas, once we talk this time about feature with Yulan and Patrick, the first use case comes from our mind is about the online exam. It's really a use case of the life, because it's very easy to cheat during the examination. Yeah. So I think the time lock in Crabby resolved this use case perfect, right? So we want to bring it into the platform first, let people to easy to use it and bring the value to the real life. Thanks. Yeah. Thank you.