ERCs icon indicating copy to clipboard operation
ERCs copied to clipboard

Add ERC: Human readable names for Interoperable Addresses

Open jrudolf opened this issue 1 year ago • 7 comments

jrudolf avatar Nov 27 '24 10:11 jrudolf

✅ All reviewers have approved.

eip-review-bot avatar Nov 27 '24 10:11 eip-review-bot

My apologies if I'm in the wrong place, I've not done this before. I'm here to comment on this proposal. My feedback is simply to think about how it might map to blockchain agnostic representations, notably this one:

https://github.com/ChainAgnostic/CAIPs/blob/main/CAIPs/caip-10.md

Thank you.

lukepuplett avatar Dec 09 '24 20:12 lukepuplett

Heya! ENS already supports this from the get go!

Have a look at ENSIP-9 (defining different records for different chains) https://docs.ens.domains/ensip/9

And the documentation around it at: https://docs.ens.domains/web/resolution#multi-chain

This doesnt solve readability but it does introduce a method for fetching addresses for a certain chain id.

With regards to testnets you can make the queries to the ENS deployments on their respective chains. (So for Base Sepolia you would check Sepolia ENS)

lucemans avatar Dec 13 '24 18:12 lucemans

@lucemans I believe ENSIP-9 doesn’t actually solve the issue, but gives redundancy in case this only gets applied to the stricter Ethereum ecosystem. The whole reason to do this multi-chain resolution is to allow for ‘clean names’ based on a widely used primitive: chainID. ENSIP-9 builds on top of this with another identification system, while this ERC is an alternative.

BTW thank you for mentioning, it’s actually a great feature of ENS that could be publicized more!

iJaack avatar Dec 13 '24 22:12 iJaack

Please keep technical discussion on the forum: https://ethereum-magicians.org/t/erc-7828-chain-specific-addresses-using-ens/21930

SamWilsn avatar Dec 16 '24 19:12 SamWilsn

@lucemans

Have a look at ENSIP-9 (defining different records for different chains) https://docs.ens.domains/ensip/9

ENSIP-9 tries to support not only EVM chains, but also bitcoin, etc. This is good thing. But it invents its own way to refer to various chains. This is bad. New version of ENSIP-9 should be created, which refers to caip-10 ( https://chainagnostic.org/CAIPs/caip-10 ) instead. Everybody should stick to CAIP-10. See also this very good comment: https://ethereum-magicians.org/t/chain-specific-addresses/6449/28 by rekmarks

u59149403 avatar Apr 23 '25 00:04 u59149403

The commit 19194805e1a464da3acd7e3b69a9f03e2478eac2 (as a parent of c9254c17a7a9322e563831c9ca5782d1030f447e) contains errors. Please inspect the Run Summary for details.

github-actions[bot] avatar Jul 09 '25 15:07 github-actions[bot]