Changelog
Start typing to search…

Changelog and API Release Resources

In addition to Developer Portal changelog, you can view granular technical updates from the following:

  • BitGo Express Docker - Track version tags and deployment history directly on Docker Hub.
  • BitGo JavaScript SDK - Access a detailed history of SDK developments, bug fixes, and feature updates within GitHub.
  • BitGo API Release  - View a comprehensive changelog in GitHub for every update made to the BitGo API.

2026.03.17

MCP Server for AI-Powered Documentation Access

The BitGo Developer Portal now includes a Model Context Protocol (MCP) server that enables your AI-powered tools to search, read, and interact with BitGo documentation through natural language. Instead of manually browsing for endpoints or guides, you can connect an MCP client to the BitGo documentation server and get answers drawn directly from the Developer Portal.

What You Can Do

With the MCP server, you can use your preferred AI client to:

  • Search documentation using natural language queries.
  • Pull the complete text of any documentation page into your AI conversation for deeper analysis.
  • Get integration help by asking the AI to help you write code against BitGo APIs using the documentation as context.
  • Explore concepts about BitGo features like wallets, policies, webhooks, and staking, with answers grounded in the official docs.

Getting Started

Connect any MCP-compatible client — including Claude Desktop, Claude Code, ChatGPT, Cursor, VS Code, and JetBrains IDEs — to the BitGo documentation server:

https://dash.readme.com/api/v1/mcp

For setup instructions and example queries, see MCP Server.

2025.02.20

Custody Starter Architecture

The Developer Portal now includes a use-case guide called Custody Starter Architecture that walks you through the most common custody integration, designed for clients operating within a single enterprise. This new section is a complete end-to-end guide that you can use to set up the most popular custody configuration.

How It Works

Custody starter architecture utilizes three wallets for each coin, each with varying degrees of security and balance sizes. This pattern helps your enterprise maximize security while maintaining operational flexibility.

The new guide walks you through creating these three wallets with distinct roles:

  • A custody wallet that provides cold storage for the majority of your assets, guarded by strict policies.
  • A self-custody hot wallet that serves as a standby wallet, with moderate policies.
  • Another self-custody hot wallet with the lowest balance. This wallet handles all deposits and withdrawals for day-to-day transactions, with minimal policy restrictions.

Integration Guides

Get started with:

2026.02.16

Stablecoin Minting and Burning

The Developer Portal now includes a use-case guide for Stablecoin that walks you through minting and burning stablecoins using your Go Account. This new section provides end-to-end integration guides for issuing and redeeming fiat-backed stablecoin tokens via the BitGo API.

How It Works

Stablecoins are blockchain-based tokens backed by fiat-denominated collateral, maintaining a 1:1 relationship between circulating tokens and their backing reserves. Using your Go Account, you can hold fiat currency, enabling you to mint and burn stablecoins.

The new guides cover two core operations:

  • Minting converts fiat currency held in a Go Account into newly issued stablecoin tokens. Minted tokens can be issued to your Go Account, a whitelisted Go Account, a whitelisted BitGo wallet, or a whitelisted external wallet.
  • Burning permanently removes stablecoin tokens from circulation in exchange for fiat currency deposited back into your Go Account. Burn orders are typically fulfilled in under two hours.

Both operations use the Stablecoin Order API and require BitGo Express or JavaScript SDK to sign and process transactions. All orders are subject to validation, authorization, and reconciliation controls to ensure token supplies and reserve balances remain aligned.

Integration Guides

Get started with:

2025.12.03

V3 Access Tokens

BitGo fixed a bug regarding v3 access tokens. These tokens were causing the JavaScript SDK to fall back to v1 authentication, which doesn't include Hash-Based Message Authentication Code (HMAC) .

Now, tokens created with v3 authentication are prefixed with v2x, ensuring they use v2 or v3 authentication protocols with HMAC.

If you're currently using v3 access tokens, BitGo recommends rotating to v2 or v3 access tokens with v2 or v3 authentication. This enables you to have the added security benefits of HMAC.

2025.11.26

Go Account Staking

BitGo extends staking support to Go Accounts. You can now stake assets held in your Go Account and accrue rewards. When you unstake, the assets and rewards become available in your Go Account.

With Go Account staking, BitGo simplifies the required transactions on your behalf, enabling a more streamlined integration experience compared to staking from custody or self-custody wallets.

To learn more, view the API reference and the integration guides:


2025.10.07

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:

  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.

See Also