Read before using
Fee-backed leveraged positions can lose their full margin.
The reserve cap limits how much of a coin vault can be exposed; it cannot make leverage or a volatile memecoin safe.
Deployed margin can go to zero
A routed position can be liquidated. The 2× cap reduces risk, but the deployed 25% vault slice can still be lost.
Router and venue risk
Imperial routes to an underlying venue whose liquidity, funding, liquidation and availability govern the open position.
Reserve is not a guarantee
At least 75% stays outside the position by policy, but custody, conversion and smart-contract failures remain possible.
Vault strategy guardrails
These limits are checked again immediately before every routed order. This is an unaudited mainnet beta.
| Control | Purpose | Initial value |
|---|---|---|
| Maximum leverage | Limit directional exposure | 2× |
| Maximum vault deployment | Keep most capital outside leverage | 25% |
| Maximum position collateral | Limit unaudited beta exposure | $25 |
| Minimum reserve | Preserve liquidity and drawdown capacity | 75% |
| Automatic exit | Bound position duration and target loss | ±10% / 24h |
| Profit allocation | Queue burn, buyback and liquidity settlement | 40 / 30 / 30 |
| Route allowlist | Reject prefunded or stale external routes | Jupiter / Phoenix / GMTrade |
No valid wallet-scoped JWT and fresh preflight, no order.The integration calls Imperial's official API, rejects clamped or prefunded routes and never retries an ambiguous submission until reconciliation proves its outcome.