ClearSign docs

How it works

Most multisig tools show signers a transaction blob and ask them to approve. ClearSign flips that — the proposal is written in plain English first, cryptographically locked, and only then submitted to Squads for on-chain execution.

Web app

The web app lives at app.clearsign.fun/create. Six sections accessible from the left sidebar.

Connect your wallet

Click Connect wallet on any page. ClearSign supports Phantom, Backpack, Solflare, and any wallet that implements the Solana wallet standard. Sessions are stored in a signed HTTP-only cookie — no private key ever leaves the browser.

Roles

Import a Squads multisig

If your team already has a Squads v4 multisig, paste the vault PDA in Members → Import multisig. ClearSign fetches the member list on-chain and links the vault to your team so you can create proposals and execute transfers from the existing vault.

Creating proposals

Go to Proposals in the sidebar. The workbench has two panels — the form on the left, and the locked preview on the right.

Templates

Save any proposal as a template for recurring payments — payroll, vendor invoices, grants. Templates are stored locally and load with one click to pre-fill the form.

Import and verify

Switch to Import & Verifyto paste a proposal JSON from another ClearSign user. The app recomputes the SHA-256 hash client-side and confirms it matches the embedded hash before loading. If the hash doesn't match, the proposal was tampered with.

Signing & executing

Share the /p/[token] link with your signers. They only need the link and a Solana wallet — no workbench login required.

What signers see

The share page shows the proposal in plain English — title, amount, recipient, threshold, expiry countdown, and a policy review checklist. The SHA-256 hash is displayed prominently. Signers can download the raw JSON and verify the hash independently.

Executing the transfer

Once threshold is met, the Execute Transfer panel appears for teams with a Squads multisig connected.

Audit trail

Every event — created, signed, approved, executed — is recorded with wallet addresses and timestamps. Executed transfers link directly to Solscan.

Policy & rules

Admins and Founders configure spending rules in the Policy tab. Rules are enforced at proposal creation and shown in the policy review checklist on every share page.

Security model

SHA-256 hash locking

The proposal body is canonicalized — keys sorted alphabetically, no whitespace — before hashing. Any two users computing the hash of the same proposal get the same result. If a single character changes after creation, the hash changes and import verification fails.

Anomaly detection

ClearSign monitors signing patterns and flags suspicious behavior in the policy review checklist.

What ClearSign cannot do

ClearSign does not custody funds, hold private keys, or move money unilaterally. Funds stay in the Squads vault at all times. ClearSign only submits a transaction to Squads when a signer explicitly clicks Execute Transfer with their wallet connected.

CLI reference

For teams that want to create and verify proposals outside the browser. Every command runs locally — no keys ever leave the machine.

$ npm install -g clearsign

SDK

Embed ClearSign proposal verification inside your own treasury app or execution service.

$ npm install clearsign

buildProposal

import { buildProposal } from "clearsign";

const proposal = await buildProposal({
  title:      "Monthly Treasury Rebalance",
  asset:      "USDC",
  amount:     150_000,
  to:         "vault.sol",
  ttlSeconds: 1800,
  signers:    ["alice.sol", "bob.sol"],
  threshold:  2,
});

// proposal.hash      — SHA-256 of canonical JSON
// proposal.expiresAt — ISO timestamp

ExecutionGate

import { ExecutionGate } from "clearsign";

const gate   = new ExecutionGate({ policy: "./policy.json" });
const result = await gate.check(signedProposal);

if (!result.ok) throw new Error(result.errors.join(", "));
await execute(signedProposal);

Proposal schema

Every proposal is a deterministically serialized JSON object. The SHA-256 hash is computed over the canonical form — keys sorted alphabetically, no whitespace.

{
  "version":      "clearsign-web/v1",
  "title":        "Pay auditors",
  "description":  "Transfer 10,000 USDC for Q2 security audit.",
  "action":       "transfer",
  "chain":        "solana:mainnet",
  "amount":       { "value": "10000", "asset": "USDC" },
  "recipient":    "auditors.sol",
  "recipientName":"Auditors",
  "requester":    "ops-team",
  "threshold":    { "required": 2, "total": 3 },
  "signers":      ["alice.sol", "bob.sol", "carol.sol"],
  "createdAt":    "2026-06-01T10:00:00.000Z",
  "expiresAt":    "2026-06-01T10:30:00.000Z",
  "proposalHash": "8f3c9a2b4d1ef7a03c..."
}