Update ERC-7730: Add interoperableAddress format to support erc-7930 interoperable addresses #1357
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
Collaborator
File
|
eip-review-bot
changed the title
|
The commit 1378524 (as a parent of b011daa) contains errors. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Abstract
This pull request extends ERC-7730 by introducing support for EIP-7930 Interoperable Addresses. The goal is to enable wallets to safely parse and display chain-specific addresses, improving security for cross-chain interactions.
Specification
A new format specifier,
interoperableAddress, has been added to the "Bytes formats" section. This instructs wallets to interpret a bytes value as an EIP-7930 binary payload and display it in its human-readable "Interoperable Name" format.Open for Discussion
Once an
interoperableAddressis parsed to reveal a standard address, how should we best leverage the rich features of the existingaddressNameformatter?