ERC-6093: structured token errors improve diagnosis without authenticating a contract
The standard names errors and their arguments for ERC-20, ERC-721 and ERC-1155. A recognizable error payload is still data supplied by the executing code.
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-6093 was created on 6 December 2022 and is marked Final. It standardizes custom errors for three common token interfaces rather than relying only on free-form revert strings. Ethereum — ERC-6093, Final ↗
What the distinction changes
A wallet can use those fields to explain why an attempted operation failed. They do not turn the error into an independent audit of the contract emitting it.
What to check before drawing a conclusion
Review the called address, ABI and execution context alongside decoded arguments. A familiar token symbol or error name should not replace identifying the intended contract.
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 · 28 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 periodFinal specification, created 6 December 2022
The linked source supports the documented record; WFN interpretation and illustrative examples are separate.
The standard names errors and their arguments for ERC-20, ERC-721 and ERC-1155. A recognizable error payload is still data supplied by the executing code.
01 · VERIFIED RECORD
What the primary record establishes
ERC-6093 was created on 6 December 2022 and is marked Final. It standardizes custom errors for three common token interfaces rather than relying only on free-form revert strings. Ethereum — ERC-6093, Final ↗
For example, ERC20InsufficientBalance identifies sender, balance and needed amount. Defined argument meanings let a client decode a more specific failure reason. Ethereum — ERC-6093, Final ↗
02 · WFN EDITORIAL ANALYSIS
What the distinction changes
A wallet can use those fields to explain why an attempted operation failed. They do not turn the error into an independent audit of the contract emitting it.
A contract can produce an expected-looking payload without satisfying every other property of a token standard. Diagnostic compatibility and authenticity are therefore different checks.
03 · REVIEW POINTS
What to check before drawing a conclusion
Review the called address, ABI and execution context alongside decoded arguments. A familiar token symbol or error name should not replace identifying the intended contract.
The historical specification supports clearer interfaces and tests. It does not promise that every failure has this format or guarantee that retrying a rejected transaction will be safe or successful.
