Build Clear Sign Metadata
Accessing the Builder
Visit the Tool Point your browser to the ERC-7730 JSON Builder at Kai-Sign enhanced builder: beta.kaisign.xyz.
Choose “I already have Clear Sign JSON file” (optional) If you’ve previously generated your metadata, click the “I already have Clear Sign JSON file” link to upload it directly.

Entering Contract Details
Select Network (chainId)
A dropdown lets you pick the blockchain for the metadata ChainID (e.g., Ethereum Mainnet, Arbitrum, etc.).
Input Contract Address or ABI
Paste your contract’s address (e.g.,
0x…) or the full ABI JSON.Click Submit

Operation Description (Legal Name & URL)
Input:
Legal Name: Your project’s legal entity (e.g., “MyDAO Foundation”)
URL: Link to your org’s website or Github

Defining Operations to “Clear Sign”
For each operation you want users to verify:
Confirm Operation
Click on the operation (e.g.,
transferOwnership) in the left-hand menu to add it.

Filling Out Metadata Fields
For each operation you selected, fill in these fields:
Operation Display Name / Intent
Input: A human-readable label, e.g., &#xNAN;“Transfer contract ownership to [address]”
Field: JSON-pointer to the argument.
Label : Display name for the parameter.
Required (
true): Wallets must show this field.Format (
addressName): Specifies it’s an address that should be name-resolved.Address Type (
["wallet","eoa"]):eoa: Externally Owned Accountwallet: Account controlled by the wallet software(Do not include
tokenorcollectionhere because this parameter expects a user address, not a token contract or NFT collection.)
Sources (
["ens"]):Only ENS is crypto-verifiable on-chain, so local sources (which malware could spoof) are omitted

Reviewing & Exporting
Review
Once all operations and parameters are defined, click Review.
The builder shows a preview of how it will look on a Ledger device.

Submit to reality.eth
Click Continue, Copy or Download the JSON file (Currently, you need to download the JSON file first before continue to verification).
Last updated