-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for non-18 decimals in custom fee token #24
Merged
Merged
Changes from 17 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
276a9de
Add supoprt for custom number of decimals used for fee token
gvladika 4f60f8c
Add decimals param to test-node.bash
gvladika ddc75ce
Adjust values
gvladika 2148cc5
Approve correct amount
gvladika ab17b3c
Merge branch 'master' into non18-decimal-token
gvladika 9e3dc84
Move token deployment to separate function
gvladika 027c69a
Merge branch 'decouple-contracts' into non18-decimal-token
gvladika 83476e2
Adjust token amounts
gvladika cc2ead1
Mint all to deployer
gvladika 5789086
Fix amounts
gvladika 1f88575
Merge branch 'decouple-contracts' into non18-decimal-token
gvladika 917fcae
Merge branch 'release' into non18-decimal-token
gvladika fb09a19
Merge branch 'release' into non18-decimal-token
gvladika 06fe680
Merge branch 'release' into non18-decimal-token
gvladika e8e187b
Fix funding the L3 accounts in case of fee token
gvladika a964b2d
Merge branch 'release' into non18-decimal-token
gzeoneth ba9f2f9
Merge branch 'release' into non18-decimal-token
tsahee 3af86a0
Properly check that native bridging was successful
gvladika File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.gte(depositAmount)?
gte(0) will not work for 2nd transfer, gte(depositAmount) will at least work if 2nd transfer is larger than previous balance which seems reasonable.
there are probably better ways
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case when fee token has non-18 decimals, depositAmount is not equal to the amount minted on L2 (we do inflation/deflation to match 18-decimals denomination for native currency). I've improved this check to properly wait for expected amount to be minted on L2 3af86a0