fix: zaps locking [NAY-1] #157
Merged
Conversation
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
Merged
amarinkovic
force-pushed
the
NAY-1_lock_zaps
branch
from
449ca12 to
0fd9e46
Compare
amarinkovic
force-pushed
the
NAY-1_lock_zaps
branch
from
0fd9e46 to
4fd42fc
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.
While the new functions
zapStakeandzapOrdermake use of thenotLocked-modifier, they are not properly listed inthe
LibAdmin._lockAllFundTransferFunctions(and_unlockAllFundTransferFunctions) functions and can therefore not be locked viaAdminFacet.lockAllFundTransferFunctions.