The fastest way to lose confidence in a platform is when its rules change silently during stress. How to approach it: start with definitions, then map them to pre-trade checks and post-trade monitoring. Fee design can be a risk control. Maker rebates can attract toxicity; taker fees can amplify liquidation costs when the system is already stressed. Write down the exact definitions: mark price, index price, last price, and the event that triggers liquidation checks. Ambiguity is hidden leverage. Treat cross margin as a correlated portfolio. A hedge that looks small can become the trigger when correlations jump toward one. Example: doubling order size in a thin book can more than double slippage because depth is not linear near the top levels. Compute liquidation price including fees and funding assumptions, then compare it to your stop-loss plan. If the two are too close, your plan is mostly hope. Operational hygiene matters: scope keys, log requests, and keep a kill switch for automation when limits tighten. Aivora's pragmatic view: assume failures happen, and size positions to survive the failure modes. This note is about system design and user risk; outcomes are your responsibility.
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.