Implementation Overview
By following this guide, you’ll create and submit metadata files that allow users to see clear, human-readable information when signing transactions or messages from your dApp on a Ledger device.
Currently, Clear Signing implementation is supported for EVM chains only. Support for other protocols is in development.
Task 1: Determine Which Metadata Files You Need
| Your Use Case | Required Metadata | Tools Available |
|---|---|---|
| Smart Contract Transactions Users interact with your smart contract functions | Smart Contract metadata |
|
| EIP-712 Structured Data Users sign structured messages from your dApp | EIP-712 metadata |
|
| Both Transaction Types Users interact with contracts and sign structured data | Both metadata types in separate files | Mixed approach needed |
Regardless of which type of metadata file you create, the submission process to the registry is the same. All metadata files are submitted to the same repository.
Task 2: Create Your Metadata Files
Option A: Create Smart Contract Metadata
- Recommended: Use the ERC-7730 JSON Builder for a guided experience
- Alternative: Create the file manually following the Smart Contract Metadata guidelines
Option B: Create EIP-712 Metadata
Create your metadata file manually using the EIP-712 template
Option C: Create Both Types (if needed)
Follow both Option A and Option B to create separate metadata files for each purpose.
Task 3: Test the validity of the file
Use the JSON schema validator to check that your metadata file complies with the ERC-7730 standard before submission.
Learn how to test your metadata file →
Task 4: Submit to the Registry
Submit your validated metadata file to the Clear Signing Registry for inclusion in the ecosystem.
