fix: fix bug which breaks rights conservation and offer safety guarantees #3858
Conversation
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
katelynsills
force-pushed
the
3848-zcfMint-rights-conservation
branch
from
1e99b42 to
d9eed05
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR rewrites
zcfMint.mintGainsandzcfMint.burnLossesso that neither use staged allocations and neither use the typicalreallocatepath. Instead, the code is simplified such that the updated allocations are calculated, then a special reallocate only for zcfMint methods (reallocateForZCFMint) is called.reallocateInternalis deleted and its contents moved intoreallocateproper.Closes #3848