When this issue occurs, the API Co-Signer signs some raw signing transactions but not others. This usually results from signature caching for off-chain messages.
Learn more about raw signing and signature caching.
Note
Signature caching for raw signing is enabled by default. Submit a request to Fireblocks Support if you want this feature disabled.
Need additional help?
If you have a question or need assistance, contact Fireblocks Support and include the following information in your request:
- Workspace name
- The first four characters of the corresponding API key
- User information (indicate whether the user is an active Co-Signer or is going through initial setup)
Additionally, copy the following logs from the API Co-Signer:
- Transaction handling (/databases/cosigner/log/customer_cosigner.log)
- Transaction signing flow
- Logging the Callback Handler request and response
- Configuration changes to the API Co-Signer (date_time.run.log)
- Setup
- Pairing a new API user
- Changing the Callback Handler URL