Decoding (Clear Sign)

Transform raw transaction data into human-readable intents.

Overview

Raw blockchain transactions are opaque. A typical Ethereum DeFi transaction contains hex-encoded calldata that's meaningless to most users:

0x617ba037000000000000000000000000a0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
00000000000000000000000000000000000000000000000000000000000f4240
000000000000000000000000311c0d6b38cf9a544eb765ad4e1e345b3e24d0ca
0000000000000000000000000000000000000000000000000000000000000000

To ensure this opaque calldata does not include a malicious payload, it must be decoded & displayed in a human-friendly format.

ERC-7730: Clear Sign

ERC-7730 defines a standard metadata format for Clear Signing transaction calldata.

Gatekeeper: Clear Sign as a Service

Gatekeeper handles the complexity of Clear Sign so you don't have to.

Accelerates time-to-implement — Full ERC-7730 support without building custom resolution infrastructure. Submit a transaction, get structured display data back.

Descriptor verification — Validates descriptors against configured trusted registries. Only authentic, verified descriptors are used for decoding.

Automatic selection & resolution — Efficiently selects the correct descriptor. Resolves token metadata, formats amounts, and handles nested structures.

Attested output — Signs the renderable output with a configured attestation key, providing cryptographic proof of the decoding.

Production-ready — Decoding logic is thoroughly tested and audited by 3rd party.

Next Steps

• API Reference — Learn how to submit a transaction to the Gatekeeper API
• Display Guide — Schema reference and rendering patterns for building your UI