A mapping from an ENS name to the contract address in Web3 URL
|Authors||Qi Zhou (@qizhou), Qiang Zhu (@qzhodl)|
|Requires||EIP-137, EIP-634, EIP-3770, EIP-4804|
This standard defines the mapping from an Ethereum name service (ENS) name to an Ethereum address for ERC-4804.
ERC-4804 defines a
web3://-scheme RFC 2396 URI to call a smart contract either by its address or a name from name service. If a name is specified, the standard specifies a way to resolve the contract address from the name.
Given contractName and chainid from a
web3:// URI defined in ERC-4804, the protocol will find the address of the contract using the following steps:
- Find the
contentcontracttext record on ENS resolver on chain chainid. Return an error if the chain does not have ENS or the record is an invalid ETH address.
- If the
contentcontracttext record does not exist, the protocol will use the resolved address of name from ERC-137.
- If the resolved address of name is the zero address, then return an “address not found” error.
contentcontract text record may return an Ethereum address in hexadecimal with a
0x prefix or an ERC-3770 chain-specific address. If the address is an ERC-3770 chain-specific address, then the chainid to call the message will be overridden by the chainid specified by the ERC-3770 address.
The standard uses
contentcontract text record with ERC-3770 chain-specific address instead of
contenthash so that the record is human-readable - a design principle of ERC-4804. Further, we can use the text record to add additional fields such as time to live (TTL).
No security considerations were found.
Copyright and related rights waived via CC0.
Please cite this document as:
Qi Zhou (@qizhou), Qiang Zhu (@qzhodl), "ERC-6821: Support ENS Name for Web3 URL [DRAFT]," Ethereum Improvement Proposals, no. 6821, April 2023. [Online serial]. Available: https://eips.ethereum.org/EIPS/eip-6821.