BitGo — multi-sig custody with wallet-grade accounting
BitGo's multi-sig custody serves institutional clients across exchanges, asset managers, and corporate treasuries. We integrate via the BitGo API for clean accounting.
BitGo pioneered institutional multi-sig custody and remains a major player alongside Fireblocks and Anchorage. The integration model is similar — read-only API key, wallet hierarchy preserved, on-chain reconciliation. BitGo's hot/cold wallet split is captured in the export so finance teams can report cold-storage balances and hot-wallet operating activity separately.
What the BitGo integration does
BitGo Enterprise API ingest
All wallets, all assets, all chains under one workspace.
Hot / cold wallet attribution
Cold-storage and hot-operating wallets tagged separately.
Multi-sig signer attribution
Per-transaction approver list preserved.
On-chain reconciliation
BitGo state vs independently computed on-chain truth.
The connection in 4 steps
Generate a BitGo Enterprise API token
In the BitGo Enterprise dashboard, create a long-lived access token with read-only scopes. Wag3s requires access to wallet list, transaction history, and balance endpoints only.
Connect to Wag3s
Enter the API token and your BitGo Enterprise org ID in the Wag3s custody integrations panel. We discover all wallets, assets, and hot/cold wallet tiers automatically.
Hot / cold wallet attribution applied
BitGo's hot and cold wallet designation is preserved in the Wag3s workspace. Finance teams can report cold-storage balances and hot-wallet operating activity as separate line items.
On-chain reconciliation and JE export
BitGo-reported balances are reconciled against independently computed on-chain truth per asset per chain. Reconciled activity posts to your ERP on the configured schedule.
Common configurations
Exchange holds client assets in segregated BitGo wallets across BTC, ETH, and stablecoins. Monthly proof-of-reserves report requires each wallet balance to match on-chain truth. Wag3s reconciles every BitGo wallet against on-chain independently and produces the signed reconciliation report.
Asset manager holds BTC in BitGo multi-sig cold wallets with a 2-of-3 signing policy. Annual audit requires the cost-basis lot file and transaction history. Wag3s tracks UTXO lots from the first deposit, applies HIFO, and exports the lot schedule for the auditor.
BitGo integration questions
Does the BitGo integration handle Bitcoin's UTXO model correctly?
Yes. BitGo Bitcoin custody uses multi-sig P2SH or Taproot. We track at the UTXO level and reconcile lots correctly — same engine as our standalone Bitcoin coverage.
Does the BitGo integration support institutional staking activity?
Yes. BitGo offers staking services for ETH, SOL, and select other assets via their institutional custody layer. Wag3s ingests staking reward receipts reported through the BitGo API and classifies them as staking income on the distribution date at the asset's spot price. Staked balances appear as a locked receivable separate from liquid holdings in the balance report.
How are multi-sig BitGo wallets attributed to the correct entity in Wag3s?
BitGo wallets are organized in an enterprise hierarchy — enterprise, wallet group, wallet. Wag3s preserves this hierarchy and maps each BitGo wallet to a Wag3s entity during onboarding. For groups with multiple subsidiaries, each entity's wallets are tracked in isolation, ensuring that inter-entity transfers between BitGo wallets are reconciled correctly rather than appearing as external disposals.
Other connectors that pair with this one.
Connect BitGo in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.