Sign transactions with your Fireblocks vault using Kiln Connect after a simple setup.
With the Kiln Connect SDK, you remain entirely in control of what is sent for signing to your Fireblocks workspace. You can verify the content of the transactions crafted with this SDK before signing it. Note that the entire signing workflow is done on the SDK end, not on Kiln APIs. Kiln will never have access to your Fireblocks api key or secret if you use the recommended configuration described in SDK setup
// Fireblocks config
name: 'fireblocks-1', // any value you want
You can pass multiple Fireblocks integrations config in the
integrationsproperty of the SDK configuration. For example if you want to stake with vault A and vault B, you can do:
Here are the steps to follow to setup the fireblocks integration properly:
- 1.Make sure that the raw signing api is available on your workspace. You can ask the Fireblocks support for information.
- 2.Create an API user using the Fireblocks tutorial here with the Editor role (minimum privilege to initiate transactions on the workspace). This might require that you contact your Fireblocks support.
- 1.Generate the csr certificate and make sure you store it somewhere safe
- 2.Create the API user
- 3.Get the API key of the user by clicking on "Copy API key" of the user in the workspace members list
- 3.Get the vault account id you want to stake with by clicking on it in your Fireblocks workspace and check the URL. For example the vault id of https://console.fireblocks.io/v2/accounts/vault/4 is
Best practice is to pass the fireblocks api key, vault account id and secret file path as environment variable of your program.