Ethereum Foundation Clear Signing Upgrade: What It
Published 6/16/2026, 6:14:17 AM
Claim Resolution Summary
| Claim | Status | Confidence | Key Gap |
|---|---|---|---|
| c1: EF has implemented/implementing clear signing upgrade | UNRESOLVED | 0.70 | Launch date (May 12, 2026) contradicted by independent sources; implementation status across wallet ecosystem needs verification |
| c2: Specific implications for wallet display/processing | UNRESOLVED | 0.75 | Implementation details across wallet types (mobile vs desktop, hot vs hardware) need specific examples |
| c3: Changes user experience or security model | UNRESOLVED | 0.92 | Minor date inconsistency; full ecosystem partner timeline verification needed |
What Clear Signing Is
The Ethereum Foundation's Clear Signing is an open security standard designed to eliminate "blind signing" — a structural vulnerability where users approve opaque hexadecimal transaction data without understanding the actual intent. The standard replaces incomprehensible hex with human-readable transaction descriptions, enforcing a "what you see is what you sign" principle.
The initiative is part of the Foundation's Trillion Dollar Security initiative. However, the specific launch date of May 12, 2026 cited on clearsigning.org is contradicted by independent search results indicating the Trillion Dollar Security Initiative was announced on May 14, 2025 — no independent evidence confirms the May 12, 2026 date. [Source: https://clearsigning.org/]
How It Works: The Three Standards
Clear Signing rests on three Ethereum standards:
| Standard | Role |
|---|---|
| ERC-7730 | JSON "descriptor" format allowing smart contracts to describe functions in plain language. Wallets use these descriptors to render human-readable transaction summaries. |
| ERC-8176 | Attestation framework — independent auditors cryptographically verify descriptor accuracy via the Ethereum Attestation Service (EAS). |
| ERC-8213 | Bytes-level fallback digest for contracts that cannot use ERC-7730 (custom encodings, new deployments). |
[Source: https://eips.ethereum.org/EIPS/eip-7730]
Workflow:
- Smart contract developer creates a JSON metadata file describing contract functions in plain English (e.g., "Swap X ETH for Y USDC")
- Descriptor is submitted to the EF-hosted registry at
github.com/ethereum/clear-signing-erc7730-registryand merged - When a user initiates a transaction, the wallet fetches the descriptor
- The user sees a structured summary on the secure signing screen before approving
[Source: https://github.com/ethereum/clear-signing-erc7730-registry]
UX Transformation for Wallets
Before (Blind Signing): Users approve raw hex data with no way to verify intent — a "click → hope → pray" flow.
After (Clear Signing): Wallets display structured human-readable summaries with amounts, recipient addresses (resolved ENS names), function calls, and permission scope.
| Before (Blind Signing) | After (Clear Signing) |
|---|---|
0x6a76120200000000000000000000000087870bca3f3fd6335c3f4ce8392d69350b4fa4e2... | "Swap 0.5 ETH for ~1,250 USDC on Uniswap. Max slippage: 0.5%" |
Display elements users see:
- Specific action (swap, send, approve, stake)
- Exact token amounts with tickers
- Recipient address (resolved ENS)
- Permission scope (e.g., token approval limits)
- Requesting dApp identity
[Source: https://clearsigning.org/]
Gap noted: Specific implementation examples or screenshots of before/after wallet interfaces across different wallet types (mobile vs desktop, hot vs hardware) are not yet documented in available sources.
Security Implications
Clear Signing directly addresses the root cause of major exploits:
- Bybit hack ($1.4B–$1.5B, February 2025): Attackers replaced a smart contract upgrade with a malicious version — users had no way to read the transaction intent. [VERIFIED: Multiple independent sources confirm the Bybit hack occurred in February 2025 with approximately $1.5 billion in losses.]
- Radiant Capital ($50M, October 2024): Similar vector — malicious approvals hidden behind opaque data. [VERIFIED: Multiple independent sources confirm the Radiant Capital exploit occurred on October 16, 2024 with approximately $50 million in losses.]
Protections provided:
- Phishing protection via recipient address verification
- Amount confirmation before signing
- Function clarity (users know which contract functions are being called)
- Permission awareness (users see exactly what approvals they're granting)
[Source: https://clearsigning.org/]
Ecosystem Adoption Status
| Wallet/Partner | Status |
|---|---|
| Ledger | Supports natively in Ledger Wallet for native flows (send, swap, stake). Has disabled blind signing by default — requires manual re-enablement. |
| Trezor | Plans implementation by June 30, 2026 |
| MetaMask | Working group member |
| WalletConnect | Working group member |
| Other supporters | Keycard, ZKnox, Fireblocks, Zama, OneKey, Keystone, Cyfrin, Sourcify, Argot |
[Source: https://clearsigning.org/]
Gap noted: Current implementation status beyond Ledger's native support is not fully documented. Coverage depends on developers publishing ERC-7730 files; for unsupported contracts, wallets show a warning + raw hash.
Conclusion
The Ethereum Foundation's Clear Signing upgrade represents a significant structural change to how wallets display and process transactions — replacing opaque hex data with human-readable summaries that let users verify transaction intent before signing. The security implications are substantial, directly addressing the blind signing vulnerability responsible for billions in losses (Bybit: ~$1.5B, Radiant Capital: ~$50M). However, the specific launch date remains contested (clearsigning.org states May 12, 2026; independent sources indicate May 2025 for the broader initiative), and full ecosystem adoption timelines are still incomplete — particularly for non-hardware wallet implementations.
Follow-Up Actions
-
Monitor ecosystem adoption timelines — Track Trezor's June 30, 2026 implementation date and MetaMask/WalletConnect integration status via the official registry at
github.com/ethereum/clear-signing-erc7730-registry. -
Verify current coverage — Query the EF-hosted registry to identify which major DeFi contracts currently have ERC-7730 descriptors published, to assess real-world UX impact today.