 I'm Paul, and I won't be talking about ERC-20 tokens. I guess every Korean developer has been through ERC-20. Codebase probably uses open zeppelin code. I'm going to be talking about a very specific feature, which is the max-approval thing. Many dApps have been using it, and it's way less secure than we may think. In the middle of me, I'm building this project called Sibir, an app and brought forth real-time payments. Imagine getting your salary every second. I published a beta version of the project in early this summer. Of course, I looked at other dApps, and I saw that they have this max-approval thing. I said, let's do it. Sounds cool. It's easy because you only have to ask your resource once, and then that's it. This is how it looked. You have to approve the Sibir contract once, and that was it. All things work. It went fine for like one or two months. I had like 15 people posting 100 die in total. It was not a big deal. I was like, it's fine. If there's a bug, it's fine. No. Because of this thing, there was a bug, and we're the big one. Even if in the contract you only had 100 die, the trees I put by mistake are more than 10,000 in total. Because there was a bug in the contract that allowed people to create streams, what I said, like real-time payments, using the ER students' allowance, and pay themselves, basically. Using the money that was not in the contract, funny enough, the money in the contract was safe, but the money outside the contract was not safe. So that's why I like to call this thing missing the force for the trees. So that tree is your smart contract, beautiful, secure, and whatnot, but the ER students' allowance is basically in the back, and you're not seeing it. So how can we solve this? Do you have all we have to build better wallets? I know it's still kind of early days, but this is bad UI. There's no way I can easily explain this to anyone. It's a big number. It looks like some app wants to steal all your money from the wallets right now, even if it's just looking approval, right? So there's that. And in the back end, this is what we can do as developers. There are three solutions. The first one being that you can use a different token. It's not going to be good, because most tokens are ERC-20, and yeah, just we're stacked with this standard at the moment. But hopefully in the future, we'll be using more stuff like this. Then you can use a metal wrapper that if you pay custom-wide, developed a way to deposit, die, and use it in a safer manner. I think they use this with the new standard developed by Engine called 1155. It's good, but still requires user input, so that's quite troublesome. And the optimal solution is to sign through transactions. So you go to your app, and you have like a proof, and then spend. And even if that is slightly better UX, you can sleep better because you know that in case there's something bad, the forest is fine. The forest is safe, right? So kudos for kickback for doing this. I think UI is good enough. I didn't have any problem with allowing and then spending. So that was it. Thank you for this.