This repository contains the implementation of the OnlyBoost white paper, focusing on smart contracts for the CRV Liquid Locker. These contracts optimize the fund distribution between Stake DAO and Convex to maximize the boost.
The locker contract serves as a repository for both the voting power and boosting power inherent to the underlying protocol. Acting as a proxy for the end user, it retains any deposits with the goal of enhancing their returns.
Serving as the central access point to the locker, the strategy contract establishes a bridge for interaction. This contract facilitates the movement of funds between the users and the locker, undertakes the task of harvesting rewards, and ensures their appropriate distribution.
Additionally, third-party contracts, referred to as plugin contracts, can also interface with the strategy contract for various functions, including voting.
The optimizer contract's responsibility is to determine the most advantageous allocation of deposits between Convex and Stake DAO. By referencing the Convex Minimal Proxy Factory, it identifies the relevant Convex addresses; however, if none are found, all allocations are directed towards Stake DAO
For each Convex pool, there's a dedicated minimal proxy that is deployed through a factory system. Given that any participant can stake a claim for a user on Convex, this architecture not only simplifies the reward distribution process but also results in a reduction of gas costs.
graph TD
Vault -->|Mint| LiquidityGauge
Vault -->|Deposit & Withdraw| Strategy
Optimizer <.->|GetOptimalDepositAllocation| Strategy
subgraph OnlyBoost[ ]
Strategy -->|Deposit & Withdraw| Locker
Strategy -->|Deposit & Withdraw| ConvexProxyPID_1
Strategy -->|Deposit & Withdraw| ConvexProxyPID_2
Strategy -->|Deposit & Withdraw| ConvexProxy...
end
ConvexProxyPID_1 -->|delegatecall| ConvexPIDImplementation
ConvexProxyPID_2 -->|delegatecall| ConvexPIDImplementation
ConvexProxy... -->|delegatecall| ConvexPIDImplementation
Each Pool ID is associated with its own contract. When harvesting occurs, the strategy claims from both the corresponding fallback and the locker, then proceeds to distribute the rewards within the liquidity gauge. (RewardDistributor)
graph TD
Vault -->|Deposit & Withdraw| Strategy
Vault -->|Mint| LiquidityGauge
Optimizer <.->|GetFallbackAddress| Strategy
subgraph OnlyBoost[ ]
Strategy -->|Harvest| Locker
Strategy -->|Harvest| ConvexProxyPID_1
end
ConvexProxyPID_1 -->|getReward| Convex
Strategy -->|deposit_reward_token| LiquidityGauge