Fireblocks signing in Guardian UI
Operations remotely signed by the keys in Fireblocks
submitMessage
All messages sent to Hedera are signed with the Fireblocks keys using Raw Signing method.
Operations signed by Operator ID/Key
OPERATOR_KEY is used for generating DIDs and signing documents as Fireblocks API does not support such operations.
Additionally OPERATOR_KEY is used for the following operations:
β’ newToken
β’ newTopic
Note: creation of new topics and/or tokens require freeze/wipe keys as a parameter in the API call. Guardian uses OPERATOR_KEY.
β’ wipe
β’ grantKyc
β’ revokeKyc
β’ associate
β’ dissociate
β’ freeze
β’ unfreeze
β’ updateToken
β’ deleteToken
Note: Similarly to the creation of topics/tokens, Hedera SDK API require explicit specification of keys as a parameter.
β’ transfer
β’ transferNFT
β’ newAccount
β’ newTreasury
Note: These operations require specific transaction type not supported by RAW SIGNING.
β’ balance
Note: Guardian uses the account specified in the UI
Enabling Fireblocks Remote Signing:
When creating a user, select the βUse fireblocks signingβ option and populate the following fields with values from your Fireblocks account configuration:
Fireblocks Vault ID
Fireblocks Asset ID
Fireblocks API Key
Fireblocks Private Key
Users, which have been created with this option enabled to remotely sign their Hedera transactions using Fireblocks API instead of via the built-in Guardian signing workflow.
Last updated