API co-signer

The last word stays on your side

The co-signer runs on a machine you control. Chainvara asks it before every signature, and it answers according to your own rules: amounts, destinations, daily budgets, or a person clicking Approve. It holds your share of every MPC and split key, and decodes every transaction itself before adding its signature.

chainvara-cosigner · your server · listening

t-1041 2,500 USDC → trusted address · auto-approved

t-1042 48,000 USDC → new address · waiting for a person

t-1043 destination differs from approval · refused

t-1044 0.8 BTC → cold storage · approved by Marie

t-1045 daily budget would be exceeded · refused

holding: 4 MPC shares · 2 split-key halves▍

What makes it safe

Core

Your rules, enforced remotely

Approve automatically under a limit, only to known destinations, within a daily budget, or wait for a person.

Your own logic, called first

Point the co-signer at your own server: it sends every transfer for your code to approve or reject, signed both ways. Down, slow or forged answers approve nothing.

Holds your key shares

Your share of every MPC wallet (FROST and threshold ECDSA) and half of every split key stay on your machine, encrypted at rest, with encrypted backups.

Verifies every transaction itself

It decodes each chain's own format — EVM, Bitcoin, Litecoin, Dogecoin, Solana, Tron, XRP Ledger, Stellar, Aptos, Sui, TON — recomputes the hash it signs, and refuses any other recipient, amount, token, fee or extra instruction.

No double payment

One approval can only ever be signed with one nonce, sequence number or set of coins: a retry is possible, a second payment is not.

No open port

By default it connects out to Chainvara over HTTPS; nothing on your network needs to accept incoming connections.

Signed both ways, one verifiable file

Every request and answer is HMAC-signed with timestamps; the single Node.js file is published with its SHA-256 on GitHub.

Install with npm, verify its origin

npm install -g @chainvara/cosigner: no dependencies, nothing runs at install, and every version carries a provenance attestation tying it to its public source commit. Only our release workflow can publish it — no npm token exists.

How it works

  1. 1

    Install and start

    npm install -g @chainvara/cosigner on a server or an always-on PC (or download the single file), then run it: it connects out to Chainvara.

  2. 2

    Connect it

    Pair it in Developers → API co-signer with its shared secret.

  3. 3

    Set your rules

    Limits, allowed destinations, budgets, fee caps, and which transfers need a person.

Install and run (Node.js 20+)

npm install -g @chainvara/cosigner@1.2.3
npm audit signatures   # checks the provenance
chainvara-cosigner setup   # paste your co-signer secret
chainvara-cosigner serve

Works best with

Ready to see Chainvara in action?

Start free on test networks. Move to production when your controls are in place.