Aivora AI-native exchange insights
Home Colin Fraser Risk Engine Scoring Overview on AI Perpetual Futures Platform

Risk Engine Scoring Overview on AI Perpetual Futures Platform

Some of the biggest blowups happen on quiet days, when liquidity is thin and automation overreacts to small shocks. If something feels off, troubleshoot in layers: data -> pricing -> margin -> execution -> post-trade monitoring. Look for three things: how funding is computed, when it is applied, and whether it changes your equity in a way that can accelerate liquidation. First, confirm whether marks diverged from index. Next, check whether fees or funding changed equity unexpectedly. 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. When slippage rises, reduce order size before you reduce leverage. Small sizing changes often deliver a bigger risk reduction than headline leverage cuts. Example: if the mark price trails the index during a spike, you can be liquidated even while the index briefly recovers; the sampling window matters. Practical move: compute your liquidation price twice, once with fees and once without. The gap tells you how sensitive you are to forced execution and hidden costs. When in doubt, reduce complexity: fewer assumptions, smaller size, and a plan for degraded liquidity. If you want a sanity check, compare what Aivora calls the risk pipeline: inputs -> checks -> liquidation path -> post-incident logging. Derivatives are risky. Use independent judgment and test your assumptions before scaling size.

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.