ERC-5267: wallets can retrieve the domain behind a typed signature
The interface exposes the fields used to form an EIP-712 domain. A readable domain helps integration, but the signed message still needs its own review.
Full analysis selected. Choose Quick brief to read the key points first.
WFN QUICK BRIEF · UNDER 1 MIN
The short version
MODE 2 OF 2
What the primary record establishes
ERC-5267, created on 14 July 2022 and published as Final, defines eip712Domain() to return a domain description, including a field bitmap and values such as chainId and verifyingContract. Ethereum — ERC-5267, Final; created 14 July 2022 ↗
What the distinction changes
WFN interpretation: obtaining a structured description is more useful to an integration than treating an opaque domain hash as a complete explanation for the person signing.
What to check before drawing a conclusion
Check both field presence and value, rather than assuming every returned slot participates in the signature. Record the network, contract and observation block when comparing what the interface displayed with what was signed.
Quick Brief is a reading aid. The full article and source trail stay on this page.
WFN STORY COMPASS
Choose your reading angle
Switch between the reported record, market context and open questions. Status labels distinguish claims from findings.
All context layers are visible. Choose a lens to jump to that part of the story.
Original WFN vector illustrationWFN · 30 October 2026
Editorial noteSource-based explanation with original WFN analysis. Historical records retain their dates; numerical examples are illustrative. The original vector illustration is conceptual and is not documentary evidence.
WFN REALITY LEDGER
What is on the record?
Primary-source explainer
Primary-source explainer
Primary record / reference periodHistorical specification; Final; created 14 July 2022
The linked source supports the documented record; WFN interpretation and illustrative examples are separate.
The interface exposes the fields used to form an EIP-712 domain. A readable domain helps integration, but the signed message still needs its own review.
01 · VERIFIED RECORD
What the primary record establishes
ERC-5267, created on 14 July 2022 and published as Final, defines eip712Domain() to return a domain description, including a field bitmap and values such as chainId and verifyingContract. Ethereum — ERC-5267, Final; created 14 July 2022 ↗
The bitmap identifies which optional fields are present; a returned value for an absent field is unspecified. The specification also allows the domain to change during a contract’s lifetime. Ethereum — ERC-5267, Final; created 14 July 2022 ↗
02 · WFN EDITORIAL ANALYSIS
What the distinction changes
WFN interpretation: obtaining a structured description is more useful to an integration than treating an opaque domain hash as a complete explanation for the person signing.
However, a domain describes the context. The message might authorise a transfer, an allowance or another operation, so its contents and limits still determine what the user is agreeing to.
03 · REVIEW POINTS
What to check before drawing a conclusion
Check both field presence and value, rather than assuming every returned slot participates in the signature. Record the network, contract and observation block when comparing what the interface displayed with what was signed.
If the application caches a domain description, test how it refreshes that information after changes. A matching project name is only a label; the deployed address and actual message provide the concrete objects that a signing review must inspect.
