Changelog

The Developer Portal delivers the new Withdrawal Fee Sources reference that explains which address pays the fees for withdrawal transactions. The page breaks down fees by asset, network type, and wallet type, while identifying if transaction fees are come from the base address, gas tank, or UTXO inputs. It also answers common questions, such as why an EVM token withdrawal can fail when the base address holds too little native coin for gas.

BitGo renames the self-custody wallet types to better reflect their purpose and reduce ambiguity.

All documentation, guides, and cookbooks reflect the new names. However, the underlying API values (for example, "type": "hot") remain unchanged to avoid breaking integrations.

BitGo replaces the Coins and Tokens table on the Developer Portal with the new BitGo Assets page — a dedicated reference for everything BitGo supports. The new reference launches with these three purpose-built views:

• Protocols
• Tokens
• Staking

Each page is searchable, filterable by trust entity, and exportable to CSV. The new pages also provide real-time asset prices and direct links to the blockchain reference pages.

BitGo delivers webhook signing keys that you can use to verify authenticity of BitGo notifications for your webhook policies. Requests include a JSON Web Token (JWT) that enables you to verify webhooks originate from BitGo. Webhook signing keys help prevent replay attacks, so you can automatically approve or deny transactions with greater confidence.

To learn more, see Set Up Webhook Signing Keys.

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.

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:

• Stablecoin Overview
• Mint Stablecoins
• Burn Stablecoins

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.

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:

• Staking Overview
• Stake from Go Account
• Unstake from Go Account
• View Rewards for Go Account

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

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)