Execution integrity & limits
Snapshot liquidity, source freshness and the boundaries of the simulation.
On this page
A shared quoted-liquidity budget
Consumed size is recorded against market, book timestamp, execution side and price level. Manual orders, pending orders and forced closes use the same durable budget. Concurrent requests and retries cannot reuse one timestamped level beyond its quoted quantity.
A newer source timestamp creates a new snapshot budget, even if the shown size is unchanged. The simulator cannot know whether a real level replenished, cancelled or traded between observations. Simulated fills do not alter the real order book.
Scheduling is not exchange priority
The worker checks account risk before pending intents. Pending intents rotate by last check time, with reduce-only priority on ties followed by creation time and ID. Manual requests can interleave through lock acquisition.
This does not promise global FIFO, passive-maker priority or queue placement on Hyperliquid. A richer passive model would require specified queue and trade-print inputs, not just a candle’s high or low.
Freshness checks
Server market context has a five-second cache. Execution rejects books more than eight seconds away from the server clock and context fetched more than eight seconds ago. The context fetch time is when the server received the response; it is not an independently verified mark timestamp from the exchange.
Concurrent book requests are coalesced while in flight. Healthy markets remain usable when another dex or a malformed asset is excluded, but every exposed account still needs its own required prices.
Request budgets and recovery
A durable owner budget charges entry attempts before market RPC: a burst of 30 with a refill of one per second. Protective actions have a separate burst of 30 and refill of two per second. Rejected attempts also consume this infrastructure budget.
Known successful exact-key retries return stored results before quote fetching or request-budget consumption. The app preserves the original body when the outcome is uncertain. Infrastructure budgets are not extra trading fees or account-loss rules.
What can and cannot be reconstructed
Fills retain consumed levels, quantity, average price, fees, realized P&L and source book time. Intents retain limits, triggers and lifecycle. Funding retains rates and recorded oracle samples.
The current ledger does not store every original full book or every observed trigger mark. It cannot reconstruct missed tick-by-tick paths, an exact passive queue position or historical marked equity from data that was never recorded.