Seeing how many of you have brought this up, I’m not being stubborn about it. I discussed it with the dev team today, but it’s a bit tricky to handle. When a hot topic pops up, the system instantly pushes it out. At that moment, we need to analyze the token structure and block it within milliseconds (since the token injection happens in seconds). This level of computation would crash the trenches and seriously affect the chain-scanning experience. And that’s just for one address. If you guys add a few more, we might not even need to scan the chain anymore. Optimizing this is a long process, and it’s like trying to put out a fire with distant water. Maybe some plugin can handle this feature instead. Plugins doing this won’t have much of a performance burden.