{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "ens-address-records",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/ens-address-records/",
  "collection": "ethereum",
  "title": "ENS address records: one name, different destinations",
  "description": "Check the coin and chain context of ENS address records before using a readable name as a payment destination.",
  "aliases": [
    "ENS multiple addresses",
    "ENS address record wrong network"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:27:58.939Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "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.",
    "claimId": "ens-address-records-quick-answer",
    "sourceIds": [
      "x425-eth-ens-resolution",
      "x425-eth-ens-reverse"
    ]
  },
  "keyFacts": [
    {
      "label": "Multiple records",
      "value": "ENS resolution can return coin-specific or chain-specific addresses.",
      "sourceIds": [
        "x425-eth-ens-resolution"
      ],
      "id": "multiple-records",
      "claimId": "ens-address-records-fact-multiple-records"
    },
    {
      "label": "Chain context",
      "value": "EVM-chain address records use defined coin-type mappings.",
      "sourceIds": [
        "x425-eth-ens-resolution"
      ],
      "id": "chain-context",
      "claimId": "ens-address-records-fact-chain-context"
    },
    {
      "label": "Default support",
      "value": "Supported default EVM records can act as a fallback.",
      "sourceIds": [
        "x425-eth-ens-reverse"
      ],
      "id": "default-support",
      "claimId": "ens-address-records-fact-default-support"
    }
  ],
  "prerequisites": [
    "ethereum-chain-id"
  ],
  "sections": [
    {
      "id": "destination",
      "heading": "Resolve the intended transfer, not just the text",
      "sourceIds": [
        "x425-eth-ens-resolution"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "example",
      "heading": "Different treasury addresses can be intentional",
      "sourceIds": [
        "x425-eth-ens-resolution"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "updates",
      "heading": "Changing routing affects future lookups",
      "sourceIds": [
        "x425-eth-ens-resolution",
        "x425-eth-ens-roles"
      ],
      "paragraphs": [
        "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."
      ]
    }
  ],
  "faq": [
    {
      "question": "Can I put one address in every EVM record?",
      "answer": "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.",
      "sourceIds": [
        "x425-eth-ens-resolution",
        "x425-eth-ens-reverse"
      ]
    },
    {
      "question": "Does setting a rollup address bridge my ETH?",
      "answer": "No. The record tells compatible software where to send on that chain. Moving assets between chains requires a separate supported process.",
      "sourceIds": [
        "x425-eth-ens-resolution"
      ]
    }
  ],
  "claims": [
    {
      "id": "ens-address-records-quick-answer",
      "articleSlug": "ens-address-records",
      "statement": "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.",
      "sourceIds": [
        "source-9b4fe04b40d00867",
        "source-8e756b4d7083a59e"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-9b4fe04b40d00867",
          "locator": "Resolving addresses; multicoin lookup"
        },
        {
          "sourceId": "source-8e756b4d7083a59e",
          "locator": "Primary names; reverse resolution; verification"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Fresh Address Lookup specifies coin types and ENSIP11 mapping for EVM chains; Primary Names supports default EVM fallback. Record mutation is routing change, not fund movement. No arbitrary assumption that same-looking addresses have identical authority cross-chain."
        ]
      }
    },
    {
      "id": "ens-address-records-fact-multiple-records",
      "articleSlug": "ens-address-records",
      "statement": "Multiple records: ENS resolution can return coin-specific or chain-specific addresses.",
      "sourceIds": [
        "source-9b4fe04b40d00867"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-9b4fe04b40d00867",
          "locator": "Resolving addresses; multicoin lookup"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Fresh Address Lookup specifies coin types and ENSIP11 mapping for EVM chains; Primary Names supports default EVM fallback. Record mutation is routing change, not fund movement. No arbitrary assumption that same-looking addresses have identical authority cross-chain."
        ]
      }
    },
    {
      "id": "ens-address-records-fact-chain-context",
      "articleSlug": "ens-address-records",
      "statement": "Chain context: EVM-chain address records use defined coin-type mappings.",
      "sourceIds": [
        "source-9b4fe04b40d00867"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-9b4fe04b40d00867",
          "locator": "Resolving addresses; multicoin lookup"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Fresh Address Lookup specifies coin types and ENSIP11 mapping for EVM chains; Primary Names supports default EVM fallback. Record mutation is routing change, not fund movement. No arbitrary assumption that same-looking addresses have identical authority cross-chain."
        ]
      }
    },
    {
      "id": "ens-address-records-fact-default-support",
      "articleSlug": "ens-address-records",
      "statement": "Default support: Supported default EVM records can act as a fallback.",
      "sourceIds": [
        "source-8e756b4d7083a59e"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-8e756b4d7083a59e",
          "locator": "Primary names; reverse resolution; verification"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Fresh Address Lookup specifies coin types and ENSIP11 mapping for EVM chains; Primary Names supports default EVM fallback. Record mutation is routing change, not fund movement. No arbitrary assumption that same-looking addresses have identical authority cross-chain."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-eth-ens-resolution",
      "label": "ENS address lookup",
      "publisher": "ENS Labs",
      "url": "https://docs.ens.domains/web/resolution/",
      "locator": "Resolving addresses; multicoin lookup",
      "note": "Resolve the requested coin or chain address rather than assuming all records are one payment destination.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:25.398Z",
      "contentSha256": "8fff5811a3c95fa9d36b2a46de975e99dbafb310a55e5329f3062bc662e1eb40",
      "recordId": "source-9b4fe04b40d00867"
    },
    {
      "id": "x425-eth-ens-reverse",
      "label": "ENS primary names",
      "publisher": "ENS Labs",
      "url": "https://docs.ens.domains/web/reverse/",
      "locator": "Primary names; reverse resolution; verification",
      "note": "Reverse-name display, chain-specific primary names and forward-address verification.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:25.312Z",
      "contentSha256": "1f7f00ca52002d56a66b5ce6e7fd67180aaef4e407b9ee61d5878ccfa90e0e1d",
      "recordId": "source-8e756b4d7083a59e"
    },
    {
      "id": "x425-eth-ens-roles",
      "label": "ENS terminology",
      "publisher": "ENS Labs",
      "url": "https://docs.ens.domains/terminology/",
      "locator": "Owner; controller; resolver; registrant",
      "note": "Roles in ENS naming, resolution and management.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:25.181Z",
      "contentSha256": "eda2d55d25857800cbddcf2ddc398a9235d7cf2572bc315534aaf8b3939fed9a",
      "recordId": "source-0314bf4e15f4a3c3"
    }
  ],
  "related": {
    "articles": [
      "ethereum-chain-id",
      "ethereum-layer-2",
      "blockchain-bridges",
      "ens-primary-name",
      "ens-subnames"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "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/"
}