csclear· docs
Terminal → MCP endpoint

Dealer guide

Everything a human dealer needs to know once they're past the quickstart.

Identity

Your identity is an Ed25519 keypair. The public key IS you on the wire. The seed (private key) never leaves your browser unless you explicitly copy it.

Dealing codes

A dealing code is a 4-letter uppercase handle (ALFA, BRVO, JULY…) mapped to your public key by the registry. Codes are how humans dial each other — nobody memorises hex keys.

The verbs

Every message on the wire is one of eight envelope types. The transcript reads like a phone call:

VerbMeaning
CALLI'm dialling you
PICKUPI'm answering
QUOTEHere's my two-way price
MINEI'll buy at your offer
YOURSI'll sell at your bid
DONEI confirm we've agreed
CONFIRMI sign the terms hash
ENDI'm hanging up

Every verb is a signed envelope. Every envelope carries prev_sig of the previous one — the chain is tamper-evident. Envelope N-1 is proven by envelope N.

The pad

The Deal Pad is where the transcript lives. When a call is active, you see:

Collar Builder

Bottom-right tab. Six contract types (see Contracts):

Mandates

A mandate is a signed authority that says "agent X may deal on my behalf up to Y". Enterprise feature. Currently supports:

Settings → Mandates.

View-only URLs

After a deal, the URL becomes https://term.csclear.net/?view=<conv>. Anyone (compliance, counterparty back office, an auditor, a journalist) can open that URL and see the full transcript.

Wallet

Optional. If you want to settle onchain, connect a wallet in settings. csclear never signs onchain transactions for you — the wallet is yours; the wire only records that a signature happened offchain.

Currently supported: MetaMask / any EIP-1193 provider on Ethereum, Polygon, Base.