BitGo Opens Its Self-Custody Wallets to Decibel Trading

BitGo activated live WalletConnect access to Decibel on September 3, 2026, letting institutional users initiate Aptos-based trading from BitGo self-custody MPC wallets while keeping their existing approval policies. The launch covers wallet connections from Ethereum and Solana; support for more networks is announced but not yet deployed. That distinction matters: Decibel executes on Aptos, so the source-chain wallet is an entry point, not the settlement venue.

How does BitGo connect a self-custody wallet to Decibel?

The integration keeps BitGo in the signing path while Decibel supplies the trading interface and on-chain venue. A user connects through WalletConnect, prepares an action in Decibel, then sends the transaction back through BitGo’s MPC infrastructure and policy engine. Address allowlists and multi-party approvals therefore apply before signing instead of being abandoned for a fresh browser wallet.

• Connect: an approved Ethereum or Solana wallet establishes the WalletConnect session.
• Authorize: BitGo evaluates the request against the institution’s wallet policy and required approvers.
• Execute: collateral reaches Decibel’s Aptos trading account, where orders, matching and settlement run on-chain.

This improves on the common predecessor workflow: transfer funds into a separately administered wallet, introduce another seed or signing key, and rebuild internal controls around it. The customer retains the recovery path and key control of the BitGo self-custody wallet, while BitGo remains a policy and co-signing dependency for normal operations.

Do assets really stay in the BitGo wallet while trading?

No—not in the literal sense once collateral is deposited—although users do not need a second source-chain wallet. Decibel’s documentation says deposits from Ethereum and Solana are bridged automatically to Aptos using Wormhole and Circle’s Cross-Chain Transfer Protocol, then credited to an on-chain trading account holding USDC collateral. Trading also relies on an Aptos API wallet that signs order transactions, a layer the BitGo announcement does not explain in detail.

The launch therefore preserves the institution’s control plane, not the original location or risk profile of every dollar. Wallet approval risk is reduced, but deposited collateral is exposed to Decibel contracts, Aptos execution, oracle and liquidation mechanics, and the cross-chain transfer path. Perpetual positions add leverage and continuous funding risk.

What does Decibel access cost, and what is still limited?

Decibel’s published base tier charges 0.0340% for taker orders and 0.0110% for maker orders below $10 million in 30-day volume. Rates decline with volume, with maker fees reaching zero above $1 billion; deposits and withdrawals carry no added protocol fee, though gas remains, and funding or builder-code charges may apply.

BitGo describes access to both spot and perpetual markets, but Decibel’s public documentation is inconsistent: its overview includes spot while another trader page says spot is still forthcoming. Institutions should verify the available markets in the live interface rather than treat the announcement as proof that every product is enabled.

The verdict is narrow but meaningful. BitGo has removed a costly governance break between an institutional wallet and an on-chain order book. It has not turned Decibel into cold storage, qualified custody or off-exchange settlement. The gain is policy continuity; the price is a new stack of bridge, contract, margin and operational dependencies.