---
title: Validate & Submit
category: how-to
---

# How to validate and submit your descriptor

This guide shows you how to validate your descriptor, preview it on a Ledger signer, and submit it to the registry so your protocol's transactions become Clear Signed.

Before you start, make sure you have created your descriptor with the [JSON Builder](/docs/clear-signing/for-dapps/json-builder) or [written it manually](/docs/clear-signing/for-dapps/manual-implementation).

## Validate your descriptor

Validate your file against the ERC-7730 schema before submitting, to catch errors early.

### CLI tool

### Install the validator

```bash
pip install erc7730
```

> **Note:** Requires Python 3.12 or higher.

### Validate your file

```bash
# Validate a single file
erc7730 lint your-descriptor.json

# Validate multiple files
erc7730 lint registry/**/eip712-*.json registry/**/calldata-*.json
```

### Auto-format your file

```bash
erc7730 format your-descriptor.json
```

### Node.js (CI)

To validate in CI, run the same `erc7730` CLI, or check your descriptor against the ERC-7730 JSON schema with any JSON Schema validator. Download the schema from the registry's [`specs/` directory](https://github.com/ethereum/clear-signing-erc7730-registry/tree/master/specs), then validate with [Ajv](https://ajv.js.org/):

```javascript
import Ajv from 'ajv';
import { readFileSync } from 'node:fs';

const schema = JSON.parse(readFileSync('./erc7730-v1.schema.json', 'utf8'));
const descriptor = JSON.parse(readFileSync('./your-descriptor.json', 'utf8'));

const validate = new Ajv({ allErrors: true }).compile(schema);

if (!validate(descriptor)) {
  console.error(validate.errors);
  process.exit(1);
}
console.log('Descriptor is valid');
```

> **Note:** Install Ajv with `npm install ajv`.

### Common validation errors

- **Missing required fields** — the file must include the `context`, `metadata`, and `display` sections, plus the top-level `$schema` field.
- **Unaccounted parameters** — every function parameter must appear in either `fields` or `excluded`.
- **Incorrect format structure** — format types must match the field's data type. For example, `tokenAmount` requires either `tokenPath` or `token` in `params`. See the [format types reference](/docs/clear-signing/reference/erc7730-reference#format-types).
- **Incorrect chain ID** — verify each deployment's `chainId` against the actual deployment. Use [ChainList](https://chainlist.org) to look up IDs (1 for Ethereum mainnet, 137 for Polygon, 42161 for Arbitrum).
- **Invalid path expression** — check the `#`, `$`, and `@` roots against the [path system reference](/docs/clear-signing/reference/erc7730-reference#path-system).

## Test the display on a signer

Before submitting, preview how your descriptor renders on a real device. The [ERC-7730 Tester](https://app.devicesdk.ledger.com/clear-signing-tools) injects your descriptor and displays the resulting fields against a live Ledger signer or the Speculos emulator, so you can confirm each label and value before opening a pull request.

## Submit to the registry

Once your descriptor passes validation, submit it as a pull request to the registry.

### Fork and clone the registry

Fork [github.com/ethereum/clear-signing-erc7730-registry](https://github.com/ethereum/clear-signing-erc7730-registry), then clone your fork:

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

### Add your descriptor

Place your file in a directory named after your dApp, using lowercase and hyphens (`uniswap-v3/swap-router.json`, not `UniswapV3/file1.json`):

```bash
mkdir -p registry/your-dapp-name
cp /path/to/your-descriptor.json registry/your-dapp-name/descriptive-name.json
```

### Open a pull request

Commit, push to your fork, and open a pull request describing your protocol, the contracts covered, and any notable configuration choices.

> **Note:** The registry runs automated checks (schema, linting, ABI and deployment consistency) before a maintainer review. For the full, ecosystem-wide submission and review process — including auditor signals and attestations — see [clearsigning.org/build](https://clearsigning.org/build).

If a reviewer requests changes, push to the same branch and the pull request updates automatically. Submissions are most often rejected for:

- Contract addresses that do not match the claimed protocol
- Display labels that are misleading or incomplete
- Schema violations not caught by local validation

## After your pull request merges

Once merged, your descriptor becomes available in  (after the next scheduled update), in all wallets that support the Clear Signing standard, and through the public registry API. Users signing transactions through your protocol then see human-readable details instead of raw hex.

## Get help

- **[Registry issues (GitHub)](https://github.com/ethereum/clear-signing-erc7730-registry/issues)**
- **[Discord community](https://discord.ledger.com)**
