Skip to main content

Multisig treasury

The multisig treasury is the shared pot of USDC of an organization that runs several agents. It holds most of the money, several people control it together, and the agent wallets of the organization are refilled from it. A single agent does not need one: fund its wallet directly.

  1. Signers' phones

    Each signer holds a passkey in the Keyban Signer app.

  2. Multisig treasury

    Holds most of the money. A move needs a threshold of signers.

  3. Agent wallets

    Refilled from the treasury. Each pays within its own policy.

Each signer approves from their phone, with a passkey kept in the Keyban Signer app. A threshold of signers moves money out of the multisig treasury, which holds most of the money. The treasury refills the agent wallets. An agent cannot reach the treasury.

In short, the signers' phones control the treasury, the treasury refills the agent wallets, and no agent can reach it.

What it is​

The treasury is a smart account, like an agent wallet: a contract on the blockchain that holds the USDC. It is a separate pot, with its own signers, that sits one step upstream of the agent wallets. It is available from the Growth plan and above. See Plans and quotas.

One treasury per network​

A treasury lives on one blockchain network and refills only the agent wallets on that network, whatever their application. An organization can have at most one treasury per network. Since an application runs on one network, an organization with an application on Base mainnet and another on XDC mainnet can have two treasuries, one on each network.

Who controls it​

The treasury is controlled by its signers: people of your organization, who must be Owners or Admins, who approve each move from their own phone.

  • The threshold is a number of signers. A move needs a set number of signatures out of the signers, for example 2 out of 3. You choose it when you create the treasury, and the signers can change it later, together.
  • Each signer keeps a passkey in the Keyban Signer mobile app. The passkey is created on the signer's own phone and kept behind Face ID or a fingerprint. It is the signer's key in the treasury contract. Keyban does not hold it.
  • Every key is checked by a colleague. Each invited signer creates a passkey in the app. Once all of them have, Keyban draws who checks whom, and each key is checked by a colleague over a phone call, with a 4-digit code. The treasury is deployed on the blockchain once every key is checked.
  • The signers manage the signers. Adding or removing a signer, or changing the threshold, is proposed by an admin from the dashboard and approved by the threshold of signers on their phones. Keyban only relays it to the blockchain.

How the signers are protected, and how access is restored, is in Treasury security.

What it holds​

The treasury holds most of the money: the USDC the organization keeps in reserve for its fleet. It is funded by sending USDC to its address, or by card, on Base mainnet only, when card top-ups are enabled. The agent wallets then hold only what their agents are about to spend.

How money leaves it​

Money leaves the treasury in a lot: a single operation with one to twenty USDC transfers. Each transfer names an agent wallet of your organization, on the same network, or a contact from the treasury's address book: a named address that a signer vouched for first. It never names a raw address typed in.

  • Nothing moves when the lot is opened.
  • Each signer signs the whole lot once in the Keyban Signer app, which recomputes what it is signing instead of trusting the server.
  • When the threshold of signatures is reached, the lot is sent to the blockchain. It is atomic: every transfer lands or none does.
  • Only one lot can be in progress at a time, and a lot that has reached the threshold can no longer be cancelled.

What it cannot do​

  • It never goes through an agent's spending policy. A treasury transfer is authorized by the signatures of its signers alone. The spending policy applies to what an agent itself spends.
  • An agent cannot reach it. No agent can create the treasury, sign for it or refill itself from it: every move needs the signatures of human signers. An agent can only report that its wallet is low, so that the people who manage the treasury refill it.
  • It cannot be driven from an assistant. Treasury by prompt Coming soon is planned and is not available yet.