#fogo $FOGO @Fogo Official
6:18am.
Stop loss at $142.48. Filled at $139.20.
$3.28 drift across three slot boundaries.
Stop-loss protection built for block-based execution assumes trigger and fill share execution context. On FOGO's deterministic slot sequencing, they occupy separate closures.
Slot N: stop triggered at $142.48
Slot N+1: market order queued at $141.10
Slot N+2: order sequenced at $140.05
Slot N+3: filled at $139.20
Four execution contexts. Four independent price states.
Firedancer's deterministic leader schedule rotates every 40ms. Each slot boundary is a finality checkpoint. Stop-to-market conversion spans minimum two slots—under volatility, three to four.
On 40ms cadence, stop trigger and fill cannot occupy the same slot unless submitted and executed within a single 40ms window. During price movement, that window closes before the market order queues.
The risk isn't slippage. It's slot-boundary exposure.
Protection exists in Slot N. Position closes in Slot N+3. Different execution states. Different orderbook depth. Different price discovery.
On FOGO's 1.3s finality model, consensus finalizes every 33 slots. Stop execution spanning three slots means protection trigger finalizes before position exit. Protection and exit exist in different finality windows.
On FOGO’s slot-based execution model, stop-loss protection spans independent deterministic closures. Trigger and exit do not share execution state.
Protection evaluates in Slot N.
Exit executes in Slot N+3.
The slot boundary does not wait for your stop.