I’ve been lurking while you’ve all been chatting for a while, and today I got a lesson myself.



Last night, I had an order where the price level didn’t match when placing the order. I thought I’d manually snipe into the position, but the moment I clicked, the slippage hit me so hard I was stunned. The stop-loss level I had planned didn’t get triggered at all—I actually ended up losing a lot more than I expected. Looking back afterward, it’s basically because the order book depth wasn’t enough. When contract depth is awful, a big order gets absorbed and the price just rockets up. Meanwhile, I hadn’t even reacted on my side yet, and I hit my stop-loss. In plain terms: next time before placing an order, I need to check those few levels in the order book—not just stare at the K-line.

Lately there have been quite a few on-chain incidents: cross-chain bridges getting hacked and stolen, oracle price quotes going abnormal—so now everyone is basically “waiting for confirmation” to find out whether it’s safe or not. But honestly, waiting for confirmation still depends on the level of on-chain congestion. Sometimes waiting a few extra seconds and the price has already moved. This stuff really tests your timing.

Anyway, consider it tuition. For short-term trading, you can only take the losses if you can afford to lose. Discipline matters, but you also have to practice your order timing. That’s it for now.
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
  • Pinned