fix: set ZETA token address from constructor argument #151
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.
Reverting back to setting ZETA token address explicitly through a constructor argument, instead of reading it from the connector, because connector on Ethereum and BNB has ZETA token address stored in
zetaToken, and connector on ZetaChain has ZETA token address stored inWZETA(zeta-chain/protocol-contracts#158) Thus, we can't use the same constructor to read ZETA token address, so we have to revert back to passing it explicitly.Tested messaging to and from ZetaChain, it works.
https://zetachain-athens-3.blockscout.com/address/0xf401596Ff974F379cE85F727D2F2dc441a319e06?tab=logs
https://sepolia.etherscan.io/address/0x08b6C291B45949A2ab646C1969493913F1771DFc#events