-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENS Registry migration #237
Comments
thank you for contribution. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 0.045 ETH (11.92 USD @ $264.8/ETH) attached to it.
|
I made the change but I will wait for the return of @angerborn he has the right to the bounty. |
Thanks for the quick response! It mostly have been done by @angerborn , but I will handle this. to make everyone get the reward for open-source coding Thank you all! @angerborn,'s PR deletes testnetwork addresses. p.s. |
Thanks @skywinder, about #239 I think is bug in go-ethereum, I wait for update release for better verification. |
⚡️ A tip worth 0.04000 ETH (10.56 USD @ $264.11/ETH) has been granted to @aranhaagency for this issue from @skywinder. ⚡️ Nice work @aranhaagency! Your tip has automatically been deposited in the ETH address we have on file.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This Bounty has been completed. Additional Tips for this Bounty:
|
Oh, mentioned, that the second 10$ tip sent to @aranhaagency too. I supposed to send! @angerborn as the kind of respect his Pr You received double bounty by 0.04 eth. Can you kindly send it to @angerborn ? 😅 |
Hello, again @angerborn & @aranhaagency! Thanks for the contribution, hope you've like and use our library! :) Cheers! |
Due to a bug in the old contract (the ones used by this library at the moment), the ens registries are being migrated.
See:
https://medium.com/the-ethereum-name-service/ens-registry-migration-bug-fix-new-features-64379193a5a
And:
https://docs.ens.domains/ens-migration/guide-for-dapp-developers
Since this was deployed on feb 3rd, any resolved addresses using the old registry may return old data.
The text was updated successfully, but these errors were encountered: