Actually, everyone understands that mempool is just the waiting room for transactions. The more congested it gets, the more it resembles the Spring Festival travel rush: you just submit your order, and it gets pushed to the back by a bunch of people willing to pay more "fare." By the time you realize it, the quoted price is no longer the same, and slippage suddenly aligns like a rhyme—what matches is a loss.

When I experience congestion myself now, I first glance at the depth, don’t rush to send everything at once, break it into smaller parts, and set an acceptable range. If it doesn’t work, just cancel and try again. After all, the most frustrating part of queuing is “I’ve already submitted, why hasn’t it gone through yet.” Recently, before and after the upgrade of that mainstream public chain, everyone in the group was guessing whether projects should migrate. I think a more realistic approach is: don’t try to force transactions on the chain right before or after maintenance windows. When it’s congested, your transaction either fails or turns into a slow poem.