 I'd like to discuss a real entity of steps of kind of the world smart contract. So I'm a research engineer at IXA. I'm also a volunteer community building kids' neural networks, working with the NS20 and the university. So you can find me out. And basically, this is not IXX. This is the idea on the side of doing intelligent benefit IXX in the whole community. Some people are saying that. And it's partially true. When you add a real entity to a contract, you add the ability for someone to change the code and violate invariance that you assume were there. They could steal your token. They could change the rules of the game. And you don't want that. But it's a bit more complex. It is smart contract ability, has its strengths, and its weaknesses. And there are cases where you don't want that. Obviously, I would not want an NS20 to be a great name or somehow. But there are cases where it makes sense. And those cases are where also the contract is clearly established. And this is true for DAOS. But most likely for a mixing wallet, like with some grills. A mixing wallet is somehow owned by one people or a community of people. And if they agree, there is no reason why they could not change the rule that how they want to treat their assets but who they want to enforce. So how the mixing wallet works? Basically, it's a multi-chain smart contract that holds your token or your token or everything that is related to your identity. And multiple private keys can sign transactions that will be recognized by the wallet. And depending on the rule of the wallet, so a wallet can interact with one of many applications. It's very good because even for a user, you may want to put one private key to be back. You don't have to bother about secrets. And if you're using a smartphone, then your desktop can basically remove this key that you're using and create a new one. But what about DAOS? I mean, all those wallets need DAOS. I mean, it's a bit painful. So what we do is we use that transaction. We make it with that transaction. They are awesome. And they allow the wallet to just sign some meta transactions or just a sign message and have a relay or send a transaction to the network. That's great. But then, what about the credibility? We don't have a credibility here. So we could use an ARC725 proxy. It's pretty nice. It holds a lot of meta data and it separates basically identity from the multi-chain logic. These could work great. And if you want to update the logic, you just deploy a new contract, that's the ARC725 proxy to bond to that new one. So you set up a new security and then you bond to it. It works really great. The thing is, the on-chain wallet and proxy are just from different contracts and only one of those has tokens. So if you want to refund the meta transaction, this is a bit of an issue because to refund the meta transaction, the on-chain wallet has to be aware that there is a proxy and has to go that way to send tokens back to the relayer. So there is a much better way. And this way is to use while we could proxy contracts, but not like the ARC725 proxy, proxy using the database code. And this is what starting to emerge in the community, like universal again is doing it and it's great. And the thing is, this proxy will hold the token because it's a single address. But it has the memory, but not the code. What it does, it delegates the code to what you call a master. You could use that, you could do that using, it opens up in infrastructure like ZOS sleep does that. But once you do that, it's pretty good. If you want to update your contract because there is a bug or you want to change your logic, you just use another on-chain wallet and you have proxy points to that one. And the on-chain wallet, the code, the big contract on-chain, the logic is the same for everyone. People just have proxy that point to it. So in terms of safe space, on the blockchain, it's good for everyone. So that's the issue with that. It's the issue that was here before I came in, basically, that's when you could upgrade from one contract to another, provided that the memory pattern is the same. But if memory pattern changes, then you're basically screwed. And the thing is, this could happen in the future when one of the white providers goes out of service. And we don't know how long, like, Argent or Universal are going to be there for, and you would like to keep your address and be able to migrate, not only upgrade, but migrate from one provider to another while keeping your account. And this is particularly important for, like, claims or assets that you can transfer from one provider to another. So this is what I did at TTSCC. It's called Kitsune Wallet. It's just a very small layer for proxy that have a great ability. I have mastered, as you can see, an example of how you can do migration from one wallet to another. My goal is not to build multi-signals, even though I do, my goal is to raise awareness about the importance of the great ability and migability of wallets. You can check it out, check this out on GitHub or everywhere, and it's funded by Iexac and Binance. It's used by Sheephole for proxy plus VTC, and I've been discussing a lot with Universal again, so there are also, even though they don't use my code, it's very similar pattern. Thank you.