feat: axelar support #18
Merged
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
|
@oed is this one ready for review/merge? |
|
@sanderpick yes! |
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.
This PR adds support for Axelars Interchain Token Service to our ERC20 token. Our ERC20 is kept upgradable such that we can add/remove bridges over time (e.g. we are not locked into axelar).
The deploy script has been set up to connect the token to the axelar bridge on deploytime.
Deployed a test version of the token on Filecoin so far, which can be viewed on Axelars bridge app.
Waiting for gasprices on Ethereum to lower a bit before I deploy there, after which the bridging can be tested.
In addition to the bridge functionality I noticed that the ERC20 was importing
PausableUpgradeable, but wasn't actually overriding any of the ERC20 methods to make them respect pausing. Fixed this.