Skip to main content
The same vocabulary is used in the console, in the API and throughout these docs.

​
Workspace

The unit of tenancy. A workspace owns its wallets, members, policies, API keys and webhooks. Every API route that reads or changes workspace state is scoped by workspace_id. A person can belong to several workspaces; a user’s role is set per workspace.

​
Wallet

An MPC wallet is a key pair generated by the signing cluster, where the private key exists only as shares held by separate nodes. Creating a wallet is asynchronous: the API records the request, the cluster runs distributed key generation, and the wallet becomes active when its public key is stored. A wallet belongs to one workspace and is identified by wallet_id.

​
Asset and wallet asset

The asset catalog lists the networks and tokens the platform supports. Each catalog asset has a UUID, a network, a native-or-token flag, decimals, and for tokens a contract address. Catalog asset IDs are never contract addresses. A wallet asset is a catalog asset attached to a wallet. Attaching derives a deposit address for that wallet on that network from the wallet’s public key. Balances, deposits and withdrawals are all per wallet asset.

​
Deposit address

The address derived for a wallet asset. Funds sent to it are observed by the chain scanner, credited once they reach the configured confirmation depth, and recorded as inbound transactions.

​
Withdrawal and signing request

A withdrawal is a request to send an amount of a wallet asset to a recipient. It is idempotent by request key, passes through policy evaluation, and (once cleared) produces exactly one signing request to the cluster and one broadcast. A withdrawal moves through states such as pending, pending_approval, submitted, confirmed and failed. A signing request is the cluster-side unit of work: the digest to sign, the wallet and derivation metadata, and, when complete, the signature.

​
Transaction

The workspace’s activity record: withdrawals and observed deposits, each with direction, asset, amount, status and, once broadcast, the on-chain transaction hash. Transactions can be listed per wallet or per workspace and exported.

​
Policy and policy rule

A policy routes matching withdrawals to an approval group before they are signed. It has a name, a status, an approval group, and one or more rules:

​
Approval group and approval request

An approval group is a named set of workspace members with a threshold: the number of approvals needed. When a policy or a workspace governance setting requires approval, the platform creates an approval request; members of the group approve or reject it in the console. The requester cannot approve their own request when dual control is enabled.

​
Governance settings

Workspace-wide controls that apply on top of policies: whether every withdrawal requires approval and above what amount, dual control, a destination whitelist with a hold period for new addresses, per-transaction and daily limits, and a kill switch that freezes all withdrawals in the workspace. See Policies & approvals.

​
API key

A credential for server-to-server use. Requests are signed with HMAC-SHA256. Each key carries scopes (for example wallets:read, withdrawals:create), can be bound to specific wallets, can be limited to an IP allowlist, can expire, and can be revoked. The secret is shown once, at creation.

​
Member and role

A person in a workspace, with one of four roles: owner, admin, member or viewer. Roles decide who can change policies, groups, keys and webhooks, who can initiate withdrawals, and who can only read. Access can additionally be restricted per wallet. See Access control.

​
Webhook

An HTTPS endpoint you register to receive events: wallet created, deposit detected, withdrawal confirmed, and so on. Deliveries are signed with an Ed25519 key you can verify, retried with backoff, and logged so you can inspect and resend them. See Webhooks & events.

​
Audit event

A durable record of who did what, to which resource, and when: for sign-ins, policy and group changes, key and webhook management, approvals and freezes. Available through the console and the API. See Reporting & audit trail.