fix:M03 Move to using address.sendValue over the transfer pattern when sending eth #139
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
…n sending eth Signed-off-by: chrismaree <christopher.maree@gmail.com>
nicholaspai
added
the
OZ Audit - March
nicholaspai
approved these changes
Apr 13, 2022
This was referenced May 3, 2022
Merged
This was referenced May 17, 2022
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.
OZ points out that using the
transferpattern, introduced in PR: #90 is not optimal as if the target of the eth needs more than 2300 gas the tx will revert. This PR changes this to use theAddress.sendValuefunction, which uses the.callpattern under the hood to address this.