@fei-protocol/fuse-flywheel
v0.0.0
Published
Fuse specific compatibility modules for Flywheel V2
Downloads
2
Keywords
Readme
Fuse Flywheel
The Fuse-specific compatibility modules to add flywheel v2 to the existing Fuse comptroller.
The FuseFlywheelCore
is just a wrapper around FlywheelCore with all transfer hooks and identifiers overloaded for backward compatibility.
Adding Flywheel to Fuse
- Deploy
FuseFlywheelCore
and configure with desiredrewardToken
,rewards
andbooster
modules. If the rewards and booster need to reference core, set to 0 initially on core. After deploying, use the setter functions to re-point core to them. - Add the flywheel by calling
comptroller._addRewardsDistributor(flywheelCore)
on the Fuse pool Comptroller. - Ensure that the desired markets are added on the flywheel core by calling
strategy.addStrategyForRewards(market)
- Make sure the rewards module is configured and seeded with
rewardToken
if needed.
Using the optional plugin rewards modules
Plugin rewards modules pass incentives through from Fuse strategies or other sources back to depositors via flywheel. A great example is the Convex Fuse Pool
If the rewards are sent straight to depositors, for example by merkle drop, use the CERC20RewardsDelegate to approve the flywheelRewards
module for each rewardToken
If the rewards come from an ERC-4626 plugin strategy, use the CERC20PluginRewardsDelegate to approve the flywheelRewards
module for each rewardToken
. This should be upgraded from a CERC20PluginDelegate.
Because approvals are cumulative and remain active on the proxy until used, this process can be repeated by applying iterative _becomeImplementation
calls on the same RewardsDelegate to add support for multiple flywheels and reward tokens.
Powered by forge-template