chore: upgrade to ENSv2 (Universal Resolver)#2692
Conversation
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Dhaiwat Pandya.
|
|
We require contributors to sign our Contributor License Agreement. In order for us to review and merge your code, please sign one of the linked documents below to get yourself added. If you're an independent Individual please sign this form: https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=1353a816-a9c1-47ba-847e-ec79f0f23d31&env=na3&acct=6e152afc-6284-44af-a4c1-d8ef291db402&v=2. If you're with a company (corporate) please sign this form: https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=2b5fe8ba-51d4-4980-b4ee-605d66e675d4&env=na3&acct=6e152afc-6284-44af-a4c1-d8ef291db402&v=2. To agree to the CLA license, please fill out one of the attached forms. |
Hey! I'm Dhaiwat from the DevRel team at ENS Labs. We're working on getting active repos and libraries across the ecosystem ready for ENSv2.
Summary
Upgrades this repo to be ENSv2-ready by routing ENS resolution through the Universal Resolver (
0xeeeeeeee14d718c2b47d9923deab1335e144eeee) instead of the legacy ENS Registry.Changes
viem^2.29.0→^2.48.11inpackages/arb-token-bridge-ui/package.jsonWhy
The current path returns stale results for names managed by the new Universal Resolver. For example,
ur.integration-tests.ethshould resolve to0x2222222222222222222222222222222222222222; legacy resolution returns incorrect values.More details: https://docs.ens.domains/web/ensv2-readiness
Verification
ur.integration-tests.eth→0x2222222222222222222222222222222222222222