ClearSign

Review before signing

ClearSign for Solana & AI Agents

Readable signing for Solana wallets.

You sign the intent. Not raw bytes.

Install Command

$curl -fsSL https://clearsign.fun/setup.sh | bash

Chrome extension • SDK • OWS-compatible

SHA-256 locked•30-minute TTL•Policy gates

Coverage

One signing layer. Every surface.

ClearSign sits between intent and execution — securing every signing flow whether you're using the CLI, SDK, MCP, or Chrome extension.

Wallet Transfers
Token Swaps
Multisig Ops
AI Agent Actions
Treasury Flows
ClearSignClearSign
CLI
TypeScript SDK
MCP Server
Chrome Extension
Claude Skill

Live Demo

See ClearSign in action.

Single-signer approvals, token swaps, and multisig coordination — all hash-locked and policy-gated before anything moves.

ClearSign Wallet

ClearSign Wallet

Low risk

Send USDC to alice.sol

alice.sol · 9xQe...aWTD
Allowed
Debit-250.00 USDC

5N7K...Rk42

Credit+250.00 USDC

alice.sol

Expires
30m 00s
Wallet
generating
Hash
...

Token accounts

5N7K...Rk42Source USDC ATADebitAllowed
9xQe...aWTDDestination USDC ATACreditAllowed

Programs invoked

Token...kegCToken ProgramAllowed
11111...1111System ProgramAllowed
Known recipientPolicy ok
Locked hash
ReviewReady

ClearSign Wallet

Jupiter route

Low risk

Swap USDC for SOL

Minimum output locked
Allowed
Debit-125.00 USDC

USDC vault

Credit+0.53 SOL

Expected SOL

Expires
30m 00s
Wallet
generating
Hash
...

Token accounts

EPjFW...DJPZSource USDC ATADebitAllowed
7dLd1...Rx9fJupiter USDC vaultAMM poolAllowed
So111...1112Wrapped SOL accountCreditAllowed

Programs invoked

JUP6L...3gA4Jupiter Aggregator v6Allowed
Token...kegCToken ProgramAllowed
AToken...zSkATA ProgramAllowed
Compu...dgetCompute BudgetPriority feeAllowed
Programs decodedMin output
Locked hash
ReviewReady

ClearSign Multisig

Monthly Treasury Rebalance

2/2Threshold met
Sending-150,000 USDC

From treasury vault

→
Tovault.sol

3kDs...mN91

Description
Move 150,000 USDC to strategy vault
Expires
28m 14s
Hash
sha256:8f3c9a2b4d1ef7a03c...f47e

Signers — 2 of 3 required

alice.sol5N7K...Rk42
Approved3m ago
bob.sol9xQe...aWTD
Approved1m ago
carol.sol7mBn...3Pq1
Pending

Execution Gates

Hash verifiedTTL valid2/2 collected

Review as carol.sol

What signers actually see.

Typical wallets ask you to approve raw bytes. ClearSign surfaces the proposal itself — amount, recipient, expiry, and a hash that locks every field.

Before · Typical Wallet

Send USDC

Phantom-style transfer prompt

You're sending150,000 USDC≈ $150,000.00
To
9aRzBMnGx8KP2wL4dHqJe3vN…XbQunverified
Network fee
~0.000005 SOL
Requested by
treasury-ops.app
First time sending to this address

The wallet can't tell you why this transfer was requested, whether it matches what was reviewed, or whether other signers approved it.

  • No intent / description
  • Signature valid forever — no TTL
  • No tamper-evident hash
  • No multi-sig coordination
  • No policy check
  • No anomaly detection
  • No signer audit trail

You have no way to verify this matches what was reviewed.

Signing blind
After · ClearSign

Monthly Treasury Rebalance

Hash-locked, time-bound, human-readable

Amount−150,000 USDC← this amount will move
From
treasury.sol 5YNm…Gx8K
To
ops-multisig.sol 9aRz…Hk2Pverified
Expires
28m 14s · void after
Hash
sha256:8f3c9a2b…f47e
  • Amount & recipient visible
  • Hash-locked proposal
  • 30-minute TTL
  • Tamper detection
  • Policy gate passed
  • Anomaly check clean
  • Signer audit trail
  • Multi-sig coordination
  • Known recipient verified

If any field changes, the hash changes and the signature is invalid.

✓ Intent verified

Why ClearSign

Built for the teams that move real capital.

Treasury desks, autonomous agents, and multisig coordinators all share the same vulnerability: approving actions they cannot meaningfully inspect. ClearSign closes that gap.

Readable proposalsSigner-separated reviewHard execution boundaries
01

Human-readable

Review what moves

Every approval starts with a proposal people can actually read before a signature is produced.

02

Remote signers

Keep custody separate

Proposal JSON moves between machines. Private keys do not.

03

Hard stops

Expire and block bad flows

TTL, anomaly checks, and execution gating stop stale or suspicious approvals.

  • Proposals that have expired
  • Sudden large transfers outside historical patterns
  • Sends to new or untrusted addresses
  • Any mismatch between the reviewed hash and final payload

ClearSign turns trust the signer into trust the verified intent.

Market Signal

The internet capital markets need a signing standard.

$3B+lost yearlyto drainers
10M+Solanawallets
$11.8MBlowfishacquisition

Flow

Three steps between request and execution.

The workflow is deliberately simple: create readable intent, get human or agent review, then enforce every safeguard before execution.

Single invariantThe proposal stays human-readable, hash-locked, and time-bound from the first moment until final execution.

01

Intent locked

Build a proposal

Create intent with title, description, asset, payload, signer set, and expiry.

Readable JSON with a deterministic hash and explicit expiry.

02

Review distributed

Share for review

Signers import the same proposal, verify the hash, and approve from their own machines.

Approvals happen on separate machines without moving private keys.

03

Execution constrained

Verify before execution

ClearSign collects signatures, runs anomaly checks, and blocks anything expired or unsafe.

The gate rejects stale, altered, or suspicious actions before they move.