External Resources
Official resources, tools, SDKs, and standards for Clear Signing implementation. Use it as a reference index when you need a specific tool or specification while working.
Where to start
If you are new to Clear Signing, begin with the ERC-7730 Standard for the formal specification and the JSON Builder to generate your first metadata file. If you are integrating Clear Signing into a wallet, start with the Device Management Kit.
Core resources
ERC-7730 Standard →
Official Ethereum Improvement Proposal. The authoritative specification for the Clear Signing metadata format.
Clear Signing Registry →
The public registry of metadata files. Browse existing implementations and submit pull requests to add your protocol.
Tools
Use these tools during development to create and validate your metadata files before submitting to the registry.
JSON Builder →
Visual interface for generating metadata files. No coding required. Recommended for standard contracts with simple function signatures.
Python Validator (erc7730) →
Command-line tool for validating and formatting metadata files. Use this locally before opening a pull request. Requires Python 3.12 or higher.
ERC-7730 Tester →
Inject and preview ERC-7730 descriptors against a live Ledger signer or the Speculos emulator. Use this to verify your display configuration before submitting.
Developer SDKs
Use these SDKs if you are integrating Clear Signing into a wallet or building a signing interface.
Device Management Kit →
Ledger’s SDK for device interaction. Handles connection, transport, and automatic metadata fetching for Clear Signing.
Device Signer Kit (Ethereum) →
Ethereum-specific signer that enables Clear Signing when combined with the Device Management Kit.
Ledger Wallet (ledger-live) →
Source repository for Ledger Wallet. Reference this when adding token icons or contributing to the token database.
Supported Token List →
Ledger’s database of supported tokens. Check here before submitting a new token for display support.
Technical standards
These Ethereum standards are referenced by or required by ERC-7730.
EIP-155 →
Chain ID specification. Required by ERC-7730 for binding metadata to specific network deployments.
EIP-712 →
Typed structured data signing. Required by ERC-7730 for describing off-chain messages such as permits and orders.
ChainList →
Reference for EVM chain IDs. Use this when populating the
chainId field in your metadata’s deployments array.Etherscan API →
Fetch verified contract ABIs programmatically. Used as the ABI source URL in many registry metadata files.
Schema and validation
JSON Schema (v1) →
The ERC-7730 v1 JSON Schema file. Use this with AJV or any JSON Schema validator to check your metadata programmatically.
Registry Examples →
Browse real metadata files for major protocols including Uniswap, Aave, and 1inch. Useful as a reference when writing your own file.
