Security Overview

What's actually implemented in this deployment — not aspirational marketing copy.

Two-factor authentication on every money movement

Sending or approving any transaction requires a current TOTP code, whether it's initiated from the dashboard or scheduled in advance. API-key-initiated sends on hot wallets treat the key itself as the authorization, the same model BitGo/Coinbase Custody use for their hot-wallet APIs.

Multi-signature vaults

Vaults require M-of-N human approvals. An API key can propose a transaction on a vault but can never single-handedly execute one — a leaked key cannot drain a multisig vault by itself.

Tamper-evident audit log

Every recorded action is chained by hash to the one before it. Altering a past entry breaks every hash after it, which is checkable at any time via the "Verify integrity" action on the Audit Log page.

Configurable custody controls

Per wallet: address whitelisting, daily and per-transaction limits, tiered approval thresholds, time-delayed large withdrawals with a cancel window, and anomaly flags on unusual amounts or new destinations.

Sandboxed API keys

Test-mode API keys can only see and act on test-mode wallets — they never mix with live balances, and IP allowlisting is available per key.

What this is not

This product does not integrate with a real blockchain in this version — deposits are simulated for demonstration and testing. It is not insured, and it is not a substitute for real HSM/MPC-backed institutional custody. It's infrastructure a buyer runs themselves and extends.