Why We Built Both Margin Modes

Some platforms pick one margin mode and call it a feature. We built both, and the reason isn't that we couldn't decide — it's that they're fundamentally different tools for different trading approaches, and forcing traders to choose one is a product decision masquerading as a principled stance.

The case for isolated margin

Isolated margin is predictable. You allocate a specific amount, you know your maximum loss before you enter, and no other position can affect it. For traders who are placing single directional bets with defined risk parameters, this is exactly what they need. The position is self-contained.

It's also the safer mode for users who are still learning their own risk tolerance. When you can only lose what you explicitly allocated to a trade, you have a built-in safeguard against the portfolio-wide liquidation scenarios that tend to produce the most painful trading stories.

The case for cross margin

Cross margin is efficient. Capital that isn't actively at risk in one position can support another. For traders running multiple positions simultaneously — particularly correlated positions or hedged strategies — this is meaningfully more capital-efficient than maintaining separate margin pools for each trade.

It also makes hedging practical. If you're long BTC spot and short BTC-PERP as a hedge, those positions should be in the same margin environment. Forcing them into separate isolated accounts creates operational complexity and capital overhead that undermines the hedge's economics.

What this required on the protocol side

Supporting both modes correctly isn't just a UI decision. The margin accounting logic, liquidation engine, and position tracking all need to handle both modes without conflict. A trader might have some positions in isolated mode and others in cross mode simultaneously. The protocol needs to liquidate the right ones in the right order without touching the isolated positions.

Getting this right required significant work on the settlement and margin calculation layer. We tested it extensively under simulated stress scenarios before shipping, and the audit reports cover the cross-mode interactions specifically. It was worth the engineering effort because the alternative — picking one mode and telling traders to deal with it — is just a bad product decision.

What traders actually ask us

The most frequent question we get from newer traders is "which margin mode is safer?" It's the wrong frame. Safety depends on how you configure the mode, not which mode you choose. An isolated position with 20x leverage and no stop loss isn't safe. A cross margin book where each position is sized to 1-2% of total capital with clear correlation assumptions is quite manageable.

The second most frequent question is "why did my profitable position get liquidated in cross margin?" The answer is almost always that another position drew down the shared pool faster than the profitable position's P&L could offset it. Cross margin liquidations happen to the entire account, not to individual positions, when the total maintenance margin requirement isn't met.

Protocol implementation complexity

Supporting both margin modes correctly requires careful engineering. The margin accounting logic, liquidation engine, and position tracking all need to handle both modes without interference. A trader might run some positions in isolated mode and others in cross mode simultaneously. The protocol has to liquidate the right ones in the right order without touching isolated positions when the cross portfolio is underwater.

Getting this right took us several months of contract-level work and dedicated stress testing. We ran hundreds of simulated liquidation scenarios across mixed-mode portfolios before we were confident the behavior was correct at every edge case. It's one of the least visible features of the protocol, but it's the one that matters most when things go wrong.

Our data shows roughly 60% of Aark traders use isolated margin exclusively. About 25% use cross margin for their primary positions. The remaining 15% actively mix modes — those are predominantly the more experienced traders who understand both models and use each for the appropriate purpose.

The right mental model

Think of isolated margin as a separate trading account for each position. Think of cross margin as a portfolio-level account where all positions share the same capital base. Neither is better. They're tools for different objectives, and using the right one for the job is part of being a disciplined trader.

If you're not sure which to use, start with isolated margin. The predictability is worth the capital efficiency tradeoff while you're learning how a protocol behaves under volatility.