fix: moved message fee from int64 to string and uint256 #4399
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
johnsaigle
reviewed
Jun 11, 2025
johnsaigle
approved these changes
Jun 16, 2025
bruce-riley
approved these changes
Jun 18, 2025
bruce-riley
pushed a commit
to wormholelabs-xyz/wormhole
that referenced
this pull request
Jun 24, 2025
…ndation#4399) * fix: moved message fee from int64 to string and uint256 * negative check
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.
uint256and notint64, or else we'll get antoUint256_outOfBoundserror when submitting the VAA to the core bridge