Stake from Fireblocks
Kiln is a non-custodial staking provider. As a customer and owner of your assets, it is YOUR responsibility to check and verify all the transactions you are signing. While Kiln provides tooling to help you interact with your stakes (web applications, APIs), Kiln is not responsible for the transactions that you sign.
Cardano (ADA)
✅ (using Fireblocks raw signing)
✅
Cosmos (ATOM)
✅ (using the Fireblocks console)
✅
DYDX (DYDX)
✅ (using the Fireblocks console)
✅
Ethereum (ETH)
✅ (using the Fireblocks console, WalletConnect or the Fireblocks Chrome extension)
✅
Fetch.ai (FET)
✅ (using Fireblocks raw signing)
✅
Injective (INJ)
✅ (using the Fireblocks console)
✅
NEAR (NEAR)
✅ (using Fireblocks raw signing)
✅
Osmosis (OSMO)
✅ (using Fireblocks raw signing)
✅
Celestia (TIA)
✅ (using the Fireblocks console)
✅
The Open Network (GRAM (prev. Toncoin))
✅ (using Fireblocks raw signing)
✅
Tron (TRX)
✅ (using Fireblocks raw signing)
✅
Tezos (XTZ)
✅ (using Fireblocks raw signing)
✅
SUI
❌
✅
Stake from Kiln Dashboard using Fireblocks raw signing API
For a secure setup, you need to configure both policy rules and IP whitelisting for Fireblocks Raw Signing API usage.
Policy rules for Raw Signing in your Fireblocks workspace
After enabling the Raw Signing feature in your Fireblocks workspace, you must add policy rules that allow users to initiate, approve, and sign raw transactions from specific vault accounts.
For a secure setup, limit which users can initiate and authorize transactions, which vault accounts they can access, and which assets are available for raw signing.
References
Allowlisting IP addresses for Fireblocks raw signing API requests
For a secure setup, you need to allowlist the following IP addresses for your Fireblocks API users in your workspace so that API calls can only come from the specified Kiln IP addresses:
34.77.242.47
34.76.117.161
35.233.83.194
35.205.102.118
34.76.215.95
35.240.14.22
35.187.124.60
34.22.185.7
Ethereum (ETH)
Stake via UI (Kiln Dashboard + WalletConnect)
Ethereum can be staked from the Kiln dashboard using WalletConnect. See how in this video:
Stake via UI (Fireblocks Console)
Stake via API
Use the Kiln Connect SDK to generate validators on the Kiln platform and issue the stake deposit transaction through the Fireblocks raw signing API.
Solana (SOL)
Stake via UI (Kiln Dashboard + WalletConnect)
Stake via UI (Fireblocks Console)
Solana can also be staked natively from the Fireblocks Console!
Stake via API
Use Kiln Connect to facilitate this.
Polygon (POL)
Stake via UI (Kiln Dashboard + WalletConnect)
POL can be staked from the Kiln dashboard using WalletConnect. Please follow our Polygon staking documentation.
Stake via UI (Fireblocks Console)
You can stake POL using the Stake tab of your Fireblocks console in a couple of clicks:

Stake via API
Use Kiln Connect to facilitate this.
Near (NEAR)
Stake via UI (Kiln Dashboard + Raw Signing API)
Stake via API
Use Kiln Connect to facilitate this.
Cardano (ADA)
Stake via UI (Kiln Dashboard + Raw Signing API)
Stake via API
Use Kiln Connect to facilitate this.
Cosmos (ATOM)
Stake via UI (Kiln Dashboard + Raw Signing API)
Stake via API
Use Kiln Connect to facilitate this.
Tezos (XTZ)
Stake via UI (Kiln Dashboard + Raw Signing API)
Stake via API
Use Kiln Connect to facilitate this.
The Open Network (GRAM (prev. Toncoin))
Stake via UI (Kiln Dashboard + Raw Signing API)
Stake via API
Use Kiln Connect to facilitate this.
Fetch.ai (FET)
Setting up a Fireblocks vault for FET raw signing
Once you have setup your Fireblocks Vault for raw signing, you will need to add a TAP rule to allow raw signing on the vault of your choice for FET. Here is an example where we enable raw signing on the vault 37 (see derivation path: 44, 118, <vault id>, 0, 0).

Stake via UI (Kiln Dashboard + Raw Signing API)
Stake via API
Use Kiln Connect to facilitate this.
Prerequisites for staking via Fireblocks
Please be aware of the configuration prerequisites for staking with Fireblocks: link.
Kiln validator addresses
When issuing a delegation transaction programmatically, you will need to enter the Kiln validator addresses which are available here:
⛓️ProtocolsReference
Last updated
Was this helpful?

