Evm reverse resolution #157

jefflau · 2023-08-24T08:08:27Z

Renamed the branch so it isn't ensip-16. Old comments/PR here: #132

…-compatible chains

moldy530 · 2023-10-10T20:36:45Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+### Resolving Primary ENS Names by a dapp
+
+* If a dapp has a connected user it SHOULD first check the chainId of the user
+* If the chainId is not 1, it SHOULD then construct the ENS name [address].[evmChainCoinType].reverse to obtain the primary ENS name of the user. If none is found, it SHOULD assume that the user has no primary ENS name set


this is cool and kinda what I had in mind but I like the proposal of having L2 registrars in the mix, still grokking but 👍

Appreciate any and all feedback!

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

makoto · 2024-02-05T17:19:25Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+1) Sign a message to set a default record
+2) call `setName()` on the default registrar on L1
+
+Possibility: Allowing L1 Primary ENS names to also use `default.addr`. This could be incorporated into the public resolver's `name()` function.


Should this be default.reverse ?

Arachnid

You should probably explicitly include the directions from ENSIP 11 here on how to create a coin type from a chain ID.

Perhaps we should have some syntax for this? Most primary names are going to be for chains that have chain IDs as coin types, and it seems weird that they would all have hugely long decimal identifiers instead of the shorter ones a chain ID would offer. The extended DNS resolver uses the syntax e<chain id> as a shorthand; perhaps we can do something like that here too?

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

cloudflare-workers-and-pages · 2024-03-20T15:24:25Z

Deploying ens-docs with Cloudflare Pages

Latest commit:	`5c45407`
Status:	✅ Deploy successful!
Preview URL:	https://8f2d5b92.docs-bao.pages.dev
Branch Preview URL:	https://evm-reverse-resolution.docs-bao.pages.dev

View logs

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

Arachnid · 2024-03-25T15:44:44Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+
+To determine the avatar URI for a specific EVM chain address, the client MUST reverse-resolve the address by querying the ENS registry on Ethereum for the resolver of `<address>.<coinType>.reverse`, where `<address>` is the lowercase hex-encoded Ethereum address, without leading '0x'. Then, the client calls `.text(namehash('<address>.<coinType>.reverse'), 'avatar')` to retrieve the avatar URI for the address.
+
+If a resolver is returned for the reverse record, but calling `text` causes a revert or returns an empty string, the client MUST call `.name(namehash('<address>.<coinType>.reverse'))`. If this method returns a valid ENS name, the client MUST:


The way this is worded is overly specific, and implies a method that won't work for a default reverse resolver.

Yeah actually this doesn't really make sense, because there are no custom resolvers on L2 reverse registrars anyway

Also, the examples should be written descriptively - describing what the client does in the example scenario. SHOULd and MUST etc are for the specification itself.

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

Co-authored-by: Nick Johnson <arachnid@notdot.net>

Arachnid

This also needs updating to reflect the decision to hex-encode chain IDs.

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

Arachnid · 2024-04-04T07:50:49Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+
+To determine the avatar URI for a specific EVM chain address, the client MUST reverse-resolve the address by querying the ENS registry on Ethereum for the resolver of `<address>.<coinType>.reverse`, where `<address>` is the lowercase hex-encoded Ethereum address, without leading '0x'. Then, the client calls `.text(namehash('<address>.<coinType>.reverse'), 'avatar')` to retrieve the avatar URI for the address.
+
+If a resolver is returned for the reverse record, but calling `text` causes a revert or returns an empty string, the client MUST call `.name(namehash('<address>.<coinType>.reverse'))`. If this method returns a valid ENS name, the client MUST:


Also, the examples should be written descriptively - describing what the client does in the example scenario. SHOULd and MUST etc are for the specification itself.

…nto evm-reverse-resolution

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

Arachnid · 2024-05-14T09:27:25Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+
+To make things explicit we will require the signing of a message to confirm that the address in question would like to use mainnet or another network as fallback. This would either resolve directly on mainnet. Defaults would only be applicable to EoAs that can sign a message. This is because smart contract accounts would not be able to reliably set a default on all chains.
+
+### Setting default


This is quite vague. Is it worth including at all?

Do you mean removing everything related to defaults?

Yes; it seems incomplete.

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

Co-authored-by: Nick Johnson <arachnid@notdot.net>

Arachnid · 2024-06-07T14:34:03Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+
+1) If a dapp has a connected user it SHOULD first check the chainId of the user.
+2) It will then construct the cointype using ENSIP-11: `coinType = 0x80000000 | chainId`, which must be converted to lower-case hexadecimal representation.
+3) If the chainId is 1, it should call `[address].addr.reverse`, then skip to step 5.


What does it mean to "call" an ENS name?

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

Arachnid · 2024-06-07T14:47:51Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+
+ENSIP-12 was concieved before the ENS L2 reverse resolution specification and therefore should be updated to reflect the current state of ENS primary name resolution. This means that all avatar records are able to be updated on a per-chain basis by updating the avatar record on their reverse node.
+
+#### Example of resolving an avatar on an L2 or EVM chain


This is titled "example" but seems to describe a mandatory process for resolving avatars. It also duplicates much of the functionality of the above section. Can we reformulate it to be clearer as a standard, and less duplicative?

Arachnid · 2024-06-07T14:51:17Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+
+To make things explicit we will require the signing of a message to confirm that the address in question would like to use mainnet or another network as fallback. This would either resolve directly on mainnet. Defaults would only be applicable to EoAs that can sign a message. This is because smart contract accounts would not be able to reliably set a default on all chains.
+
+### Setting default


Yes; it seems incomplete.

Co-authored-by: Nick Johnson <arachnid@notdot.net>

Arachnid · 2024-06-21T11:13:06Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+To determine the avatar URI for a specific EVM chain address, the client can follow the resolution process above until step 6) And then do the following
+
+1. Perform [Ethereum address avatar text record resolution](https://docs.ens.domains/ensip/12#ethereum-address) on the reverse node.
+2. If none is found, proceed to step 7), if no primary name is found, consider the avatar resolution a failure


Arachnid · 2024-06-21T11:14:09Z

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

+1. Perform [Ethereum address avatar text record resolution](https://docs.ens.domains/ensip/12#ethereum-address) on the reverse node.
+2. If none is found, proceed to step 7), if no primary name is found, consider the avatar resolution a failure
+3. Perform [ENS name avatar text record resolution](https://docs.ens.domains/ensip/12#ens-name) on the ENS name.
+4. Complete the Reverse resolution process and consider the avatar found valid if the Primary name has been verified on step 12)


I don't think this last line is necessary.

Co-authored-by: Jeff Lau <tyranel@hotmail.com>

cb-elileers · 2024-07-09T21:01:37Z

docs/ensip/19.mdx

+### Examples of valid L2 reverse resolution
+
+* Arbitrum: 0f32b753afc8abad9ca6fe589f707755f4df2353.8000A4B1.reverse
+* Optimism:


Unwanted newline?

stevieraykatz · 2024-07-18T20:11:34Z

docs/ensip/19.mdx

+3) Otherwise, set `coinType` using ENSIP-11: `coinType = 0x80000000 | chainId`.
+4) Set `reverseName = '[address].[coinTypeAsHex].reverse'`
+5) Set `node = namehash(reverseName)`.
+6) Fetch the resolver for the reverse name: `resolver = registry.resolver(node)`


I think that this should explicitly state that clients use wildcard resolution so that CCIP-enabled reverse nodes are picked up.

jefflau and others added 8 commits March 14, 2023 15:37

First draft of evm-chain reverse resolution

2739178

Expand upon the spec

6a043e0

Add a point about keeping a default resolver

7abd935

Add line about DAO/multisig owning the subnames controlling ccip-read

53b4a1c

Add extension to ENSIP-12 for avatar resolution

0a6fb2d

Add in reasoning for deprecating use of mainnet reverse record on evm…

bd38f8b

…-compatible chains

Merge branch 'master' of github.com:ensdomains/docs into ensip-16

45d2cbd

Change ensip number to 17

d3a0c48

moldy530 reviewed Oct 10, 2023

View reviewed changes

ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md Outdated Show resolved Hide resolved

Add a default setup process

5341063

lucemans added ENSIP v1 labels Jan 24, 2024

makoto reviewed Feb 5, 2024

View reviewed changes

Fix typo

f71d920

Arachnid reviewed Mar 7, 2024

View reviewed changes

Updates from feedback

1b13e44

jefflau added 6 commits March 20, 2024 15:35

Add link to avatar resolution ensip in evm example

00d9d74

Add link to avatar resolution ensip in evm example

2f35f9b

Update to use evm chain id vs cointype

f184b0b

Add examples of L2 reverse resolution

ec8da79

Resolve conflict

57b220c

resolve conflict

95d8bc9

Arachnid requested changes Mar 25, 2024

View reviewed changes

jefflau and others added 3 commits March 28, 2024 14:26

Update ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

41b35c1

Co-authored-by: Nick Johnson <arachnid@notdot.net>

Update ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

acbe22e

Co-authored-by: Nick Johnson <arachnid@notdot.net>

Update ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

89c4259

Co-authored-by: Nick Johnson <arachnid@notdot.net>

Arachnid reviewed Apr 4, 2024

View reviewed changes

additions from feedback

b478b82

Merge branch 'evm-reverse-resolution' of github.com:ensdomains/docs i…

8fa5b3c

…nto evm-reverse-resolution

jefflau requested review from Arachnid and makoto May 10, 2024 09:35

Arachnid requested changes May 14, 2024

View reviewed changes

jefflau and others added 8 commits May 31, 2024 12:58

Update ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

7253c72

Co-authored-by: Nick Johnson <arachnid@notdot.net>

Add glossary of terms, fix resolution process with mainnet resolution

1026228

Change forward resolution to use ENSIP-10

75ffb3d

Change resolve to a function

93694c1

Add legacy addr() into resolution process

0facf11

Change decimal cointypes to hex

c1fedb3

Change address representation to lowercase

43234f1

Remove note

9b0589c

jefflau requested a review from Arachnid June 7, 2024 08:29

Arachnid requested changes Jun 7, 2024

View reviewed changes

jefflau and others added 4 commits June 19, 2024 11:28

Update ens-improvement-proposals/ensip-17-evmchain-reverse-resolution.md

b63cce9

Co-authored-by: Nick Johnson <arachnid@notdot.net>

Update resolution process

e435268

Remove default section

4c9c2f7

Adjust the avatar resolution process to be less duplicative

de73a71

jefflau requested a review from Arachnid June 19, 2024 16:39

Arachnid approved these changes Jun 21, 2024

View reviewed changes

jefflau and others added 3 commits June 24, 2024 11:57

Adjust avatar resolution process

1c8d5f2

Introduce ENSIP-19

928164f

Co-authored-by: Jeff Lau <tyranel@hotmail.com>

Merge branch 'ensip/reverse-multichain' into evm-reverse-resolution

71c2fd7

lucemans requested review from lucemans and svemat01 as code owners June 26, 2024 23:38

Update Index to include ENSIP-19

5c45407

cb-elileers reviewed Jul 9, 2024

View reviewed changes

jefflau merged commit d5e1e8f into master Jul 17, 2024
4 checks passed

lucemans deleted the evm-reverse-resolution branch July 17, 2024 09:52

stevieraykatz reviewed Jul 18, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Evm reverse resolution #157

Evm reverse resolution #157

jefflau commented Aug 24, 2023

moldy530 Oct 10, 2023

jefflau Oct 11, 2023

makoto Feb 5, 2024

Arachnid left a comment

cloudflare-workers-and-pages bot commented Mar 20, 2024 •

edited

Loading

Arachnid Mar 25, 2024

jefflau Mar 28, 2024

Arachnid Apr 4, 2024

Arachnid left a comment

Arachnid Apr 4, 2024

Arachnid May 14, 2024

jefflau Jun 3, 2024

Arachnid Jun 7, 2024

Arachnid Jun 7, 2024

Arachnid Jun 7, 2024

Arachnid Jun 7, 2024

Arachnid Jun 21, 2024

Arachnid Jun 21, 2024

cb-elileers Jul 9, 2024

stevieraykatz Jul 18, 2024


		To determine the avatar URI for a specific EVM chain address, the client MUST reverse-resolve the address by querying the ENS registry on Ethereum for the resolver of `<address>.<coinType>.reverse`, where `<address>` is the lowercase hex-encoded Ethereum address, without leading '0x'. Then, the client calls `.text(namehash('<address>.<coinType>.reverse'), 'avatar')` to retrieve the avatar URI for the address.

		If a resolver is returned for the reverse record, but calling `text` causes a revert or returns an empty string, the client MUST call `.name(namehash('<address>.<coinType>.reverse'))`. If this method returns a valid ENS name, the client MUST:


		To make things explicit we will require the signing of a message to confirm that the address in question would like to use mainnet or another network as fallback. This would either resolve directly on mainnet. Defaults would only be applicable to EoAs that can sign a message. This is because smart contract accounts would not be able to reliably set a default on all chains.

		### Setting default


		ENSIP-12 was concieved before the ENS L2 reverse resolution specification and therefore should be updated to reflect the current state of ENS primary name resolution. This means that all avatar records are able to be updated on a per-chain basis by updating the avatar record on their reverse node.

		#### Example of resolving an avatar on an L2 or EVM chain

Evm reverse resolution #157

Evm reverse resolution #157

Conversation

jefflau commented Aug 24, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Arachnid left a comment

Choose a reason for hiding this comment

cloudflare-workers-and-pages bot commented Mar 20, 2024 • edited Loading

Deploying ens-docs with Cloudflare Pages

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Arachnid left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

cloudflare-workers-and-pages bot commented Mar 20, 2024 •

edited

Loading