-
Notifications
You must be signed in to change notification settings - Fork 215
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: fusdc recovery paths (#10659)
closes: #10624 ## Description - handles potential failure in `zoeTools.localTransfer` during FUSDC Advance flow by returning funds to LP - documents why it's OK to fail during a potential `zoeTools.withdrawToSeat` failure in `.disperse()` - removes `zcf.shutdownWithFailure()` in catch blocks around `zcf.atomicRearrange`. This is only necessary when commits are not atomic. ### Security Considerations - Improves handling of Payments during unexpected, but potential, failure paths. - Ensures FUSDC contract will not shutdown during unexpected failures. ### Scaling Considerations N/A ### Documentation Considerations N/A ### Testing Considerations Includes a unit test that ensures the advancer performs the expected calls after `zoeTools.localTransfer` fails. Does not include unit tests for the new liquidity pool `borrower.returnToPool` as those have been deemed too expensive. The risk here seems low as the call is effectively passed through to `repayer.repay`, which has tests, modulo the KWR arrangement which is protected by the interface guard. ### Upgrade Considerations None, FUSDC is unreleased.
- Loading branch information
Showing
5 changed files
with
306 additions
and
106 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.