Document risk of lost funds if receiver lacks fallback #73
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
📃CI ReportCompiling 141 files with 0.8.19
For a full HTML report run: |
Document risk of lost funds if receiver lacks fallback
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
proletesseract
approved these changes
Dec 12, 2023
wcgcyx
approved these changes
Dec 12, 2023
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 adds natspec comments highlighting the risk raised in issue #59, and also tracked through SMR-2116
In addition, checks have been implemented on the front-end layer to mitigate this risk, as detailed in SMR-2112.