⚡
Boosted Leverage
Alpies owners can stake their NFTs to access higher leverage on the selected leveraged yield farming pools. If you own Dreamer Alpies, you will need to bridge your NFTs over to the BNBChain before you can stake them. You can read how to bridge your NFTs here.
Liquidation thresholds will be adjusted upwards to accommodate higher leverage for users who have Alpies staked. This means that, as an added benefit, users who stake Alpies will be less likely to get liquidated even if they don't use higher leverage.
- 1 Staked Alpie NFT will boost max leverage on an unlimited number of positions (for that wallet)
- You may unstake your Alpies at any time (but mind the leverage, more info in the warning below)
⚠️ When you unstake your Alpie NFT, the liquidation threshold will be reverted to the standard value, which mean your opened positions could be at risk for liquidation. Check the standard values here. Please make sure you review and manage your positions (lower leverage, add collateral, partial close, etc.) before unstaking.
You will have access to higher leverage (3x → 4.5x) on the following pools:
Pool | Max. Boosted Leverage | Liquidation Threshold |
|---|---|---|
BNB-USDT | 4.5x | 85% |
BNB-BUSD | 4.5x | 85% |
BTCB-BUSD | 4.5x | 85% |
ETH-USDC | 4.5x | 85% |
ETH-BNB | 4.5x | 85% |
BTCB-BNB | 4.5x | 85% |
CAKE-BNB | 4.5x | 85% |
CAKE-BUSD | 4.5x | 85% |
CAKE-USDT | 4.5x | 85% |
Pool | Max. Boosted Leverage | Liquidation Threshold |
|---|---|---|
BNB-USDT | 4.5x | 85% |
BNB-BUSD | 4.5x | 85% |
BTCB-USDT | 4.5x | 85% |
BNB-USDC | 4.5x | 85% |
ETH-USDT | 4.5x | 85% |
Pool | Max. Boosted Leverage | Liquidation Threshold |
|---|---|---|
BTCB-USDT | 4.5x | 85% |
ETH-USDT | 4.5x | 85% |
The list might be adjusted from time to time to to ensure these pools can still support higher leverage. E.g., some pools might be taken off the list if their liquidity drops too low.
As the boosted leveraged introduces a different set of liquidation thresholds (kill factor) when users stake Alpies, we recommend liquidators to query the kill factor from
workerConfig.killFactor(address worker, uint256 debt, address positionOwner) . workerConfig.killFactor(address worker, uint256 debt) will continue to work, but it will only return worker’s default kill factor.