BitGo

• Name: BitGo
• URL: https://www.bitgo.com/
• Category: institutional custody / prime brokerage / settlement and wallet-infrastructure operating stack
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: BitGo belongs as an entity note, not a protocol note. The useful question is who controls the operating stack that combines custody modes, approval policy, transaction submission, trading and financing access, settlement rails, stablecoin workflow, and embedded wallet infrastructure. Wallet and custody are only the front labels; the practical leverage sits with the BitGo-run workflow layer and the affiliated regulated wrappers that decide how those rails are exposed.
• What it does:
  • Provides institutional wallet infrastructure across multisignature and MPC/TSS wallet models, with user, backup, and BitGo keys forming a 2-of-3 control structure in the official wallet docs
  • Offers both self-custody and regulated-custody workflows, while still supplying transaction submission, node infrastructure, wallet-user permissions, whitelists, and approval requirements through the BitGo platform
  • Runs a broader prime stack covering trading, financing, collateral management, and settlement as one operational surface rather than as isolated products
  • Markets stablecoin-oriented infrastructure for deposits, payments, orchestration, issuance, and related regulated operating flows
  • Exposes Crypto-as-a-Service tooling and SDK / API surfaces so other platforms can embed BitGo-run wallet, trading, and ramp-adjacent infrastructure into their own products
• Key claims:
  • The homepage presents BitGo as the digital asset infrastructure company and combines custody, staking, trading, stablecoins, prime services, and Crypto-as-a-Service under one brand and operating shell
  • The homepage also highlights prime services as one operational flow joining trading, financing, collateral management, and settlement, which is exactly why the entity boundary matters more than any one product page
  • The wallet docs say BitGo wallets use either multisignature or MPC/TSS technology and that every wallet type uses user, backup, and BitGo keys in a 2-of-3 structure
  • Those same docs say BitGo self-custody wallets do not give BitGo access to customer private user or backup keys, while BitGo still provides node infrastructure, transaction submission, wallet-user privileges, whitelists, and approval workflows
  • The developer materials show BitGo treating API, SDK, and AI-assisted documentation access as first-class integration surfaces rather than peripheral tooling
• Whitepaper: No classic standalone whitepaper or litepaper is the point here. The clearest primary materials remain BitGo’s official website, developer portal, wallet documentation, and public SDK repositories; see ../whitepapers/bitgo-primary-sources-2026-04-26.md.
• Sources:
  • https://www.bitgo.com/
  • https://developers.bitgo.com/
  • https://developers.bitgo.com/docs/wallets-overview
  • https://developers.bitgo.com/docs/get-started-mcp-server
  • https://github.com/BitGo
  • https://raw.githubusercontent.com/BitGo/BitGoJS/master/README.md

Internal linkages

• Project-layer alias: bitgo.
• Keep the comparison set on the clearest adjacent operating-stack reads: anchorage-digital, fireblocks, and copper.
• Cleaner contrast where more authority stays in user-held or app-held signing posture: turnkey and dfns.
• Reusable lens: when custody, policy, trading, settlement, and embedded wallet rails travel together, the real control surface usually sits with the company boundary rather than with any one wallet product.

Control surface

• Authority sits in approval policy, wallet-user privileges, whitelist administration, transaction-submission routing, venue and financing access, settlement workflow, and the regulated wrappers that decide which BitGo rail a customer is actually using.

• The self-custody marketing line does not remove the operator layer. If BitGo still supplies the transaction pipeline, node infrastructure, approval logic, and treasury workflow, the practical dependency still sits with BitGo’s workflow stack.

• Treat BitGo as institutional operator infrastructure first. Wallet and custody are only the front labels.

• Last reviewed: 2026-08-09 UTC