Overview
Fireblocks enables you to connect to decentralized apps (dApps) on certain non-EVM blockchains. Using Fireblocks to interact with dApps on these blockchains differs from the experience of interacting with EVM-compatible blockchains. For example, Web3 operations on non-EVM dApps use a different type of transaction that includes less readable information than transactions on EVM-compatible dApps.
We currently support Web3 operations on these non-EVM blockchains:
- Algorand
- Cosmos
- NEAR
- Osmosis
- Solana
- Terra (Legacy)
- Tezos
- Tron
You can use the Fireblocks WalletConnect integration to connect to dApps on the above blockchains. Note that only dApps that support WalletConnect are compatible with the Fireblocks non-EVM Web3 integration. The Fireblocks Chrome Extension does not currently support non-EVM blockchains.
When connecting to dApps on the Osmosis network, use the Keplr Mobile wallet option for scanning the QR code. When connecting to dApps on the Tezos network, use the Trust Wallet option for scanning the QR code.
Enabling non-EVM dApp connections
If you’re newly onboarded to Fireblocks, non-EVM dApp connections should be enabled automatically. Otherwise, you can enable the feature using the following steps:
- In the Fireblocks Console, go to Settings > General.
- Under the Non-EVM dApp Connections heading, select Allow.
- On the confirmation window, select Allow.
After the Admin Quorum (including the Owner) or assigned Approval Group approves the change, you can connect to non-EVM dApps on the supported blockchains. You can disallow non-EVM dApp connections at any time.
Difference when connecting to non-EVM dApps
Transactions
Fireblocks supports contract calls for EVM-based networks, allowing you to view the destination address, transaction hash, and other transaction details for any contract call you make.
However, this functionality is not yet available for non-EVM contract calls. Instead, Fireblocks uses Typed Message Signing to sign contract calls without fully showing their metadata in the Fireblocks workspace. The following data is not parsed:
- Transaction destination addresses
- Transaction hashes
- Transaction confirmation status
While you cannot view this information in your workspace, you can use any block explorer on the relevant blockchain to follow the status of the signed transaction. You can also view the full transaction details in its Message Content section.
Note
Tezos native transfers do not use Typed Message Signing. Instead, they are initiated as standard transfer transactions and are governed by TAP rules configured with the Transfer operation type.
Tokens
For EVM-compatible blockchains, we support the blockchain’s base asset and any ERC-20 format token. You can add ERC-20 tokens to your workspace manually for full visibility of your tokens under custody.
For non-EVM blockchains, we support each blockchain’s base asset and support listing tokens only for the following blockchains and token formats:
- Algorand: ASA
- Digital Bits: XDB
- Solana: SPL
- Stellar Lumens: XLM
- Tron: TRC-20
Learn more about adding non-EVM tokens to your workspace.
Note that non-EVM tokens you’ve added may still be listed in your address on the blockchain even when you cannot see them in your workspace. Since Web3 applications read the address balance directly from the blockchain, you can use such applications to perform any token-related operations regardless of whether they appear in your workspace.
Osmosis network support
Currently, Fireblocks only supports the base asset of and transfers for the Osmosis network. However, you can swap OSMO for any other token in your dApp, but the token will not appear in your workspace.
Your token may still be listed in your address on the blockchain even when you cannot see the token in your workspace. Since Web3 applications read the address balance directly from the blockchain, you can use such applications to perform token-related operations regardless of whether they appear in your workspace.
Additionally, these transactions will be in the Cosmos message format, meaning you will see TYPED_MESSAGE and not CONTRACT_CALL for the transaction type in your Transaction History.
Solana message expiration
Solana transactions should be signed within one minute to prevent the message from expiring.
Creating TAP rules
Because this integration uses Typed Message signing to sign contract calls on non-EVM networks, you must create Typed Message rules in your Transaction Authorization Policy (TAP) to govern these transactions.
In short, rules configured with the Typed Message operation type will apply to your non-EVM Web3 operations. Rules configured with the Contract Call operation type will apply to your EVM-based Web3 operations.
To apply distinct rules to your non-EVM Web3 operations, create a dedicated vault account and apply those rules to it.
Note that since the destination contract address is not viewable for contract calls on non-EVM networks, policy rules for non-EVM Web3 transactions cannot be limited to whitelisted contracts.