(Fix) #1587 - Ens mislabeled as eth#1601
Conversation
|
CLA Assistant Lite All Contributors have signed the CLA. |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
|
Travis automatic deployment: |
|
Travis automatic deployment: |
| } | ||
|
|
||
| export const isENSContract = (contractAddress: string): boolean => { | ||
| const ENS_TOKEN_CONTRACT = '0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85' |
There was a problem hiding this comment.
For which network is this ENS contract address?
There was a problem hiding this comment.
For both rinkeby and mainnet, not sure if for the deployed ENS contract for other networks have this issue with the symbol() method too. In any case would be better to have support for ewc/xDai in this method, do you have those addresses for adding them?
There was a problem hiding this comment.
For xDai I don't think we have it yet.
For EWC and Volta I think it should be the ETHBaseRegister ones:
https://energyweb.atlassian.net/wiki/spaces/EWF/pages/555745281/Using+ENS
There was a problem hiding this comment.
I'm thinking on adding the addresses on the config file what do you think?
There was a problem hiding this comment.
Personally, I prefer the approach I took in https://github.com/gnosis/safe-react/blob/1587-ens-mislabeled-as-eth/src/logic/collectibles/utils/index.ts#L16-L19
It's so specific that populating the config files with that info will make them unnecessary complex in the future.
There was a problem hiding this comment.
That makes sense, will do that 👍
There was a problem hiding this comment.
I added ens addresses for both volta and ewc too 👍
|
Travis automatic deployment: |
|
Travis automatic deployment: |
|
I've checked this 2 safes that already have ENS tokens for incoming/outgoing tx's Safes: |
Closes #1587 by:
symbol()methodsymbol()so I added it