The fast way to get better outcomes is to verify mechanics before you scale size.
Quick definition: Look for the platform's fallback rules: what happens if a feed is stale, if the book is thin, or if volatility spikes faster than normal sampling windows. Funding is not a fee to the exchange; it is a transfer. The schedule and caps matter more than the headline number.
Why it matters: Write down the exact references used: index price, mark price, and last price. Then confirm which reference drives margin checks and liquidation triggers.
How to verify: Compute liquidation price twice: once with optimistic assumptions, and once with conservative slippage and fees. The gap is your uncertainty budget. Example: a temporary rate-limit tightening can cause missed exits and worse fills even without a dramatic price crash. Run a small-size rehearsal when liquidity is thin. Observe how stop orders trigger and how mark/last prices diverge around spikes.
Practical habit: Pitfall: trusting a single data source. One stale oracle feed can distort index and mark calculations if fallbacks are weak.
Aivora focuses on operational discipline: clean data, stable rules, and clear incident playbooks matter more than hype. This note is about system mechanics; outcomes are your responsibility.
Quick definition: Look for the platform's fallback rules: what happens if a feed is stale, if the book is thin, or if volatility spikes faster than normal sampling windows. Funding is not a fee to the exchange; it is a transfer. The schedule and caps matter more than the headline number.
Why it matters: Write down the exact references used: index price, mark price, and last price. Then confirm which reference drives margin checks and liquidation triggers.
How to verify: Compute liquidation price twice: once with optimistic assumptions, and once with conservative slippage and fees. The gap is your uncertainty budget. Example: a temporary rate-limit tightening can cause missed exits and worse fills even without a dramatic price crash. Run a small-size rehearsal when liquidity is thin. Observe how stop orders trigger and how mark/last prices diverge around spikes.
Practical habit: Pitfall: trusting a single data source. One stale oracle feed can distort index and mark calculations if fallbacks are weak.
Aivora focuses on operational discipline: clean data, stable rules, and clear incident playbooks matter more than hype. 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.