ERC-3770 Chain-specified address (Chain-specific addresses)
Draft · Names & metadata · created 2021-08-26
A notation standard that prepends a human-readable chain name to an address, so wallets and apps can immediately tell which chain's account the address belongs to.
Why it is needed
As the number of chains using the Ethereum Virtual Machine (EVM) besides the Ethereum mainnet grows, the same address string can refer to different targets on different chains. An address that is an externally owned account (EOA) on one chain may be a smart contract on another. Looking at the address alone gives no way to know which chain it is for, so human error can lead to lost funds. For example, sending funds on a given chain to a smart contract wallet address that was never deployed on that chain. A chain ID (EIP-155) that distinguishes chains by number already exists, but it was created for interoperability between developers, not something suited for displaying to users on a wallet or app screen. A human-readable chain identifier prefixed to the address is therefore needed.
In depth
Address format: shortName and colon
A chain-specified address has the form "shortName" ":" "address". That is, the chain's short name (shortName) comes first, followed by a colon (:), followed by a regular Ethereum address. Both shortName and address are strings. Since this does not change the existing address scheme but extends it with a human-readable chain identifier prefix, wallets and apps can apply it as is for display and input parsing.
Requirements for the two components
shortName is required and MUST be a valid chain short name registered in the ethereum-lists/chains repository (github.com/ethereum-lists/chains). Using a name from the public list rather than an arbitrary one ensures a consistent prefix per chain. address is also required and MUST be a hexadecimal address compatible with ERC-55. Since ERC-55 is a notation that uses the address's letter case as a checksum, the address portion after the prefix also retains a typo-checkable form.
Why a short name instead of a numeric chain ID
In theory, EIP-155's chainID could also be used as the prefix. However, chainID was not designed to be shown to users in a wallet or app, and it is optimized for interoperability between developers rather than human readability. The rationale behind this proposal is that eliminating ambiguity in user-facing addresses in a multi-chain environment requires linking the EIP-155 chain ID to a user-facing chain notation format. That is why a human-readable chain short name was adopted as the prefix instead of a numeric ID.
Compatibility with existing addresses
This standard does not invalidate the existing address format. However, an Ethereum address without a chain prefix still requires separate context to understand which chain it refers to. In other words, a prefixed address carries the chain information itself, while an unprefixed address still requires the parties exchanging it to confirm the chain separately, as is the case today.
Proposal status: Draft
This document was created on August 26, 2021 and its status is Draft. It is not yet a finalized standard, so the content may change or progress may stall. Developers intending to implement it should check the latest status of the original text.
Things to watch out for
- Confusion from similar chain names: Users can be confused by short chain names that look similar to each other. You should verify the chain name precisely before trusting a prefix.