Skip to content

Clear Signing Playground

What would a wallet show you?

Paste a transaction from Ethereum, Base, Arbitrum One or OP Mainnet. Your browser formats it with the Clear Signing registry, the way a wallet that implements ERC-7730 does, beside the raw call the wallet is asked to sign.

What to read

Your browser reads the transaction from the chain's public RPCs and the registry from GitHub. Nothing is signed or sent, and what you look up stays out of this site's server.

How it works

Everything happens in your browser

The playground does what a wallet that implements ERC-7730 does before it asks you to sign: it finds the contract's descriptor in the Clear Signing registry and formats the call with it. This site only serves the page.

  1. The transaction

    Your browser asks the chain's public RPC nodes for the transaction: the contract it calls, the value it sends and its calldata. The examples carry their own transactions, so they need no RPC.

  2. The descriptor

    It looks the contract up by chain and address in the index of the Clear Signing registry, read from GitHub as it is now, and reads the ERC-7730 descriptor the index names, with the files it includes.

  3. The formatting

    Sourcify's clear-signing library, version 0.3.1, decodes the calldata and writes each value the way the descriptor says. A token amount needs the token's symbol and decimals, which your browser reads from the token's own contract.

  4. The coverage

    The page looks the contract up in the coverage tracker's report of 7 November 2026: its status, the descriptor the registry has for another of its deployments, and B3Pay's draft for it, when there is one.

Limits

What the playground does not claim

  • It does not check attestations. A wallet may show only a descriptor an auditor has attested under ERC-8176. The playground shows what the registry's descriptor says, attested or not, so a wallet you use may still show the raw call.
  • A near miss's preview is not coverage. When the registry describes a contract only at another deployment, the playground formats the call as if that descriptor listed this one too. No wallet does that: the protocol has to check that the descriptor fits, and add the deployment.
  • A draft's preview comes from the report. B3Pay's drafts are not on this site. A preview is one real call to the contract, as the draft rendered it when it was tested, and no wallet reads the draft yet.
  • Calls, not messages. The playground reads a transaction's calldata. Signed messages, such as EIP-712 permits and orders, are not read here.
  • Wallets decide. Each wallet chooses which registries and reviewers it trusts, and how it lays out a request, so what yours shows may differ from this page.
Get covered

Does your protocol's call show as raw data?

We write, test and submit descriptors. Tell us the chains, the addresses and the flows your users sign. The coverage tracker shows where your contracts stand today.