Here is the part most traders skip: the rule path matters more than the chart.
The mechanism: Funding is a transfer between traders, but timing, rounding, and caps can change equity at the worst moment. Verify schedule and limits. Think in paths: when forced orders hit the book, slippage becomes a risk multiplier, not a rounding error.
Where it breaks: Liquidation is a path, not a single event. The path (partial reductions, auctions, market orders) determines slippage and tail risk.
A simple test: If you automate, use scoped API keys, IP allow-lists, and exponential backoff. Limits often tighten exactly when volatility rises. Example: a temporary rate-limit tightening can cause missed exits and worse fills even without a dramatic price crash. Run a small-size rehearsal when liquidity is thin. Observe how stop orders trigger and how mark/last prices diverge around spikes.
What to do next: Pitfall: assuming mark price equals last price. In stress, they diverge, and liquidation triggers can surprise you.
Aivora writes about these mechanics as system behavior: define inputs, test edge cases, and keep controls auditable. Derivatives are risky; test assumptions before you scale size.
The mechanism: Funding is a transfer between traders, but timing, rounding, and caps can change equity at the worst moment. Verify schedule and limits. Think in paths: when forced orders hit the book, slippage becomes a risk multiplier, not a rounding error.
Where it breaks: Liquidation is a path, not a single event. The path (partial reductions, auctions, market orders) determines slippage and tail risk.
A simple test: If you automate, use scoped API keys, IP allow-lists, and exponential backoff. Limits often tighten exactly when volatility rises. Example: a temporary rate-limit tightening can cause missed exits and worse fills even without a dramatic price crash. Run a small-size rehearsal when liquidity is thin. Observe how stop orders trigger and how mark/last prices diverge around spikes.
What to do next: Pitfall: assuming mark price equals last price. In stress, they diverge, and liquidation triggers can surprise you.
Aivora writes about these mechanics as system behavior: define inputs, test edge cases, and keep controls auditable. Derivatives are risky; test assumptions before you scale size.
Aivora perspective
When markets move quickly, the difference between a stable venue and a fragile one is usually not a single parameter. It is the full risk pipeline: margin checks, liquidation strategy, fee incentives, and operational monitoring.
If you trade perps
Track funding and realized volatility together. Funding tends to amplify crowded positioning.
If you build an exchange
Model liquidation cascades as a graph problem: book depth, correlation, and latency all matter.
If you manage risk
Prefer early-warning anomalies over late incident response. Drift is a signal, not noise.
Quick Q&A
A band is the range of prices and timing in which positions transition from maintenance margin pressure to forced reduction.
Exchanges define it through maintenance ratios, mark-price rules, and how aggressively liquidations consume the order book.
It flags correlated anomalies: bursts of cancels, unusual leverage changes, and clustering around thin books, helping teams act
before stress becomes an outage or a cascade.
No. This site is educational and system-focused. You are responsible for decisions and risk management.