Post audit fixes for native token decimals feature #102
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
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.
When chain uses custom fee token which has non-18 decimals, that means that amount of locked funds on the parent chain is different than the amount of funds that will be minted on the child chain. This commit updates RollupCreator and DeployHelper (those contracts contain logic to deploy create2 deterministic factories to child chain via retrybles) so that amount of funds that needs to be locked is properly calculated.
Natspecs have been updated to make the denomination of retryable parameters more clear.
Also e2e tests have been refactored and improved to include more checks.