Skip to main content

​
Transaction history

Every deposit and withdrawal is a transaction with a direction, asset, amount, status and (once on chain) a transaction hash. History is available per wallet and per workspace, in the console under Transactions and through the API:
Transaction detail resolves by the platform’s transaction ID or by the on-chain hash, and links to the network’s block explorer.

​
Withdrawals

Withdrawal records carry the full lifecycle: request, approval decisions, signing, broadcast, receipt and confirmation state, with status_reason on every transition.

​
Balances and analytics

Balances are chain-observed snapshots per wallet asset, showing the available amount and what is held by in-flight withdrawals. The console’s Analytics page and the workspace statistics routes give totals and daily volumes across the workspace, with asset prices from the platform’s price feed.

​
Audit trail

Sensitive actions are recorded as audit events with the actor, the action, the resource and the time, and are available under Audit Log in the console and to admin keys through the API. Recorded actions include member and role changes, policy and approval-group changes, approvals and rejections, API-key creation and revocation, webhook and alert-channel changes, and freezing or unfreezing withdrawals.

​
Tracing an operation

Every operation carries stable identifiers that appear in responses, events, logs and audit records: the request ID, workspace, wallet, withdrawal, signing request, the signing cluster’s correlation ID, and the transaction hash. An incident can be followed from the API call that started it to the block that confirmed it.

​
Notifications

Beyond webhooks, members receive in-app notifications in the console, and a workspace can link a Telegram channel under Account Settings → Alert Channels to mirror wallet events to a team chat.