Bitcoin Lightning Network

BitGo expands support for the Bitcoin Lightning Network by delivering support for custody wallets. To learn more, see:

• Bitcoin Lightning Network Overview
• Set Up Custody Lightning Wallets

Content Rename

For clarity, BitGo renames the advanced withdraw flow to manual. This update only impacts the documentation on the Developer Portal - there's no integration impact. The new names impact the following pages:

• Withdraw from Wallet - Go Account (Manual)
• Withdraw from Wallet - Self-Custody MPC Hot (Manual)
• Withdraw from Wallet - Self-Custody Multisig Hot (Manual)

CIDR Blocks for Access Tokens

BitGo enhances security and flexibility with access tokens by enabling you to pass CIDR blocks when restricting by IP address. CIDR blocks specify a range of IP addresses that are permitted to use an access token, simplifying management of IP restrictions.

See Also

• Integration Guide: Create Access Token
• API Reference: Create Access Token

Requiring PSBT for Cold Wallets

BitGo now requires using the Partially Signed Bitcoin (PSBT) transaction format for withdrawals of UTXO assets from cold wallets in production. This requirement applies to custody wallets and self-custody cold wallets. This change already took effect in testnet on September 2, 2025.

Breaking Change

1. You must update to a newer version of the OVC. You must also update to a newer version of either BitGo Express or the SDK (depending on your integration).

   Ensure you're using the follow versions or higher:

   • OVC: 4.7.11
     • Download: https://cdn.bitgo.com/vault/v4.10.7/waeMocaeLishu7careeh/bitgo-vault-v4.10.7.raw.gz
   • Express: 14.1.3
     • Download: https://hub.docker.com/r/bitgo/express/tags
     • Instructions: Install Express
   • SDK: [email protected]
     • Download: https://github.com/BitGo/BitGoJS/
     • Instructions: Update SDK

2. Ensure that when you initiate transactions, the value for the txFormat parameter is psbt or psbt-lite (if you don't pass this parameter, the value defaults to psbt-lite). If txFormat is legacy, BitGo returns an error.

   • Custody wallets:
     • Integration guide: Withdraw from Wallet - Custody Multisig
     • API Reference: Initiate a transaction
   • Self-custody wallets:
     • Integration guide: Withdraw from Wallet - Self-Custody Multisig Cold
     • API Reference: Build a transaction

See Also

• BitGo Blog: Save Fees with MuSig2 at BitGo
• Offline Vault Console
• Withdraw Overview

Know Your Business Integration

BitGo expands functionality for Crypto-as-a-Service (CaaS) by offering a Know Your Business (KYB) API integration. You can onboard your clients' businesses to your platform, completing regulatory compliance screening programmatically. This update also delivers new webhook functionality to for KYB status monitoring.

View the integration guide at Know Your Business (KYB).

PSBT for Cold Wallets

Requiring PSBT for Cold Wallets

BitGo now requires using the Partially Signed Bitcoin (PSBT) transaction format for withdrawals of UTXO assets from cold wallets in testnet. This requirement applies to custody wallets and self-custody cold wallets.

Note: Beginning September 30, 2025 BitGo will require PSBT in production. Avoid service disruptions by updating your integration before this date.

Breaking Change

1. You must update to a newer version of the OVC. You must also update to a newer version of either BitGo Express or the SDK (depending on your integration).

   Ensure you're using the follow versions or higher:

   • OVC: 4.7.11
     • Download: https://cdn.bitgo.com/vault/v4.10.7/waeMocaeLishu7careeh/bitgo-vault-v4.10.7.raw.gz
   • Express: 14.1.3
     • Download: https://hub.docker.com/r/bitgo/express/tags
     • Instructions: Install Express
   • SDK: [email protected]
     • Download: https://github.com/BitGo/BitGoJS/
     • Instructions: Update SDK

2. Ensure that when you initiate transactions, the value for the txFormat parameter is psbt or psbt-lite (if you don't pass this parameter, the value defaults to psbt-lite). If txFormat is legacy, BitGo returns an error.

   • Custody wallets:
     • Integration guide: Withdraw from Wallet - Custody Multisig
     • API Reference: Initiate a transaction
   • Self-custody wallets:
     • Integration guide: Withdraw from Wallet - Self-Custody Multisig Cold
     • API Reference: Build a transaction

See Also

• BitGo Blog: Save Fees with MuSig2 at BitGo
• Offline Vault Console
• Withdraw Overview

Fiat & Bank Accounts

New Bank Accounts Endpoints

BitGo expands fiat and bank account functionality by delivering the following new endpoints:

• List enterprise transfer limits
• Get ACH agreement
• Get address format information
• Get deposit info
• Initiate ACH deposit

Deprecation Notice

BitGo deprecates the following:

• The Get deposit information endpoint.
• The owner object in the /bankaccounts API.
• The following fields in the /bankaccounts API:
  • address
  • address1
  • address2
  • address3
  • ownerAddress

The endpoint, fields, and object remain fully functional while deprecated, but won't receive future updates.

Content Reorganization

For clarity, BitGo renames the Bank account section of the API reference to Fiat.

Update Your Integration

Update your integration to enable new functionality, including the ability for Crypto-as-a-Service (CaaS) integrations to make ACH transfers.

1. Instead of the deprecated Get deposit information endpoint, use the new Get deposit info endpoint.

2. In the /bankaccounts API, BitGo replaces the deprecated fields and object with the following new fields:

   • bankAddressCityLocality
   • bankAddressLine1
   • bankAddressLine2
   • bankAddressPostalCode
   • bankAddressStateProvince
   • ownerAddressCityLocality
   • ownerAddressCountryCode
   • ownerAddressLine1
   • ownerAddressLine2
   • ownerAddressPostalCode
   • ownerAddressStateProvince

See Also

Deposit Assets

Ethereum Hoodi Testnet

In support of the Ethereum Pectra upgrade, BitGo migrates from using the Ethereum Holesky testnet to the Hoodi testnet. The testnet ticker symbol on the BitGo platform continues to be hteth.

Breaking Changes

BitGo disables support for the Ethereum Holesky testnet. All your existing Ethereum wallets on the Holesky testnet no longer function. BitGo did the following:

• Disabled use of Holesky wallets on the BitGo platform.
• Reset the nonce of the fee address. Fee addresses now have 0 transactions.
• Cleared the send queue for 'hteth'.
• Rejected all the unresolved pending approvals.

To migrate to Hoodi and resume your testnet activities:

1. Create Hoodi wallets (see Wallets Overview).
2. Obtain new hteth from an Ethereum Hoodi Faucet. Your Holesky hteth isn't transferable to Hoodi wallets.
3. Update all instances of Holesky wallets in your integration to use newly created Hoodi wallets.

See Also

Breaking Changes Policy

BitGo updates the Developer Portal with a new page that documents Breaking Changes. This page clarifies:

• What BitGo considers a breaking change.
• What BitGo doesn't consider a breaking change.
• How BitGo communicates breaking changes.
• Best practices for handling breaking changes.

Off Exchange Settlement

Off Exchange Settlements Disputes

BitGo expands Off Exchange Settlements with new dispute functionality. Clients can now dispute settlements with a partner exchange before settlement completes with BitGo.

View the integration guide at Disputes.