Just now, while munching on potato chips and staring at the mempool, I suddenly thought of setting a small rule for myself: once the network starts to get congested, I’ll assume "the transaction I send is just waiting in line and getting squeezed," and not rush to repeatedly click confirm to accelerate. Because your swap actually will first be observed, compared, and even casually inserted into the queue among a bunch of pending transactions, and the route might be rerouted in a very convoluted way. In the end, you might be shocked by the slippage or just fail outright and have to pay some tuition fees... Anyway, during congestion, I prefer to go slower and do less. Recently, AI agents and automated trading have been getting a lot of hype, but I care more about whether they actually keep nonce, authorization, and replay attack protections in check—don’t hype it up with fancy talk, only for users to get exploited and doubt everything in the queue. That’s all for now, finish this bag of chips and then decide.

View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pin