As the on-chain derivatives market matures, traders increasingly focus on protocol stability under extreme conditions. For on-chain Perpetual Futures protocols, the risk system is critical not only for the safety of user positions but also for maintaining the protocol's solvency and market liquidity.
Why Does Phoenix Need a Risk Control Mechanism?
Perpetual futures allow users to amplify market exposure through leverage, but leverage also magnifies loss risk. During sharp price swings, account equity can decline rapidly. Without timely risk control, the protocol may face bad debt issues.
Unlike spot trading, positions in perpetual futures markets change value continuously, requiring real-time risk monitoring. Phoenix's risk system must achieve several goals, including:
- Verifying sufficient user margin
- Curbing excessive leverage risk
- Containing bad debt during extreme events
- Ensuring stable market operations
Because Phoenix uses a Fully On-Chain model, all risk checks run on-chain rather than being manually controlled by a centralized entity.
How Does Phoenix's Margin Mechanism Work?
Margin is the cornerstone of risk control in perpetual futures trading.
When opening a position on Phoenix, users must provide a certain percentage of initial margin. This capital covers potential losses and determines the leverage level available.
For example, with 10x leverage, a user only needs to provide a fraction of the position value as margin.
As market prices fluctuate, account equity updates in real time. Phoenix continuously calculates:
- Account Equity
- Unrealized PnL
- Available Margin
- Leverage ratio
If equity drops below the maintenance margin requirement, the system may trigger liquidation.
Unlike centralized exchanges, Phoenix's margin status is fully transparent, with all risk data verifiable on-chain.
How Does Phoenix's Risk Engine Work?
Phoenix's risk engine monitors market and account conditions in real time.
When a user submits an order, the risk engine first checks whether the account meets opening conditions, including position size, leverage, margin balance, and market risk parameters. Only orders satisfying risk requirements enter the order book.
After execution, the engine continues to monitor account status. As market volatility increases risk, the system may restrict additional position increases or even trigger forced liquidation.
Given the fast-moving on-chain derivatives market, the risk engine must stay synchronized with the order book, Oracle, and settlement system.
What Is the Role of Phoenix's Funding Rate Mechanism?
Phoenix uses a Funding Rate to keep perpetual futures prices aligned with the spot market.
Since perpetual futures have no expiration, their price may diverge from spot for extended periods. The funding rate mechanism encourages balance through periodic payments between long and short positions.
Under normal conditions:
- When the perpetual price exceeds spot, longs pay shorts.
- When the perpetual price is below spot, shorts pay longs.
The funding rate affects both trading costs and market leverage direction.
For Phoenix, this mechanism reduces the risk of prolonged imbalance and mitigates the impact of price divergence on protocol stability.
What Role Does the Oracle Play in Risk Control?
Although Phoenix uses an order book model, its risk system relies on the Oracle for reference market prices.
Oracle data is primarily used for:
- Calculating the Mark Price
- Assessing account risk levels
- Triggering liquidation logic
- Preventing market manipulation
Relying solely on order book fill prices can lead to short-term anomalies in low-liquidity environments. Therefore, Phoenix combines Oracle data to maintain risk system stability.
In on-chain derivatives protocols, the Oracle is critical infrastructure. Abnormal Oracle prices can cause erroneous liquidations or escalate market risk.
Thus, Phoenix's security depends not only on its order book structure but also on the quality of Oracle data.
How Does Phoenix's Liquidation Mechanism Work?
When account equity falls below the maintenance margin requirement, Phoenix triggers Liquidation.
The liquidation system aims to prevent further losses on the account and protect the protocol's solvency.
When triggered, the system:
- Checks account risk level
- Partially or fully closes positions
- Recovers outstanding risk exposure
- Updates market status
Because perpetual futures involve leverage, liquidation can occur rapidly during volatile markets.
Phoenix's liquidation logic runs on-chain, meaning all records are publicly verifiable rather than processed internally by a centralized platform.
However, on-chain liquidation is affected by network performance. Therefore, Solana's high throughput and low latency are vital for Phoenix's risk system stability.
How Does Phoenix Handle Extreme Market Conditions?
Extreme conditions are a major risk source in on-chain derivatives markets.
Rapid surges or crashes can cause mass liquidations, liquidity shortages, severe price deviations, and delayed liquidations. Phoenix's risk system mitigates these impacts through dynamic margin parameters, risk limits, and funding rate adjustments.
Additionally, the order book model improves price discovery efficiency. Compared to AMMs, order books offer finer price management in volatile markets.
However, systemic risks persist in on-chain perpetual futures markets. Even with risk control mechanisms, potential losses from market volatility cannot be fully eliminated.
How Does Phoenix's Risk Control Differ from Centralized Exchanges?
Phoenix and centralized exchanges differ fundamentally in risk management logic.
Centralized platforms rely on internal servers for order, liquidation, and risk processing, while Phoenix's risk logic runs on-chain.
Key differences:
| Dimension |
Phoenix |
Centralized Exchange |
| Risk System |
On-chain execution |
Platform server |
| Data Transparency |
Publicly verifiable |
Internal |
| Asset Custody |
User self-custody |
Platform custody |
| Liquidation Records |
On-chain public |
Typically hidden |
| Market Control |
Protocol rules enforced |
Platform centralized |
Phoenix prioritizes transparency and decentralization but is more dependent on underlying network performance and smart contract security.
Summary
Phoenix manages on-chain perpetual futures risk through its margin model, risk engine, funding rate, Oracle system, and liquidation mechanism. Given the leverage and constant volatility in perpetual futures, a robust risk control system is essential for protocol stability.
Compared to traditional centralized exchanges, Phoenix's risk logic runs on-chain, allowing all market status, position data, and liquidation records to be publicly verified. This design enhances transparency but also increases reliance on blockchain performance and Oracle data reliability.
FAQs
When does Phoenix trigger liquidation?
When account equity falls below the maintenance margin requirement, the system may trigger liquidation.
Is Phoenix's risk system on-chain?
Yes. All risk checks, position updates, and liquidation logic run on-chain.
Does the funding rate affect trading costs?
Yes. It impacts the holding costs for both long and short positions and helps maintain market price balance.
Why is the Oracle important for Phoenix?
The Oracle provides reference market prices for risk assessment and liquidation decisions.
Can Phoenix completely eliminate market risk?
No. Risk control mechanisms reduce risk but cannot fully prevent losses from extreme market events.
How is Phoenix's risk control different from centralized exchanges?
Phoenix emphasizes on-chain transparency and automated rule execution, whereas centralized exchanges typically manage risk systems internally.
