Skip to content

Conversation

@aalimsahin
Copy link
Contributor

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.

@eip-review-bot
Copy link
Collaborator

eip-review-bot commented Dec 2, 2025

File ERCS/erc-7730.md

Requires 1 more reviewers from @arein, @arikg, @kuzdogan, @lcastillo-ledger, @llbartekll, @paoun-ledger

Copy link

@0xrcinus 0xrcinus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very supportive of this addition, thanks @aalimsahin !


| **`interoperableAddress`** | |
|----------------------------|------------------------|
| *Description* | Display byte array as an [ERC-7930](./eip-7930.md) Interoperable Name. The wallet MUST validate the checksum and format the display as `<address>@<chain>#<checksum>`. |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this type could also be used for specifying contracts on chains in one field, as in contract deployments:

{
                    "chainId": 1,
                    "address": "0xdAC17F958D2ee523a2206206994597C13D831ec7"
                }

|----------------------------|------------------------|
| *Description* | Display byte array as an [ERC-7930](./eip-7930.md) Interoperable Name. The wallet MUST validate the checksum and format the display as `<address>@<chain>#<checksum>`. |
| *Parameters* | --- |
| `resolveAddress` | Boolean. If set to `true`, the wallet SHOULD attempt to resolve the inner address segment using the same logic as `addressName` (e.g., resolving ENS names). Defaults to `false`. |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think strictly speaking this is "reverse resolution" https://docs.ens.domains/web/reverse

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants