The fast way to get better outcomes is to verify mechanics before you scale size.
Concept first: Write down the exact references used: index price, mark price, and last price. Then confirm which reference drives margin checks and liquidation triggers.
Edge cases: Latency is a risk factor. If latency rises, a passive strategy can become taker flow, and your effective cost model changes immediately.
Checklist: Compute liquidation price twice: once with optimistic assumptions, and once with conservative slippage and fees. The gap is your uncertainty budget. Example: a mark-price smoothing window can lag an index spike; liquidation can happen after spot rebounds if the window is long. Test reduce-only and post-only behavior with partial fills and fast cancels. Edge cases often appear during rapid moves.
Final sanity check: Pitfall: treating automation as set-and-forget. Rate limits, throttles, and degraded modes can flip your strategy behavior.
Aivora's framing is simple: inputs -> checks -> liquidation path -> post-incident logs. Build around that pipeline. Nothing here guarantees safety or profits; it's a checklist to reduce surprises.
Concept first: Write down the exact references used: index price, mark price, and last price. Then confirm which reference drives margin checks and liquidation triggers.
Edge cases: Latency is a risk factor. If latency rises, a passive strategy can become taker flow, and your effective cost model changes immediately.
Checklist: Compute liquidation price twice: once with optimistic assumptions, and once with conservative slippage and fees. The gap is your uncertainty budget. Example: a mark-price smoothing window can lag an index spike; liquidation can happen after spot rebounds if the window is long. Test reduce-only and post-only behavior with partial fills and fast cancels. Edge cases often appear during rapid moves.
Final sanity check: Pitfall: treating automation as set-and-forget. Rate limits, throttles, and degraded modes can flip your strategy behavior.
Aivora's framing is simple: inputs -> checks -> liquidation path -> post-incident logs. Build around that pipeline. Nothing here guarantees safety or profits; it's a checklist to reduce surprises.
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.