Skip to Content
📢 Breaking change: Applications using LedgerJS for transport implementation should migrate to the Device Management Kit (DMK). Learn more.

Clear sign your Earn smart contracts

Earn Live Apps must clear sign every smart-contract interaction they trigger: staking, unstaking, claiming rewards, delegating. This page shows how to do it with ERC-7730, the metadata-only standard supported by Ledger Wallet.

👉

Clear signing is a release blocker for Earn. A Live App with even one un-clear-signed call will not be approved.

Prerequisites

  • Your contract is deployed on an EVM-compatible mainnet.
  • You have the contract address and ABI.
  • You can open a pull request to ethereum/clear-signing-erc7730-registry, the public ERC-7730 registry that wallets fetch from.

Steps

Pick the right approach

Use ClearSigning.org Build  for the current ERC-7730 authoring, schema, validation, and registry-submission guidance. Then use How to test Clear Signing for your dApp to review the fields users see on a Ledger signer or Speculos emulator.

Describe each function in metadata

For the current schema and descriptor examples, see ClearSigning.org Build  and the registry examples . Each function your Earn Live App calls needs metadata.

Validate the file

Validate and submit your descriptor using ClearSigning.org Build  and the registry’s submission process .

Submit to the registry

Open a pull request following the registry’s submission process . After your submission is accepted, verify your Earn flows on a Ledger signer before release.

Non-EVM chains

ERC-7730 currently covers EVM-compatible chains only. If your Earn Live App stakes on a non-EVM chain (for example Cosmos, Solana, Cardano, Polkadot), get in touch with your Ledger contact during the integration review. Clear signing on those chains is handled outside this registry.

Common pitfalls

  • localhost: links in the file. A local validator URL has no place in a registry submission; remove it before opening the pull request.
  • Spelling mistakes in intent or label. They appear verbatim on the device screen, so misspellings ship straight to users.
  • Forgotten functions. If you ship a flow with five contract calls, the registry file must describe all five. Anything missing falls back to blind signing.

See also

Last updated on
Ledger
Copyright © Ledger SAS. All rights reserved. Ledger, Ledger Stax, Ledger Flex, Ledger Nano, Ledger Nano S, Ledger OS, Ledger Wallet, [LEDGER] (logo), [L] (logo) are trademarks owned by Ledger SAS.