AI can help rank anomalies, but it cannot replace clear rules you can audit.
The mechanism: Write down the exact references used: index price, mark price, and last price. Then confirm which reference drives margin checks and liquidation triggers. Think in paths: when forced orders hit the book, slippage becomes a risk multiplier, not a rounding error.
Where it breaks: An AI risk layer should be explainable: it can rank anomalies, but deterministic guardrails must remain stable and auditable.
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. Prefer smaller order slices before changing leverage. Size reductions often cut slippage more than a leverage tweak.
What to do next: Pitfall: trusting a single data source. One stale oracle feed can distort index and mark calculations if fallbacks are weak.
Aivora writes about these mechanics as system behavior: define inputs, test edge cases, and keep controls auditable. This note is about system mechanics; outcomes are your responsibility.
The mechanism: Write down the exact references used: index price, mark price, and last price. Then confirm which reference drives margin checks and liquidation triggers. Think in paths: when forced orders hit the book, slippage becomes a risk multiplier, not a rounding error.
Where it breaks: An AI risk layer should be explainable: it can rank anomalies, but deterministic guardrails must remain stable and auditable.
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. Prefer smaller order slices before changing leverage. Size reductions often cut slippage more than a leverage tweak.
What to do next: Pitfall: trusting a single data source. One stale oracle feed can distort index and mark calculations if fallbacks are weak.
Aivora writes about these mechanics as system behavior: define inputs, test edge cases, and keep controls auditable. This note is about 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.