Add Gearbox cp0xLRT Pool to ETH Higher Risk Vault
Submission Date : 26 August 2025
Author : @cp0x
Summary
This proposal suggests adding the Gearbox cp0xLRT wstETH v3 pool as a new ARK strategy within the Summer.fi ETH Higher Risk Vault (Ethereum Mainnet).
The Gearbox pool supports cp0xLRT, a liquid restaking token backed by wstETH, and currently offers one of the highest yields among Gearbox vaults.
- Current Supply APY: 7.21%
- Pool Status: Among the top Gearbox vaults by size and utilization with 301 wstETH supply
- Mellow cp0x LRT Conservative Vault with 1674 wstETH TVL
https://app.mellow.finance/vaults/ethereum-cp0xlrt
Motivation
- High Yield Opportunity: The cp0xLRT pool currently provides a 6.34% APY (more than current ETH higher risk vaults) to suppliers, making it one of the top-performing Gearbox lending markets. Integrating it strengthens Summer.fi’s higher-risk strategies with sustainable yield.
- Diversification: Adding cp0xLRT, cp0xLRT (→ wstETH) expands the range of supported collaterals in the ETH Higher-Risk Vault, reducing dependency on a limited set of assets.
- Liquidity Growth: Strengthening the connection between Summer.fi and Gearbox benefits both ecosystems and creates new opportunities for users.
Specifications
- Vault: Summer.fi ETH Higher Risk (Ethereum Mainnet)
- New ARK: Gearbox cp0xLRT Lending Pool
- Supported Asset: cp0xLRT, cp0xLRT → wstETH
- Format: ERC-4626 lending pool, fully compatible with Lazy Summer architecture
- Network: Ethereum Mainnet
Risk & Integration
- Block Analitica Review: Will define caps, exposure thresholds, cooldowns, and other safety parameters.
- Protocol Security: Gearbox has operated for over 4 years without incidents, audited by ChainSecurity, ABDK, Decurity, and MixBytes.
- Collateral Security: cp0xLRT is a liquid restaking token (LRT) backed by wstETH, leveraging the security and liquidity of Ethereum staking while enabling restaking yield.
- Seamless Integration: The ERC-4626 design of the Gearbox pool ensures smooth integration with Lazy Summer vaults.
Next Steps
- Collect feedback from @Recognized_Delegates.
- Finalize parameters with @BlockAnalitica.
- Proceed to on-chain vote if no blocking issues arise.