Add ERC: Chain-specific addresses using ENS #735
Conversation
eip-review-bot
changed the title
|
The commit 32b8276 (as a parent of 9e96e5f) contains errors. |
|
|
||
| The resolution of a `address@chain` on the contrary, imposes that the left-hand resolves to an address and the right-hand to a chain identifier. | ||
|
|
||
| When given a `[email protected]`, the wallet can resolve `rollup.eth` to get a chain identifier and `user.rollup.eth` to get an address. In any other case it fails. |
There was a problem hiding this comment.
This doesn't require a new syntax: When the wallet is resolving user.rollup.eth, the standard resolution process should be resolve to resolve the way you described: resolve rollup.eth to get a chain identifier and user.rollup.eth to get an address.
This approach also allows user.rollup.eth to override this behavior by setting a record for their own preferred chain identifier to use when their ENS name is resolved. *.rollup.eth names will likely never override this, but I'd expect almost every user.eth to want to receive funds on some chain that isn't L1.
| ``` | ||
| ### Note: default fallbacks | ||
|
|
||
| If a user receives a legacy address without chain name, the wallet can: |
There was a problem hiding this comment.
I don't think any of these fallbacks should be our target behavior. Users should be able to control on which chain assets sent to their ENS name arrive. I think ENS experts should lead the way on this resolution process via an ENSIP.
| @@ -0,0 +1,235 @@ | |||
| --- | |||
There was a problem hiding this comment.
| --- | |
| --- | |
| eip: 7828 |
Assigning next sequential EIP/ERC/RIP number.
Numbers are assigned by editors & associates.
Please also update the filename.
| title: Chain-specific addresses using ENS | ||
| description: A unified chain-specific address format that allows specifying the account as well as the chain on which that account intends to transact. | ||
| author: Sam Kaufman (@SampkaML), Marco Stronati (@paracetamolo), Yuliya Alexiev (@yuliyaalexiev), Jeff Lau (@jefflau), Sam Wilson (@samwilsn), Vitalik Buterin (@vbuterin) | ||
| discussions-to: <URL> |
There was a problem hiding this comment.
Please create a discussions topic in Eth Magicians.
https://ethereum-magicians.org/c/ercs/57
It just needs to be a link to this PR.
| account ::= <user>@<chain> | ||
| ``` | ||
|
|
||
| Note the difference between `ens-name`, which is a full ENS name, and `ens-subdomain` that is just a segment of a name between dots. E.g. `user.app.eth` is a name, `user` and `app` are subdomains. |
There was a problem hiding this comment.
In the below examples, isn't the user also just <address> | <ens-name>?
No description provided.