-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Wrong ENS contract address for testnets #509
Comments
FML, thank you for catching this. Will updated ASAP and get live in the AM. |
|
@Deozaan I believe the problem is you selected the changed the node while on the ENS tab, for example you had the mainnet node and went to ENS tab then changed to Rinkeyby. |
it show an error message now when you change the node |
Yes, that does sound like what I did. I guess I was expecting a more AJAX-y interface where changing things in the middle of the process would update everything appropriately behind the scenes.
And yes, I realize that now. :)
Thank you very much. I appreciate the time and effort you and @tayvano put into this. |
Consider this low-priority since it has to do with testnet.
I wanted to test ENS on a testnet (Rinkeby) so I used MEW to check if a domain was available. It told me it was available and allowed me to place a bid. After confirmation I realized my ETH got sent to the ENS address for mainnet, which is not associated with the ENS contract on the testnet. I was careless and sent a large amount of ETH because I was expecting to get most of the ETH back once the auction closed.
No real loss to me since the test ETH isn't worth anything, but maybe MEW shouldn't allow the ENS tab to work if a testnet is selected from the dropdown menu. Or the contract address should be updated to use the correct testnet addresses.
Mainnet: 0x314159265dd8dbb310642f98f50c066173c1259b
Rinkeby: 0xe7410170f87102df0055eb195163a03b7f2bff4a
Ropsten: 0x112234455c3a32fd11230c42e7bccd4a84e02010
The text was updated successfully, but these errors were encountered: