Recently, I’ve been looking into MEV and these “queue-jumping” issues. Put simply, whoever gets included in a block first can capture price changes first. The impact isn’t just on high-frequency bots; it’s more often ordinary people. You think you’ve placed your trade and you’re just waiting your turn, but then you get sandwiched, the slippage gets worse, or—if things go really off—the execution price is outrageous. In terms of the experience, it’s basically, “How am I getting screwed again?” When you think about it afterward, it’s kind of ridiculous. We’re calling for on-chain transparency, yet we assume that someone can pay to get pushed further forward.



Developers are excited about modularization and the DA layer, but users are genuinely clueless. You tell me to put the data on which layer, and settle it on which layer—I just want to make sure I don’t get queue-jumped… Anyway, my current approach is pretty crude: for large amounts, go slower, split it into several smaller batches, and if a limit order is an option, don’t use a market order. At least then I don’t feel quite as uneasy. As for fairness, it may not be “no one gets to queue-jump,” but rather ensuring that the cost and benefits of queue-jumping don’t always end up on the heads of people who understand the least.
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