Clear Sign Display Guide

Reference for rendering Gatekeeper display data to Clear Sign in your application.

Overview

Gatekeeper returns a resolution object containing structured data for rendering transaction details to users.

This page covers the display schema and how to render each field type.

Response Structure

The resolution is returned as part of the evaluation response:

{
  "data": {
    "action": "eth_sendTransaction",
    "whitelisted": true,
    "resolution": {
      "display": { 
        "intent": "Approve", 
        "interpolatedIntent": "Approve Uniswap V2 Router to spend 1000000 USDC", 
        "interactWith": { 
          "contractName": "USDC Token", 
          "contractAddress": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48", 
          "contractChainId": 1
        }, 
        "fields": [ ... ], 
        "requiredFields": [ "Amount", "Spender" ] 
      }, 
      "decoding": {
        "hexSignature": "0x095ea7b3",
        "descriptor": { ... }
      },
      "policyEvaluation": {
        "expectedBehavior": true,
        "matchedPresets": [ ... ]
      },
      "resolutions": null
    },
    "protocolPresets": [ ... ],
    "attestation": { ... }
  }
}

Resolution Schema

Display Schema

Rendering Guide

To display the Clear Sign data, follow a few best practices.

1. Display the Context - which contract/protocol is being interacted with?
2. Display the Intent - what is the transaction doing?
3. Display the individual fields - what are the values of each field?

Rendering the Context

This data is returned in the resolution.display.interactWith field.

It will be null for personal_sign messages.

Rendering the Intent

Display the intent using this priority order:

1. interpolatedIntent — Human-readable summary with values (e.g., "Approve Uniswap to spend 1000 USDC")
2. intent — Static action label (e.g., "Approve")
3. Fallback — Show "Unknown Operation" warning; clear sign not available.

NOTE: intent can be a string or an object where keys are labels.

Field Formats

Each field in fields[] is either a terminal field (has format) or a nested field (has fields).

tokenAmount

Displays a token amount with proper decimal formatting.

addressName

Displays an Ethereum address with contextual name resolution.

date

Displays a timestamp.

raw

Displays unformatted values for miscellaneous data.

calldata

Displays raw transaction calldata (hex-encoded).

Nested Fields

Fields can contain sub-fields for grouped data. A nested field has fields instead of format.

Nested Resolutions (Batch Transactions)

For batched transactions (multicalls), resolution.resolutions contains an array of nested resolution objects. Each has the same structure as the top-level resolution.

const isBatch = resolution.resolutions && resolution.resolutions.length > 0

{
  "resolution": {
    "display": {
      "intent": "Multicall",
      "interpolatedIntent": null,
      "interactWith": {
        "contractName": "Morpho Bundler 3",
        "contractAddress": "0x6566194141eefa99Af43Bb5Aa71460Ca2Dc90245"
      },
      "fields": [ ... ]
    },
    "resolutions": [
      {
        "display": {
          "intent": null,
          "interpolatedIntent": "Approve Gauntlet USDC Prime to spend 100 USDC",
          "interactWith": { "contractName": "USDC Token" },
          "fields": [ ... ]
        }
      },
      {
        "display": {
          "intent": "Deposit",
          "interpolatedIntent": "Deposit 100 USDC against gtUSDC for you",
          "interactWith": { "contractName": "Gauntlet USDC Prime" },
          "fields": [ ... ]
        }
      }
    ]
  }
}

Full Example: Morpho Multicall

A complete rendering example using the Morpho BundlerV3 multicall.