Skip to main content

Glossary

Keyban-specific terms used across the Wallet for Agents documentation. Generic Web3 and software-engineering terms are not redefined here — refer to the broader ecosystem (MDN, Wikipedia, ethereum.org) for those.

D​

Destination rules: Allow-lists or deny-lists that say where payments may go: addresses for USDC transfers and domains for x402 payments. They exist at the organization, application and wallet levels, a level is either an allow-list or a deny-list, and the strictest level wins. See Spending policy.

DKG (Distributed Key Generation): Cryptographic protocol where several parties jointly generate a key pair such that no single party ever holds the full private key. Keyban uses DKG to create the two shares of an agent wallet's key. See Shared key.

E​

Emergency stop: The emergencyStop switch of a spending policy. While it is on, the wallet refuses every payment with policy/emergency-stop until an operator resumes it. It is enforced by Keyban's policy engine, not by an on-chain rule. See Control spending.

F​

FROST (Flexible Round-Optimized Schnorr Threshold): A threshold signature scheme based on Schnorr signatures. Keyban uses FROST to produce a single Schnorr signature from multiple shares without ever reconstructing the private key. See also Schnorr, TSS.

I​

Intent (payment intent): A payment an agent asks Keyban to evaluate before the wallet signs it. Keyban checks it against the spending policy and either approves it, holds it for a human decision, or refuses it. See Payment intents.

K​

Key share (client key share): The agent's half of an agent wallet's key, kept in a file stored where the agent runs. Keyban keeps the other half. Any agent with access to that file can ask Keyban to pay from the wallet, within the policy, so it is kept like a password. See Where the agent's share lives.

M​

MCP (Model Context Protocol): An open protocol for exposing capabilities to AI assistants. The Keyban MCP server bridges agent apps and assistants (Claude Desktop, Claude Code, ChatGPT, etc.) to the Keyban backend. See CLI, MCP and API.

Mission: A bounded task, with its own budget and sources, that an agent runs under a wallet's policy. See Missions.

Monthly budget: A cap on what a group of wallets spends together in a calendar month, set for the whole organization and for each application. A wallet has budgets of its own. The dashboard labels the organization and application budgets "envelope". See Spending policy.

MPC (Multi-Party Computation): A cryptographic protocol that distributes computation across multiple parties such that no single party can see the others' data. The umbrella term that contains TSS, DKG, and FROST as Keyban uses them.

Multisig treasury: The shared USDC account of an organization, which holds most of its money and from which agent wallets are refilled. A threshold of signers must approve each move. See Multisig treasury.

O​

Operator: A person assigned to an agent wallet who holds the operate right on it: getting its MCP configuration, registering a new key for the agent, approving or declining held payments, pausing and resuming the wallet, and asking for a top-up. In the dashboard, the Editor role is shown as "Operator". See Operators and roles.

S​

Schnorr Signature: A digital signature scheme prized for its short signatures and clean threshold variants. Keyban uses Schnorr signatures (via FROST) for agent wallet signatures on EVM.

Signer: A person who approves the moves of a multisig treasury, with a passkey kept in the Keyban Signer mobile app on their phone. Only Owners and Admins of the organization can be signers. See Multisig treasury.

Spending policy: The rules Keyban evaluates before any payment from an agent wallet is signed. At the organization, application and wallet levels it is made of destination rules and a monthly budget; a wallet adds a per-payment cap, daily and weekly budgets, an approval threshold and the emergency stop. See Spending policy.

T​

TSS (Threshold Signature Scheme): A signature scheme that produces a valid signature from a threshold number of cooperating parties, none of whom ever sees the full private key. The construction behind every Keyban agent wallet.

X​

x402: An open protocol that lets an HTTP service ask for a payment with a 402 Payment Required response, which the buyer pays and then repeats the request. It is the rail agent wallets use to pay services. See x402 protocol.