 Hi, I'm from Salkett, we're visiting Germany. Today, we're going to talk about our project called this Patan Collection. This is a collection of design patterns for smart contract and it consists of coding patterns and their descriptions for smart contract, the draft plan. It's currently also support ERC and smart contract weakness classification history. As most of the developers know that design patterns is very important to see the draft development not only for coding efficiency, but also to avoid the amount of ability when developing a secure system. And in my experience, I found that there are a lot of design patterns on the internet spreading around the internet, but it's having gathered into the one place as a reference resource like, for example, like design patterns by the data form that's making the design patterns hard to find. We list these resources in our project to be there and to be important for looking into all those design patterns that we can find for all scale levels of developers and also to create our net community to improve the design patterns together in the long place. So now we're looking into the privacy, project and privacy. So there's three things involved. So the last column in this picture is the content resource. It can be our blog post, our ERC or smart contract weakness classification stuff. Or you can also even create a call request directly to our privacy. The main column is the component included in our project. The format that creates the mount json output and human-medium resource, like a mount-down output out of the design pattern resource. The left column is client that reads the json file for whatever it is. So we're going to explain one of the clients developed by Highcore, it's called Pied. Yeah, like I had mentioned, we can use the json output for dev tools and we work on like in for one dev tool, it's called Pied. Pied is a tool to analyze and interact with smart contract structures. So that's how it looks like. And now if you click on this icon, you will see a list of all the patterns reported. They are organized by tags. So if you filter for the security tag, you will see all the patterns which are related to security. So I will now select the state machine pattern. And on the right side, you now can see a sample implementation of this pattern in the middle and you can see a text describing this pattern. It's always has an abstract problem solution, reference section and there are comments where you can discuss something about this pattern. So if you see some disadvantages or so you can leave a comment. And on top you see a graph representing the contracts involved in this pattern. If you select one, you see on the left side the structure of this contract. And to understand it better, you can also deploy the example and play around with it. So now I will deploy back the team of this pattern. Now this contract has an address and you can also read the state variables and you can also send transactions. Like this now and yeah. Now the stage should have changed and yes, it changed. And yeah, that's it already. If you want to get involved then you can make a pull request. Thank you.