ENSv2 readiness guide #486
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Fix grammar: "just update" → "just updating" - Replace "according" with "appropriate" for better clarity - Fix typo: "will introduction" → "will introduce" - Fix grammar: "an integrations" → "an integration" - Fix localhost URL to use relative path 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- Add context about ENSv2 and Namechain as primary L2 - Convert formal tone to conversational "you" style throughout - Break complex sentences into shorter, punchier ones - Change passive voice to active voice - Rename generic "Test" headers to descriptive ones - Clarify that supported libraries handle everything automatically - Position technical sections as educational rather than required steps - Fix CCIP Read link 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- Explain importance of detecting DNS names alongside .eth names - Show common mistake: regex that only matches .eth domains - Provide correct regex pattern for matching all valid domains - Add info callout recommending library use over custom regex - Include real examples: ensfairy.xyz and ses.fkey.id - Link to DNS integration documentation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Deploying ens-docs with
|
| Latest commit: |
d955ae9
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1239feea.docs-bao.pages.dev |
| Branch Preview URL: | https://ensv2-readyness.docs-bao.pages.dev |
gskril
reviewed
Nov 2, 2025
|
|
||
| ## Universal Resolver | ||
|
|
||
| Even though ENSv2 supports multi-chain, all resolution starts on Ethereum Mainnet. ENS deployed a [new Universal Resolver](https://eth.blockscout.com/address/0xeEeEEEeE14D718C2B47D9923Deab1335E144EeEe) that acts as the canonical entry point. This resolver can be updated in the future if needed. |
Member
There was a problem hiding this comment.
Suggested change
| Even though ENSv2 supports multi-chain, all resolution starts on Ethereum Mainnet. ENS deployed a [new Universal Resolver](https://eth.blockscout.com/address/0xeEeEEEeE14D718C2B47D9923Deab1335E144EeEe) that acts as the canonical entry point. This resolver can be updated in the future if needed. |
The reason the 0xeEeEE... version is a proxy contract controlled by the DAO is to hopefully never require an update again, so we probably shouldn't say this.
Member
Author
There was a problem hiding this comment.
My intention was to explain exactly this: That this is a proxy contract that will be updated (not redeployed) for ENSv2. Maybe this can be more explicit like:
"ENS deployed a new Universal Resolver that acts as the canonical entry point. This is a proxy contract, so this address won't change in the future if the implementation is changed."
|
|
||
| Even though ENSv2 supports multi-chain, all resolution starts on Ethereum Mainnet. ENS deployed a [new Universal Resolver](https://eth.blockscout.com/address/0xeEeEEEeE14D718C2B47D9923Deab1335E144EeEe) that acts as the canonical entry point. This resolver can be updated in the future if needed. | ||
|
|
||
| Your application needs to use this new Universal Resolver. As mentioned above, updating to the latest version of your library should handle this automatically. |
Member
There was a problem hiding this comment.
Suggested change
| Your application needs to use this new Universal Resolver. As mentioned above, updating to the latest version of your library should handle this automatically. | |
| As mentioned above, updating to the latest version of your web3 library should handle this automatically. |
Member
Author
There was a problem hiding this comment.
I think it is important to re-emphasize that they need to update to the latest universal resolver.
|
|
||
| Your application needs to use this new Universal Resolver. As mentioned above, updating to the latest version of your library should handle this automatically. | ||
|
|
||
| Learn more about the [Universal Resolver here](/resolvers/universal) and about the [resolution process in general here](/resolution). |
Member
There was a problem hiding this comment.
Suggested change
| Learn more about the [Universal Resolver here](/resolvers/universal) and about the [resolution process in general here](/resolution). |
Explained above
Co-authored-by: Greg <35093316+gskril@users.noreply.github.com>
Co-authored-by: Greg <35093316+gskril@users.noreply.github.com>
Co-authored-by: Greg <35093316+gskril@users.noreply.github.com>
Co-authored-by: Greg <35093316+gskril@users.noreply.github.com>
Co-authored-by: Greg <35093316+gskril@users.noreply.github.com>
Co-authored-by: Greg <35093316+gskril@users.noreply.github.com>
schmidsi
commented
Nov 3, 2025
| - ethers.js: Not published yet. [Work in progress on v6.16.0](https://github.com/ethers-io/ethers.js/tree/wip-v6.16.0-ens) | ||
| - web3.js: Deprecated | ||
|
|
||
| If you're using a supported library, it should handle everything automatically. The sections below explain what's happening under the hood and how to test that your integration is working correctly: |
Member
Author
There was a problem hiding this comment.
Make it more clear that usually people don't need to read further
schmidsi
commented
Nov 3, 2025
|
|
||
| ENS supports importing DNS names into ENS, allowing traditional domain names to work alongside .eth names. It's important that your application correctly also detects DNS names to avoid false positives. | ||
|
|
||
| ### Common Mistake: Only Matching .eth |
Member
Author
There was a problem hiding this comment.
Add some examples: emoji, ...
gskril
reviewed
Nov 3, 2025
| - `.eth` names like `vitalik.eth` | ||
| - DNS names like `ensfairy.xyz` | ||
| - Subdomains like `ses.fkey.id` | ||
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First stab at an ENSv2 readiness guide: