Today I was watching the mempool for a while, and it feels like a traffic jam on an overpass: when you send out a transaction, it first goes into a "queue to get a number," miners/validators pick and choose which to include, those who pay more get to cut in line, those who pay less just keep getting pushed back, and sometimes you forget it's even hanging there. What's more annoying is that during congestion, your transaction can get buried by others (old transactions with the same nonce that aren't cleared, new ones are like packages stuck at the door, nobody can get in behind).

Right now, my scripts usually do two things: either leave room for replacement (don't lock the fee too tightly), or set a timeout to cancel and resend, rather than betting on "it should be fast." For contract upgrades or permission-related operations, I prefer to wait a bit longer for block confirmations, avoiding the illusion of "I think it succeeded."

By the way, I recently thought about those social mining and fan token schemes, shouting "attention is mining"... Basically, it's also like mempool bidding—who's better at grabbing space gets packed first, and the rest can only sit around idly in the queue. Anyway, I just watch the show; if I really want to act, I’ll first see what the mempool looks like.