fix(axelarnet)!: stricter validation in call contract ValidateBasic #1969
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
milapsheth
requested review from
cgorenflo,
jcs47,
haiyizxx,
fish-sammy and
cjcobb23
as code owners
cjcobb23
approved these changes
Jul 19, 2023
fish-sammy
approved these changes
Jul 19, 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.
Description
Addresses an audit comment.
Use
ValidateStringfor consistency when validating contract address forCallContractrequest inValidateBasic. While the failure would have been caught in msg_server later, this approach is more consistent with our validation.AXE-1226
Todos
Steps to Test
Expected Behaviour
Other Notes