Troubleshooting technical issues is much easier when both the user and support agent practice clear communication. For this reason, we have provided the template below for you to fill out with information about your issue. Please provide as much detail as possible so we can most efficiently resolve your problem.
Delete the any text above the line separator below before posting
Description of the issue:
How can this issue be reproduced?
- Brave is displaying outdated results for ENS resolution
- Try to send ETH or BAT to “migrated.eth” in the Brave desktop crypto wallet, and it will claim that name doesn’t exist
Expected result: The name “migrated.eth” should resolve to 0x0904Dac3347eA47d208F3Fd67402D039a3b99859
Brave Version( check
About Brave): Latest, just downloaded it
The problem is that Brave is still using the old ENS registry contract; as a result, it is showing outdated results. We recently had to update the contract to fix a bug. Brave needs to update its code to point to the new ENS registry. All this requires is simply changes the ENS registry contract address in the code to the new one.
Here is more info:
Please let me know at firstname.lastname@example.org when this has been fixed (and it should be fixed ASAP).