feat: locked yvUSD cooldown strategy and pending redemptions refactor - #1
johnnyonline wants to merge 12 commits into
Conversation
|
I was initially concerned that receiving the collateral and starting its cooldown in separate transactions could leave the accounting inconsistent between calls like an additional call may disrupt the accounting. Discussed with @johnnyonline , and both calls are executed atomically through the multisig, so this is not an issue. LGTM |
Fixed that as well as Schlag's comment about |
| uint256 _baseAssets = COLLATERAL.convertToAssets(COLLATERAL.balanceOf(address(this))) + queuedBaseAssets; | ||
| if (_baseAssets > 0) _pending += _baseAssets * FXBASE.nav() / _NAV_TO_ASSET_SCALE; |
There was a problem hiding this comment.
queued assets are still earning yield ?
There was a problem hiding this comment.
Should be. It only stops earning the gauge rewards fxSAVE compounds
| uint256 _shares = COLLATERAL.maxRedeem(address(this)); | ||
| require(_shares > 0, "!claim"); |
There was a problem hiding this comment.
Do we really need this? Seems unnecessary
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Towards locked yvUSD market. Market oracle PR @ flexmeow/flex-contracts#24