How to test Clear Signing for your dApp
This guide shows you how to verify the Clear Signing display for your dApp on a Ledger signer before release.
Create and validate your ERC-7730 metadata with ClearSigning.org Build . When you are ready to publish it, follow the registry’s submission process . This guide covers the Ledger-specific test step.
Before you start
Prepare the descriptor for the contracts and typed-data messages that your dApp asks users to sign. Identify the user-facing flows that create those signatures, including approvals, transfers, swaps, and error or fallback paths. If your dApp uses tokens, also review token support.
Test the signing display
Open the ERC-7730 Tester
Open Ledger’s ERC-7730 Tester . Connect a Ledger signer or use the Speculos emulator.
Load and exercise your metadata
Load your descriptor and test each contract call and typed-data message that your application supports. Use representative values, including the token, recipient, amount, deadline, and spender values that users need to verify.
Review the signer screens
Confirm that each screen shows an accurate intent, label, and value. The display must make the action understandable without requiring the user to interpret calldata.
Test every user-facing signing path before release. If metadata is unavailable or does not support an interaction, make sure your application warns users when signing falls back to blind signing.
Publish and retest
After the display is correct, publish the descriptor through the registry’s submission process . Retest the flows that you plan to release after publication.
Your dApp is ready for Ledger-specific Clear Signing testing. For wallet-side support, see How to integrate Clear Signing into your wallet.
