Fix SecurityPool fee residue and REP bootstrap mint flow#498
Merged
Conversation
- Preserve fee and fee-index remainders across collateral updates - Add fork migration coverage for repeated public collateral updates - Refresh mainnet deployment addresses for SecurityPool components
…esidue-fix # Conflicts: # docs/mainnet-deployment-addresses.json
- Distribute leftover whole wei at fee period end - Update regression tests for fee settlement and stale-price errors - Refresh mainnet deployment addresses
- clear stale fee remainders on allowance changes and zero-allowance gaps - reconcile collateral after fee redemption to preserve pool balance - add regression tests for handoff and zero-allowance accrual
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ReputationToken.mintand move simulation bootstrap supply syncing to happen after minting.Testing