ENSIP-X: Interoperable Address Resolver Profiles (ENSIP-10)#63
Open
nxt3d wants to merge 2 commits intoensdomains:masterfrom
Open
ENSIP-X: Interoperable Address Resolver Profiles (ENSIP-10)#63nxt3d wants to merge 2 commits intoensdomains:masterfrom
nxt3d wants to merge 2 commits intoensdomains:masterfrom
Conversation
Define resolve()-only profiles intended for ENSIP-10 ExtendedResolver calls: - iAddress(chain-identifier) -> bytes - iReverse(chain-identifier) -> string - iData(key) -> bytes The profiles omit node from calldata and are keyed by an ERC-7930 chain-identifier.
Update iReverse(bytes) to take a full ERC-7930 interoperable address (chain + target address) rather than a zero-length chain-identifier, and adjust terminology + examples accordingly.
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.
Summary
This PR introduces a new ENSIP draft defining three resolver profiles intended to be called via ENSIP-10
resolve(bytes name, bytes data).These profiles omit
nodefrom calldata (since ENSIP-10 provides the DNS-encoded name) and standardize interoperable, chain-specific resolution using an ERC-7930chain-identifier.What’s included
iAddress(chain-identifier) -> bytes: returns raw target address bytes (no length prefix)iReverse(chain-identifier) -> string: returns a chain-specific human-readable name (reverse-style)iData(key) -> bytes: returns arbitrary bytes keyed by a string (aligned with ENSIP-24 key style)Motivation / Goals
nodeargument)iDataconsistent with ENSIP-24’s string-key approachNotes
resolve().iReverseare intentionally out of scope for this initial draft.