# ENS address records: one name, different destinations An ENS name can store different address records for different coins or EVM chains. A wallet must resolve the record appropriate to the transfer it is preparing. The Ethereum mainnet address record is not proof that every other network uses the same recipient, and updating a record does not move or bridge any existing funds. Evidence: [ENS address lookup](https://docs.ens.domains/web/resolution/); [ENS primary names](https://docs.ens.domains/web/reverse/) Canonical: https://degreesofsatoshi.com/encyclopedia/ens-address-records/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Multiple records:** ENS resolution can return coin-specific or chain-specific addresses. ([ENS address lookup](https://docs.ens.domains/web/resolution/)) - **Chain context:** EVM-chain address records use defined coin-type mappings. ([ENS address lookup](https://docs.ens.domains/web/resolution/)) - **Default support:** Supported default EVM records can act as a fallback. ([ENS primary names](https://docs.ens.domains/web/reverse/)) ## Resolve the intended transfer, not just the text The same readable name may be used in applications on several networks. A correct resolver asks for the corresponding address type, rather than assuming one Ethereum record is universal. Wallet support for newer record conventions matters. Before confirming a payment, compare the network, asset and resulting address. Name readability does not remove those checks. Evidence: [ENS address lookup](https://docs.ens.domains/web/resolution/) ## Different treasury addresses can be intentional Suppose an organization publishes one address for mainnet receipts and another for its rollup treasury. A rollup payment should use the rollup record supported by that name and wallet. Copying the mainnet result into a rollup send form bypasses that routing decision. The example is about record selection, not address conversion. A name service does not guarantee that a recipient controls every same-looking address on every chain. Evidence: [ENS address lookup](https://docs.ens.domains/web/resolution/) ## Changing routing affects future lookups Authorized record changes update what later resolution can return. They do not alter historical transfers or migrate balances from the previously published address. Cached results can also delay when an application displays an update. After changing a payment record, verify resolution in the intended application and chain context. Keep control of any old account that still holds assets. Evidence: [ENS address lookup](https://docs.ens.domains/web/resolution/); [ENS terminology](https://docs.ens.domains/terminology/) ## Questions ### Can I put one address in every EVM record? You can configure supported records that way when it is appropriate, but the name service does not establish that doing so is correct for your account setup. Evidence: [ENS address lookup](https://docs.ens.domains/web/resolution/); [ENS primary names](https://docs.ens.domains/web/reverse/) ### Does setting a rollup address bridge my ETH? No. The record tells compatible software where to send on that chain. Moving assets between chains requires a separate supported process. Evidence: [ENS address lookup](https://docs.ens.domains/web/resolution/) ## Claims and scope ### ens-address-records-quick-answer An ENS name can store different address records for different coins or EVM chains. A wallet must resolve the record appropriate to the transfer it is preparing. The Ethereum mainnet address record is not proof that every other network uses the same recipient, and updating a record does not move or bridge any existing funds. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ens-address-records-fact-multiple-records Multiple records: ENS resolution can return coin-specific or chain-specific addresses. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ens-address-records-fact-chain-context Chain context: EVM-chain address records use defined coin-type mappings. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ens-address-records-fact-default-support Default support: Supported default EVM records can act as a fallback. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [ENS address lookup](https://docs.ens.domains/web/resolution/) — ENS Labs. Resolve the requested coin or chain address rather than assuming all records are one payment destination. Locator: Resolving addresses; multicoin lookup. Retrieved: 2026-10-02T18:55:25.398Z. - [ENS primary names](https://docs.ens.domains/web/reverse/) — ENS Labs. Reverse-name display, chain-specific primary names and forward-address verification. Locator: Primary names; reverse resolution; verification. Retrieved: 2026-10-02T18:55:25.312Z. - [ENS terminology](https://docs.ens.domains/terminology/) — ENS Labs. Roles in ENS naming, resolution and management. Locator: Owner; controller; resolver; registrant. Retrieved: 2026-10-02T18:55:25.181Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “ENS address records: one name, different destinations.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ens-address-records/