Submit your metadata file to the registry

To make your Clear Signing metadata available to all compatible wallets, submit it to the Clear Signing Registry.

Submission steps

Step 1: Fork and clone the registry repository

1. Navigate to the Clear Signing Registry
2. Click “Fork” to create your own copy
3. Clone your fork locally:

git clone https://github.com/YOUR_USERNAME/clear-signing-erc7730-registry.git
cd clear-signing-erc7730-registry

Expected result: You have a local copy of the registry with write access.

Step 2: Create your project directory and add your file

1. Create a directory for your dApp if it doesn’t exist:

mkdir -p registry/your-dapp-name

2. Copy your metadata file with a descriptive name:

cp /path/to/your-metadata.json registry/your-dapp-name/descriptive-name.json

Naming conventions:

• Use lowercase with hyphens: lending-pool-v2.json
• Describe the contract’s main function: token-swap.json, governance-voting.json
• Include version if applicable: uniswap-v3-router.json

Expected result: Your file is located at registry/your-dapp-name/your-file.json

Step 3: Commit and push your changes

git add registry/your-dapp-name/
git commit -m "Add metadata for [Your DApp Name] [Contract Function]"
git push origin main

Expected result: Your changes are pushed to your GitHub fork.

Step 4: Create a pull request

1. Go to your fork on GitHub
2. Click “Contribute” → “Open pull request”
3. Fill out the pull request template with:
   • Title: Add metadata for [Your DApp Name]
   • Description: Brief explanation of what contracts/functions your metadata covers

For detailed pull request requirements, see the repository README.

Expected result: Your pull request is created and visible in the main repository.

Step 5: Monitor the review process

After submission:

1. Automated checks will validate your file format and structure
2. Manual review will verify the metadata accuracy and completeness
3. Feedback may be provided via pull request comments

Troubleshooting

Pull request checks fail:

• Review the automated check logs for specific errors
• Common issues: file naming, directory structure, JSON formatting

Need help?

• Comment on your pull request for assistance
• Check existing pull requests for examples
• Refer to the repository documentation

Next steps

Once your metadata is merged:

• It becomes available to all compatible wallets
• Users will see clear signing information for your contracts
• Monitor for any issues or updates needed