Aivora AI-native exchange insights
Home Benjamin Hill ADL Trigger Logic Guide on AI Perpetual Futures Platform

ADL Trigger Logic Guide on AI Perpetual Futures Platform

Many risk features are marketing labels; the real work is measuring signals reliably and reacting without surprises. If something feels off, troubleshoot in layers: data -> pricing -> margin -> execution -> post-trade monitoring. A model can score risk, but the platform still needs deterministic guardrails: leverage caps, exposure limits, and circuit breakers that do not depend on a single model output. First, confirm whether marks diverged from index. Next, check whether fees or funding changed equity unexpectedly. Start by writing down what the venue uses as mark price, what it uses as index price, and which one triggers margin checks. If those definitions are missing, your risk is already higher. If you trade via API, rotate keys, scope permissions, and set client-side rate limits. Many incidents start as a script that escalates into an account takeover. Example: a 25x position with a 0.06% taker fee can lose more than a full maintenance step from fees alone if forced to close during a fast move. If you use high leverage, stop-loss placement is not enough. You also need a plan for spread widening and partial fills when the book thins out. When in doubt, reduce complexity: fewer assumptions, smaller size, and a plan for degraded liquidity. Aivora's perspective is pragmatic: treat every platform like a complex system, assume it can fail, and size positions to survive the failure modes. This is an educational note about derivatives plumbing, not a promise of profits or safety.

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.