This guide walks you through enabling MPC-BAM for an API user via the Fireblocks Console.
Before you begin
Verify the following:
- API user paired with Co-signer: The API user must be paired with an API Co-signer (SGX, AWS Nitro, or GCP).
- Co-signer version 2026.03.02: Verify your Co-signer version meets this minimum requirement. If your Co-signer's version is below the requirement, you won't be able to enable MPC-BAM until you upgrade.
Enabling MPC-BAM for an API user
- In the Fireblocks Console, go to Developer center > Co-signers.
- Find (and expand, if necessary) the Co-signer with the API user you want to configure.
- Find the API user in the Paired API users list, then select More actions > Enable fast signing.
- Review the MPC-BAM explanation on the confirmation dialog, then select Enable.
After confirming, MPC-BAM keys are automatically provisioned in the background. You'll see a "Processing" status indicator next to the API user. Key provisioning typically completes within a few minutes.
During provisioning, your API user continues to use MPC-CMP for signing. There is no downtime.
Verifying MPC-BAM is active
Once key provisioning completes, a lightning bolt icon (⚡) appears next to the API user’s name. This icon indicates that the API user now uses MPC-BAM for all ECDSA SECP256K1 signing operations.
Disabling MPC-BAM usage
You can disable MPC-BAM at any time and revert to MPC-CMP. Repeat the process you performed to enable MPC-BAM, but instead select Disable fast signing from the More actions menu.
When disabled, the API user immediately reverts to MPC-CMP signing. Your MPC-BAM keys are retained but not used.
Troubleshooting
Fast signing option not available
Possible causes:
- API user not paired with an API Co-signer
- Co-signer version below 2026.03.02 (you'll see "Upgrade Co-signer to enable fast signing" indicator)
Solution:
- Upgrade your Co-signer to version 2026.03.02 or higher
- Ensure the API user is properly paired with the co-signer
Key provisioning is stuck in "Processing"
Possible causes:
- Co-signer is offline or temporarily unavailable
- Network connectivity issues
Solution:
- Check that the Co-signer status shows "Online" in the Console
- Wait a few minutes and refresh the page
- If the issue persists after 10 minutes, contact Fireblocks Support