Increase fault tolerance of BridgeReferralFees hooks #155
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.
Description
We have to absolutely minimize any possible reverts through execution of
BridgeReferralFees.The following cases have been identified and mitigated:
bridgedAmount - feeAmountunderflow by enforcingMAX_FEE_BASIS_POINTS < 1e4viauint8typefeeAmountcalculation to handle potential overflow caseThe following cases have been identified, but not deemed worth addressing:
tokenargument leading to failingbalanceOfcallstokenthat could violate accounting invariants, making underflow onbridgedAmountcalculation possibleAdditionally, we are removing footguns for the developer by replacing the
bytes32 coderepresentation with the simplerstring code.Asks