API Co-signer Maintenance

Documentation Index

Fetch the complete documentation index at: https://developers.fireblocks.com/llms.txt

Use this file to discover all available pages before exploring further.

This article outlines the most common maintenance operations for Co-signers. Since each Co-signer type has a unique architecture and is installed in a specific environment, refer to the relevant article for detailed maintenance instructions for your Co-signer type.

Note: Due to the enclave architecture of the Google Cloud Confidential Space Co-signer, maintenance operations can only be performed through Google Cloud’s portal or using gcloud.

Co-signer maintenance include:

• View the logs
• Observe the status
• List the paired API users
• Retrieve the public key (used for the Callback Handler JWT authentication)
• Stop the Co-signer
• Restart the Co-signer
• Retrieve the running version
• Update the Co-signer
• Migrate to a new machine
• Configure a proxy server
• Configure the communication protocol

Use the Co-signer management tab to observe the Co-signer’s online / offline status and the list of paired API users and refer to the following guides to learn about platform-specific Co-signer maintenance: