Skip to main content

Multisig treasury

The treasury is a shared USDC account that an organization's admins control together: moving its funds takes a threshold of signers, each approving from their own phone. It is the pot you keep your money in when you run several agents, and from which you refill the wallets of the fleet. What the treasury is, who controls it and why an agent never touches it is explained in Multisig treasury; the other ways to fund a wallet are in Funding sources. A single agent does not need a treasury: fund its wallet directly, as described in Fund a wallet.

The treasury is available from the Growth plan, or by a grant from Keyban. Without it, the dashboard shows "Available from the Growth plan". See Plans and quotas.

How it is built​

  • The threshold is a number of signers. You choose it when you create the treasury: a number of signatures out of a number of signers. The dashboard offers a threshold of at least two, up to ten, and never more than the number of signers. It is set at creation; afterwards the signers change it together, as described in Change the signers.
  • Each signer's key is a passkey. It is created on the signer's own phone in the Keyban Signer mobile app and held in the device keychain, behind Face ID or a fingerprint. The passkey is the signer's key in the treasury contract: Keyban does not hold it. The biometric check is signed into every approval and verified on the blockchain.
  • The mobile app only signs. Admins navigate in the web dashboard. The app opens on the signer's pending duties: a key to validate, a transfer to sign. An e-mail or a push notification takes them straight there.
  • One treasury per network. An organization has at most one treasury on each network.

From the dashboard​

The Treasury entry of the dashboard menu opens it. It needs the rights on the treasury that Owner and Admin hold.

Create the treasury​

  1. Choose Create treasury. Pick the network, a name, the number of signatures required per transfer and the display currency, which is chosen once for the whole organization and cannot be changed afterwards.
  2. Invite the signers: pick the other admins of your organization. A treasury needs at least two admins, so invite a second admin to your organization first if you are alone. You are invited automatically.
  3. Each invited admin receives an e-mail pointing to the signer app, installs it, signs in with the same account and creates their own key. Nothing is enrolled on their behalf.
  4. Once every invited signer has a key, Keyban draws who checks whom: each key is checked by a colleague over a phone call, as described below, and nobody checks their own key.

The account is deployed on the blockchain once every invited signer holds a checked key. Until the draw, an invitation can be revoked; after it, changing the signers before deployment means deleting the treasury and creating it again. If the deployment fails, delete the treasury and create it again: no funds can have reached it.

If the threshold equals the number of signers, 2 of 2 for example, every signer must accept a warning in the app when they create their key, because such a treasury has no spare signer. See Treasuries without margin.

Check a key: the verification call​

A new key is admitted only after a colleague checks it, so that a compromised dashboard cannot slip in a key nobody holds.

  1. The colleague calls the new signer, on a number they already knew.
  2. The new signer's phone shows a 4-digit code derived from their key, and the new signer reads it out. It is never sent in writing.
  3. The colleague compares it on their own phone. A match lets them go on. A mismatch refuses the key, and a colleague who finds two mismatches can no longer check keys of that treasury.

Change the signers​

On the treasury page, the Signers card offers Propose a change: Remove a signer, Change the threshold or Add a signer. An Owner or an Admin proposes it, signed in to the dashboard: an API key is refused.

  • The signers approve the change on their phones, in Keyban Signer. It needs the approval of the threshold of current signers, or of every signer of the result when the change makes the threshold equal to the number of signers.
  • There is no veto: a signer who declines is heard by everyone, but cancels nothing.
  • One change at a time per treasury. It closes after seven days without its approvals. Its author can cancel it until it has them; then it is sent to the blockchain and can no longer be withdrawn.
  • A change that takes effect cancels the transfer waiting for signatures.
  • To add a person, pick an Owner or Admin of the organization who holds no key in this treasury. They join from the app, and each signer who approves calls them and checks their key as described above before approving.

Losing a phone does not lose the signer in the ordinary case, because the passkey follows the person's account on iCloud Keychain or Google Password Manager. A signer who changes phone moves their key in two scans, from Change phone in the app. For a lost key, see Recovery in Treasury security.

Fund the treasury​

Choose Top up and then Card or USDC deposit. A card purchase is available on Base mainnet only, for 5 to 999 €, when enabled. For a deposit, send only USDC, on the network of the treasury: anything else is lost.

Refill the agent wallets​

The Agent wallet fleet table lists the wallets on the network of the treasury with their balance and runway. A wallet with less than two days of runway is due.

  • Top up selected wallets and Top up wallets due open a transfer that tops each wallet back up to what its monthly budget still allows. The proposal never exceeds that budget. Without an exchange rate, the monthly budgets cannot be converted to USDC: use a single transfer with an amount you choose.
  • New transfer sends USDC to a wallet of your fleet or to a contact of the address book of the treasury.
  • Several transfers leave in one signed lot of up to twenty, and only one lot can be in progress at a time. Nothing moves when the lot is opened.

When a team member asks for a refill, the request lands in the Inbox of the people who manage the treasury and can be fulfilled from there. See Fund a wallet.

Sign a transfer​

  1. An admin opens the transfer in the dashboard. Each active signer is notified by e-mail and by push notification.
  2. Each signer's phone recomputes the transfer and shows the destination, the amount and the network. It refuses to sign if what it computed differs from what the server sent: a tampered transfer shows an alarm, never a sign button.
  3. The signer approves with Face ID or a fingerprint.
  4. When the threshold of signatures is reached, the transfer is sent to the blockchain. The signing window lasts one hour. A lot that has reached the threshold can no longer be cancelled.

Treasury transfers are authorized by the signatures alone. They do not go through the spending policy of an agent wallet.

The address book, the history and the holdings​

  • Contacts is the address book of the treasury: a named destination that you add the first time you send a transfer, and archive when you no longer use it. A transfer goes to a contact, never to an address typed in at the last minute.
  • Movements lists the incoming and outgoing movements of the last 90 days, with who signed, the status and the transaction, and can be exported.
  • Holdings over time draws the daily USDC holdings of the treasuries, of the agents and of the funding, converted to the display currency, one point per day.

Notifications​

Invited admins are told by e-mail. Signers are told by e-mail and by push notification in the app when a key waits for a check, when a change to the signers waits for their approval, when a key is replaced and when a transfer waits for their signature. Every Owner and Admin is told when a key is admitted. The e-mails never carry the code of the verification call: it is read from the new signer's screen.

Treasury by prompt Coming soon​

Treasury by prompt Coming soon, driving the treasury from an assistant, is planned. It is not available yet.

What the agent can do​

Nothing. An agent cannot reach the treasury, create one, sign for it or refill itself from it: every move needs the signatures of human signers. What the agent can do is report that its wallet is low, from the balance tool, so that the people who manage the treasury refill it. See Track spending. There is no admin tool for the treasury either.

Limits​

  • Available from the Growth plan, or by a grant from Keyban.
  • One treasury per organization and per network, and one lot in progress at a time.
  • A lot holds one to twenty transfers, to wallets of your fleet or to contacts.
  • The threshold is at least two and at most ten at creation. Afterwards, the signers change it, and who signs, together.
  • One change to the signers at a time per treasury, open for seven days.
  • Card top-ups of the treasury are on Base mainnet only, for 5 to 999 €, when enabled.
  • A signature needs a signer's phone: there is no way to sign from the dashboard.
  • Keyban relays the signed transfers and changes, and cannot forge a signature. Its admin key can upgrade the contract. See What Keyban can and cannot do.
  • Treasury by prompt Coming soon is not available yet.