Clear Signing
Signing requests are written for wallets and smart contracts, so the raw data can be difficult to understand. Clear signing turns a supported request into a readable summary of the action you are being asked to approve.
When Cloaked shows Checked with clearsigning.org, Cloaked has matched the request against a clear-signing definition it accepts before showing the summary. The label refers to the open clear-signing standard and registry. It is not an endorsement of the app, contract, or transaction by clearsigning.org.
What the check means
The check means Cloaked confirmed that:
- the contract, network, request type, and field order match the published definition;
- the recipient, amount, token, fees, and other displayed values were derived from the exact request;
- any account setup included in the request matches Cloaked's expected account setup; and
- the request has not changed between review and signing.
The info icon beside the check gives a short explanation. The definition sources Cloaked uses are listed below.
What the check does not mean
Clear signing explains what a request asks you to sign. It does not prove that a contract is bug-free, confirm that the app is trustworthy, or guarantee the transaction's outcome. Definitions and software can also contain errors, so you should still review the displayed values.
Cloaked may also simulate a transaction to estimate what it is likely to do. These checks answer different questions:
| Check | What it tells you |
|---|---|
| Clear signing | Whether Cloaked matched the exact request to a definition it accepts |
| Simulation | An estimate of asset changes based on the contract state at the time it was run |
Actual onchain transfers may differ from the simulation if the contract state changes before the transaction is executed. Neither check is a substitute for reviewing the recipient, token, amount, network, and fees yourself.
If the check is unavailable
If Cloaked cannot find or validate a suitable definition, the clear-signing check is not shown. You can still review the decoded request and any available simulation before deciding whether to continue. The absence of the check does not by itself mean that a request is unsafe.
If a checked request changes after you review it, Cloaked blocks signing. If a quote expires or has to be replaced, you must review the replacement before confirming it.
How Cloaked verifies definitions
Cloaked uses clear-signing definitions based on ERC-7730, an open format for describing contract calls and typed messages in a human-readable form. These include definitions from the Ethereum Clear Signing Registry.
The registry is open to contributions, so publication alone does not mean that a definition is trusted or approved. Cloaked decides which definitions it accepts and uses a fixed, reviewed version. Your device then confirms that the definition matches the exact request before showing the check.
Definitions used by Cloaked
A checked request can combine several sources. For example, Cloaked may check the outer account request, the contract call inside it, and the account implementation separately. Every applicable part must match before the check is shown.
Cloaked currently uses:
- fixed versions of definitions from the Ethereum Clear Signing Registry;
- a pinned Porto signing definition, which has been submitted for upstream review; and
- the pinned Ithaca account implementation used for Cloaked account setup.
Cloaked does not fetch changing definitions from GitHub while you are reviewing a request. Registry updates are pinned, tested, and released with the application.