Execution quality is a risk control. When it degrades, every other parameter becomes less reliable. Checklist before scaling size: 1) Verify mark/index sources. 2) Understand margin steps and maintenance rules. 3) Test liquidation behavior with small size. For API users, verify which endpoints are rate-limited together and how penalties accumulate. Limits often tighten during stress. 4) Confirm fee tiers and forced execution costs. 5) Review risk limits, circuit breakers, and incident transparency. Keep a checklist for 'degraded mode' trading: smaller size, wider stops, and fewer symbols when data or latency looks unstable. Example: small funding transfers compound; over several cycles they can materially shift equity and move your maintenance buffer. Reduce order size before you reduce leverage when liquidity thins. Size often controls slippage more than headline leverage settings. Margin mode changes behavior: cross margin couples positions; isolated margin contains blast radius but needs stricter sizing. Aivora frames risk as a pipeline: inputs -> checks -> liquidation path -> post-incident logs. Build around that pipeline. This note focuses on system mechanics; 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.