You have probably approved a crypto transaction without fully understanding what it actually did. Most people have. That gap between what you see on screen and what you actually authorize has cost the industry billions.
In 2025 alone, attackers stole more than 3 billion dollars from crypto users, and a significant share of that came from exploiting exactly this gap, according to the Chainalysis report. The technical term for this weak point is blind signing.
On May 12, 2026, the Ethereum Foundation launched a new standard called Clear Signing to fix it directly. This guide breaks down what changed, why it matters, and how it protects your funds today.
TL;DR
- Clear Signing turns raw, unreadable transaction data into plain language you can actually verify before approving.
- It runs on two combined standards: ERC-7730, which formats the readable description, and ERC-8176, which lets auditors verify that the description is accurate.
- The Ethereum Foundation formally launched Clear Signing as an ecosystem-wide standard on May 12, 2026.
- Ledger originally built the concept in 2021 and proposed ERC-7730 in 2024, then transferred governance to the Foundation this year.
- A public registry at clearsigning.org hosts verified transaction descriptors that any wallet can pull from.
- Backers include MetaMask, Trezor, Fireblocks, WalletConnect, Cyfrin, Sourcify, Zama, and Keycard.
- The Foundation cited the 1.4 billion dollar Bybit hack as a direct example of what blind signing enables.
- Adoption is still uneven as of July 2026 (51 protocols and 380 descriptors in the public registry as of end-June). You will still hit blind signing prompts on newer or unsupported contracts.
Note: While ERC-7730 remains formally a Draft EIP on the Ethereum standards track, the broader Clear Signing initiative (including the public registry and ERC-8176 attestation framework) was launched as live ecosystem infrastructure by the Ethereum Foundation on May 12, 2026.
Table of Contents
What Is Clear Signing?
Clear Signing is a security standard that shows you a plain-language summary of a transaction before you sign it. Instead of a wall of hexadecimal code, you see the recipient, the amount, and what the contract actually does.
The industry shorthand for this is “what you see is what you sign.” Your wallet or hardware device displays the true intent of the transaction, not just its raw code.
One important distinction upfront. Clear Signing started as a Ledger feature, but it is no longer Ledger-specific. As of May 2026, it is an open Ethereum Foundation standard that any wallet can implement.
How it works, step by step:

- A dApp sends you a raw transaction to sign.
- Your wallet checks the Clear Signing registry for a matching descriptor.
- If a verified descriptor exists, it decodes the transaction into readable terms.
- You review the recipient, token, amount, and function being called.
- You approve or reject based on what you actually understand.
Why Blind Signing Became One of Crypto’s Biggest Security Problems
Blind signing means approving a transaction using only its raw, encoded data. You see a string like 0xa9059cbb000000000000… instead of “Send 500 USDC to this address.”
This happens because most wallets historically could not decode every smart contract call into readable form. Developers had to manually support each protocol, and most never bothered.
You run into blind signing most often with:
- DeFi token approvals and swaps
- NFT minting and marketplace listings
- Smart contract interactions on new or niche protocols
- Permit signatures that grant spending access
The scale of the resulting phishing problem is significant. Binance alone intercepted 22.9 million phishing attempts in the first quarter of 2026, according to crypto.news reporting on the exchange’s security data. Blind signing is frequently the final step that turns a phishing attempt into a completed theft.
Real Hacks Caused by Blind Signing
These incidents show what happens when the presentation layer fails, even when the underlying wallet security is intact.
| Date | Incident | Estimated Loss | What Happened |
| February 2025 | Bybit exploit | 1.4 to 1.5 billion dollars | The Lazarus Group tricked the exchange into blind signing a malicious transaction |
| July 2024 | WazirX breach | Roughly 235 million dollars | Signers approved a transaction whose true intent was never displayed |
| Ongoing through 2026 | Wallet drainer scams | Part of the 3 billion dollar 2025 total | Malicious approvals hidden behind opaque calldata on fake dApp interfaces |
The pattern across all three is the same. The hardware or software wallet was never hacked. The user approved something they could not actually read.
Ledger’s Clear Signing vs. the Ethereum-Wide Standard
This distinction matters, and most explainers still get it wrong. Before May 2026, “Clear Signing” meant a Ledger device feature. That has changed.
Ledger’s original feature (2021 to 2024): A device-level UX and security improvement, exclusive to Ledger hardware wallets.
ERC-7730 (2024): Ledger’s proposal to formalize that feature as an open format any wallet could adopt.
ERC-7730 V2 (April 2026): An expanded version covering cross-chain transactions, software wallets, and confidential-token primitives.
The Ethereum Foundation launch (May 12, 2026): Ledger transferred governance of ERC-7730 to the Foundation, which combined it with a new attestation standard and launched the full Clear Signing standard.
Ledger still offers what it calls the most complete Clear Signing experience when its hardware is paired with Ledger Wallet, according to the company’s own blog. But the standard itself now belongs to the wider ecosystem, not to Ledger alone.
What Is ERC-7730?
ERC-7730 is the technical format at the center of Clear Signing. It is a JSON-based descriptor that tells a wallet how to translate a smart contract’s raw function calls into plain language.
Think of it as a translation file. The smart contract developer, or a third party, writes a descriptor once. Every wallet that supports ERC-7730 can then read it.
What a descriptor typically defines:
- Function labels, such as “Swap tokens” instead of swapExactTokensForTokens
- Parameter formatting, so amounts and addresses display cleanly
- Network and protocol context
- Approval and permit details
Because descriptors live off-chain in a registry, existing smart contracts do not need to be modified or redeployed to become compatible. Ledger has also open-sourced its internal developer tooling, including a Builder, Linter, Tester, and Analyzer, so any team can create and test descriptors.
What Is ERC-8176?
ERC-7730 solves the readability problem. It does not, by itself, solve the trust problem. That is where ERC-8176 comes in.
ERC-8176 is an attestation framework. It lets independent auditors cryptographically verify that a given ERC-7730 descriptor accurately represents what the underlying transaction actually does.
Without this layer, anyone could submit a misleading descriptor and label a malicious transaction as harmless. ERC-8176 gives wallets a way to check whether a descriptor has been independently reviewed before trusting it.
Wallet providers decide which auditors or attestation sources they trust. This keeps the system decentralized while still giving you a meaningful trust signal before you sign.
The Clear Signing Registry

The registry lives at clearsigning.org. It functions as the shared library that wallets pull descriptors from.
How it works:
- Developers or auditors submit ERC-7730 descriptors for a given contract.
- Independent security researchers review and attest to their accuracy under ERC-8176.
- Wallets query the registry and display verified descriptions to you at signing time.
The Ethereum Foundation’s Trillion Dollar Security Initiative manages the registry infrastructure. Because the system is off-chain and mirrorable, no existing dApp needs to redeploy its contracts to participate.
From Ledger Initiative to Ethereum Standard: The Full Timeline
- 2021: Ledger builds Clear Signing internally as a device-level feature.
- 2024: Ledger formalizes the idea and proposes it as ERC-7730.
- April 2026: ERC-7730 V2 releases, adding cross-chain, software wallet, and confidential-token support.
- May 12, 2026: Ledger transfers governance to the Ethereum Foundation. The Foundation launches the combined Clear Signing standard, built on ERC-7730, ERC-8176, and the public registry.
- Mid-2026 onward: Wallets, auditors, and dApps continue adopting the standard at varying speeds.
The governance transfer was deliberate. For competing wallets like MetaMask or Trezor to trust and adopt the standard, it could not remain under the control of a single hardware wallet company. Neutral stewardship was a prerequisite for ecosystem-wide adoption.
Why Ethereum Adopted ERC-7730 and ERC-8176
Ethereum’s wallet ecosystem was fragmented before this standard. Each wallet decoded transactions differently, if it decoded them at all.
The core reasons behind adoption:
- Standardization reduces duplicate decoding work across wallets.
- A shared format lets developers write one descriptor instead of many.
- Attestation gives institutions and regulated entities a verifiable trust signal.
- A consistent presentation layer directly closes the gap that caused the Bybit and WazirX losses.
- The framework is designed to extend cleanly into account abstraction as that rolls out further.
Clear Signing vs. Blind Signing

| Factor | Clear Signing | Blind Signing |
| Readability | Plain language summary | Raw hexadecimal data |
| Human verification | You can check the actual details | Not practically possible |
| Scam resistance | Higher, when a verified descriptor exists | Low, relies entirely on trusting the interface |
| Default recommendation | Preferred whenever available | Use only with trusted, audited protocols |
| Smart contract coverage | Depends on descriptor availability | Works on any contract, decoded or not |
| Developer requirement | Requires submitting an ERC-7730 descriptor | No extra work required |
Clear Signing vs. EIP-712
People frequently confuse these two, but they solve different problems.
EIP-712 standardizes how structured off-chain messages, like permit signatures, get formatted and signed. It defines the data structure itself.
ERC-7730 and Clear Signing define how that data, structured or not, gets translated into a readable summary for you. A permit signed under EIP-712 can still be rendered through a Clear Signing descriptor, so the two standards work together rather than compete.
What Information Does Clear Signing Show?

A properly attested descriptor typically surfaces:
- Recipient address or name
- Token and exact amount
- Network and protocol
- Contract name and function being called
- Gas cost
- Approval, permit, or deadline details
- Context for NFT mints, swaps, bridges, and staking actions
Which Wallets Support Clear Signing?
Adoption is active but uneven as of July 2026. The public registry shows 51 protocols and 380 descriptors (snapshot June 30, 2026). Confirmed backers and early implementers include:
- Ledger Live, with the deepest native integration
- MetaMask
- Trezor
- Fireblocks
- WalletConnect, which extends support across many connected wallets
- Keycard
- Ambire and Gemini (live support)
This list is expanding. Check each wallet’s current documentation before assuming full coverage, since support depends on which descriptors each wallet chooses to pull from the registry.
Which Organizations Are Behind the Standard?
Beyond the wallets, the working group includes named contributors: ZKnox, Sourcify, Cyfrin, Zama, and Argot, alongside Ledger and the Ethereum Foundation as co-stewards. This breadth of independent involvement is part of what makes the registry credible.
Which Blockchains Support Clear Signing?
Coverage centers on Ethereum mainnet and its major EVM-compatible networks. Support depends on wallet and dApp adoption per chain, not just technical compatibility.
Networks with active or growing support include Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, Scroll, Linea, and zkSync. ERC-7730 V2, released in April 2026, specifically expanded cross-chain descriptor coverage.
Which Ledger Devices Support Clear Signing?
Support depends on running current firmware and an updated Ethereum app. Older firmware versions will not decode newer descriptors correctly.
How to Enable Clear Signing on Ledger
Prerequisites:
- Latest Ledger device firmware
- Current version of Ledger Live
- Updated Ethereum app on your device
- A wallet or dApp that supports Clear Signing
Steps:
- Connect your Ledger device and open Ledger Live.
- Open the Ethereum app on the device itself.
- Initiate your transaction from a supported wallet or dApp.
- Review the readable summary shown on your device screen.
- Confirm the details match your intent, then approve.
If no descriptor exists yet for a contract you are interacting with, you will still see a raw, undecoded prompt. This remains common for newer or niche protocols in mid-2026.
How Developers Can Add Clear Signing to Their dApps
Getting your contract covered involves a defined workflow, not a one-time submission.
- Write an ERC-7730 JSON descriptor for your contract’s functions.
- Test it using Ledger’s open-sourced Builder, Linter, Tester, and Analyzer tools.
- Submit the descriptor to the clearsigning.org registry.
- Request attestation from an independent auditor under ERC-8176.
- Monitor which wallets pick up and display your descriptor.
When Will You Still See Blind Signing?
Coverage gaps remain common. You are most likely to hit blind signing prompts on:
- Unsupported or newly launched dApps
- Experimental or unaudited protocols
- Unknown or unverified smart contracts
- Legacy applications that were never updated
- Custom or one-off contracts without a submitted descriptor
Is Blind Signing Ever Safe?
Sometimes it is unavoidable, but treat it as a higher-risk exception, not a default. Reduce your exposure by combining these conditions:
- You trust the specific protocol and have researched it independently
- You verified the URL character by character
- You are testing with a small transaction amount first
- Your firmware and wallet software are fully updated
- The protocol has a public audit history
Common Clear Signing Errors
| Error | Likely Cause | Fix |
| Transaction cannot be decoded | No descriptor submitted for this contract | Proceed with caution or contact the dApp developer |
| Metadata unavailable | Descriptor exists but wasn’t pulled by your wallet | Check for a wallet software update |
| Unknown contract | Contract not yet indexed by the registry | Verify manually before proceeding |
| Unsupported wallet | Your wallet has not implemented ERC-7730 | Switch to a supported wallet if security is a priority |
| Outdated firmware | Device software behind current release | Update through Ledger Live |
| Ethereum app outdated | App version doesn’t support current descriptors | Update via Ledger Live’s Manager |
Security Best Practices
- Never approve a transaction you do not fully understand.
- Read every screen on your hardware device, not just the wallet interface.
- Stick to dApps with an established track record.
- Keep firmware and wallet apps updated at all times.
- Revoke token approvals you no longer use.
- Verify URLs directly rather than clicking links from messages or social media.
- Prefer attested descriptors over unattested ones when your wallet shows the distinction.
- Test new protocols with small amounts before committing larger funds.
Clear Signing Limitations
Clear Signing significantly reduces risk, but it does not eliminate it. Keep these limitations in mind.
- Coverage depends entirely on developer adoption of ERC-7730.
- Descriptor quality and attestation coverage are still expanding.
- Legacy and experimental contracts often remain uncovered.
- Complex, batched, multicall transactions are harder to summarize clearly.
- The ecosystem-wide standard is only a few months old as of this writing, so expect rapid changes.
Future of Clear Signing

Adoption will likely keep expanding through the rest of 2026 as more wallets integrate ERC-7730 and ERC-8176. The Ethereum Foundation’s Trillion Dollar Security Initiative continues to steward the registry directly.
Expect continued cross-chain expansion, deeper WalletConnect integration, and growing institutional interest tied to the attestation layer. Longer term, the standard is positioned to extend into account abstraction as that infrastructure matures.
Frequently Asked Questions
What is Clear Signing on Ethereum?
It is a standard that displays transaction details in plain language before you sign, instead of raw encoded data.
Is Clear Signing a Ledger feature or an Ethereum standard?
Both, historically. Ledger built it first, then transferred governance to the Ethereum Foundation in May 2026, making it an open, wallet-agnostic standard.
What is ERC-7730?
The JSON-based format that defines how a smart contract’s functions get translated into readable descriptions.
What is ERC-8176, and how is it different from ERC-7730?
ERC-8176 is the attestation layer that lets auditors verify an ERC-7730 descriptor is accurate, rather than just readable.
Is Clear Signing mandatory?
No. Adoption depends on individual wallets and dApp developers choosing to support it.
Does Clear Signing eliminate blind signing entirely?
No. You will still encounter blind signing on contracts without a submitted or attested descriptor.
Which wallets support Clear Signing right now?
Ledger Live, MetaMask, Trezor, Fireblocks, WalletConnect, Ambire, Gemini, and Keycard, with more expected to follow.
Does MetaMask support Clear Signing?
Yes, MetaMask is listed among the standard’s backers.
Is ERC-7730 an official Ethereum standard?
Yes. It is an Ethereum Improvement Proposal (currently in Draft status) that forms the core of the Clear Signing standard now governed and stewarded by the Ethereum Foundation.
What happens if a transaction has no descriptor yet?
Your wallet will typically fall back to a raw, undecoded blind signing prompt.
Does Clear Signing work on every blockchain?
No. Coverage depends on chain and wallet support, though it currently spans Ethereum and several major EVM networks.
Can scammers bypass Clear Signing?
They can still target contracts without an attested descriptor, which is why attestation coverage matters as much as descriptor availability.
Conclusion
Clear Signing addresses one of crypto’s oldest and most expensive weaknesses: approving transactions you cannot actually read. As of May 2026, it stopped being a Ledger-only feature and became shared Ethereum infrastructure, built on ERC-7730 and ERC-8176.
Use Clear Signing whenever it is available to you, and treat blind signing prompts as a signal to slow down and verify manually. Adoption is still expanding, so check your wallet’s documentation regularly as coverage grows through the rest of 2026.
Sources & References
- Ethereum Foundation – Clear Signing Announcement (12 May 2026)
https://blog.ethereum.org/2026/05/12/clear-signing-announcement - ERC-7730: Structured Data Clear Signing Format
https://eips.ethereum.org/EIPS/eip-7730 - Clear Signing Official Site & Registry
https://clearsigning.org/
Ecosystem data: https://clearsigning.org/ecosystem/ - ERC-8176: Integrity Verification for ERC-7730
https://ethereum-magicians.org/t/erc-8176-integrity-verification-for-erc-7730/27911 - Chainalysis – 2025 Crypto Theft Reaches $3.4 Billion
https://www.chainalysis.com/blog/crypto-hacking-stolen-funds-2026/ - Ledger Clear Signing Developer Tools (open-source)
https://github.com/LedgerHQ/clear-signing-erc7730-developer-tools - Ethereum Foundation – Trillion Dollar Security Initiative
https://blog.ethereum.org/2025/05/14/trillion-dollar-security - ERC-7730 Clear Signing Metadata Registry (GitHub)
https://github.com/ethereum/clear-signing-erc7730-registry
Disclaimer
This article is for educational and informational purposes only and does not constitute financial, investment, or security advice. While Clear Signing greatly improves transaction transparency and reduces the risks of blind signing, no technology can eliminate all security risks. Always carefully review every transaction detail on your device, use trusted wallets and hardware, and do your own research before approving any transaction. Cryptocurrency transactions involve a substantial risk of loss.