Blockchain

Stop-Loss vs. Stop-Limit: Why a Trigger Is Not a Fill

Read full article at source ↗

Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 27/10/2026, 13:27:25 UTC.

Briefings

The provided evidence explains that stop-loss and stop-limit orders behave differently because a trigger does not guarantee a market fill. A matched price-gap example demonstrates that one order can sell below its trigger while another leaves tokens unsold, highlighting the risk of premature execution. The source material does not specify the exact number of tokens affected, the specific trading pair, or the time of the event, leaving these details unknown.

Key points

• A matched price-gap example shows that one order may sell below its trigger while the other leaves tokens unsold.
• The source does not specify the number of tokens affected, the specific trading pair, or the time of the event.

Context

Onchain swaps add liquidity and transaction checks to the trading environment, which is where the discrepancy between trigger orders and actual fills occurs.

Limitations

The evidence is limited to a single matched price-gap example and does not provide specific numbers, the specific trading pair, or the time of the event.

Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 27/10/2026, 15:02:46 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.

View archived briefing on IPFS
bafybeignlnvg5tm5i5t4remsoehkkz33hy65kyx4lsx7mbk53vbhnigtou