Closed fadeev closed 3 months ago
In the connector on connected EVM chains ZETA token address is stored as zetaToken:
zetaToken
https://github.com/zeta-chain/protocol-contracts/blob/d21bce58271993ca9ad32b295a44b23d06ee5ff9/contracts/evm/ZetaConnector.base.sol#L16
On ZetaChain's connector it's stored as WZETA:
WZETA
https://github.com/zeta-chain/protocol-contracts/blob/d21bce58271993ca9ad32b295a44b23d06ee5ff9/contracts/zevm/ZetaConnectorZEVM.sol#L65
I propose we rename WZETA to zetaToken, so that it becomes possible to deploy messaging contracts that read ZETA token address from the connector instead of passing it explicitly to the constructor.
Will be set the same for new contracts
this can be closed, it is named correctly on v2 zetaconnector
In the connector on connected EVM chains ZETA token address is stored as
zetaToken
:https://github.com/zeta-chain/protocol-contracts/blob/d21bce58271993ca9ad32b295a44b23d06ee5ff9/contracts/evm/ZetaConnector.base.sol#L16
On ZetaChain's connector it's stored as
WZETA
:https://github.com/zeta-chain/protocol-contracts/blob/d21bce58271993ca9ad32b295a44b23d06ee5ff9/contracts/zevm/ZetaConnectorZEVM.sol#L65
I propose we rename
WZETA
tozetaToken
, so that it becomes possible to deploy messaging contracts that read ZETA token address from the connector instead of passing it explicitly to the constructor.