Use caip 350 in ENSIP-11 and ENSIP-19#30
Open
0xteddybear wants to merge 3 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Gm ENS frens!
In the context of trying to finalize ERC-7828, I was in need of some clarifications on how ENSIP-19 (which afaik is being actively worked on) serializes chain names, and I found it easier to just write them into the draft spec.
I've taken this as an opportunity to edit ENSIP-11 as well, since it's in draft status, to use Interoperable Addresses as a more extensible & future proof way to refer to chains, that paves the way for an ERC-7785 future
I'm looking forward on iterating with you on this, since it's my first time involving myself with ENS at an architectural level, and there are probably some considerations I'm not seeing, especially around what kind updates to current resolvers are possible in the production ENS deployment.