Available now

Custody orchestration, without being the custodian

Segregated 2-of-3 multi-signature vaults on BitGo Bank & Trust qualified custody — created programmatically, governed by policy engines, automated by webhooks. You generate and hold the backup key, which is why no one, including us, can move your value alone.

Start custody onboarding Request the data room

How it works

Three keys. One gate. Zero unilateral control.

The 2-of-3 key structure

Every vault is a multi-signature wallet with three keys held by three different parties. Any transaction requires two — which means no single party has unilateral control, cryptographically, not contractually.

User key (platform) — initiates transactions; encrypted with a tenant-scoped passphrase; cannot move funds alone.
Backup key (you) — generated and held by you; only the public key ever reaches our infrastructure; your recovery path if Unykorn disappears tomorrow.
Custodian key (BitGo) — held inside BitGo Bank & Trust's OCC-chartered, insured qualified-custody environment.

The gate runs before the vault exists

Compliance is not a report generated after activity — it is a precondition of the account itself. KYC/KYB, sanctions screening, and Travel Rule clearance run before a wallet is created, then again on every transfer.

Account gating — an unverified counterparty never gets a wallet, so there is nothing to freeze later.
Transfer gating — every movement is checked against your program's rules pre-settlement.
Signed record — each decision lands in an append-only audit trail, exportable and verifiable without us.

Capabilities

What ships in the box

Programmatic vault creation

Create segregated vaults per tenant, per program, per asset — through the API, gated by compliance clearance, in minutes not weeks.

Wallet policy engine

Address whitelists, velocity limits, transaction ceilings, and m-of-n approval chains — enforced at the custody layer, not in your app code.

Treasury automation

Webhook-driven stablecoin sweeps, deposit consolidation, and scheduled rebalancing — with HMAC-verified events and idempotent processing.

Segregation by construction

Per-tenant wallet isolation — no omnibus commingling, no shared credentials, and client assets never touch a corporate balance sheet.

Audit-ready reporting

Every vault event — creation, policy change, transfer, sweep — produces a signed record built for regulator and counterparty review.

Recovery you control

Your backup key recovers your assets through BitGo's processes even if Unykorn ceases to exist. Exit risk is engineered out, not papered over.

Specifications

The details a diligence team asks for

Qualified custodian	BitGo Bank & Trust, N.A. — OCC-chartered national trust bank
Key structure	2-of-3 multi-signature; user key (platform), backup key (client-held), custodian key (BitGo)
Unykorn's custody status	Never a custodian. Software orchestration only; cannot move value unilaterally
Compliance preconditions	KYC/KYB, sanctions/OFAC, Travel Rule (IVMS101) — before wallet creation and per transfer
Accounting	Integer minor units throughout; no floating point in any money path
Audit trail	Append-only, cryptographically signed; exportable and verifiable independently of Unykorn
Fee posture	Platform and per-vault fees only; zero transaction-contingent fees