L2 Interop Working Group - Call #8
April 30th, 2025
- Chain-specific addresses aka “Interoperable addresses” (ERC-7828 and ERC-7930)
Call Notes
condensed notes below – watch the recording (above) for full discussion
TL;DR
- Chain-specific addresses (aka “interoperable addresses”) have been revamped from the original ERC-7828 design, led by Wonderland team in collaboration with co-authors from wallet teams, L2s, and ENS
- Original ERC is now split into two:
- ERC-7828: human-readable names for Interoperable Addresses
- ERC-7930: interoperable addresses: extensible binary format to refer to an address specific to one chain
Overview of Interoperable Addresses Standards
Evolution of the Standards
- Initial attempts tried combining binary and text representation in one format
- Challenges due to different requirements from wallets vs message passing protocols
- Decision made to split into two separate standards to better serve different use cases:
- Smart contracts/cross-chain messaging (ERC-7930)
- Human-readable format for wallets and UIs (ERC-7828)
- Designed for smart contracts and intents/cross-chain messaging frameworks
- Binary payload structure:
- Version field (for future extensions)
- Chain Type (matches namespace)
- Chain Reference (specific chain within ecosystem)
- Address field
- Basic text representation format (checksum only used in text representation, not in binary)
- Supports all chains in Ethereum ecosystem (including non-EVM)
ERC-7828 Features and Implementation
Next Steps and Discussion Points
- Resolve address format concerns (email collision)
- ethmagicians discussion forum for additional feedback
- Implementation considerations for wallets and naming registries being finalized