Overview
Web3 refers to the ecosystem of applications, projects, and protocols built using decentralized blockchains. Web3 applications can be built for a variety of use cases, such as decentralized finance (DeFi), NFT marketplaces, and gaming (GameFi).
Fireblocks offers several integrations for connecting your workspace to Web3 applications. Through these integrations, you can use the Fireblocks wallet infrastructure and MPC signing to trade and manage NFTs, contribute to liquidity pools, and participate in other Web3 activities.
In the Fireblocks Console, you can view the details of your Web3 transactions and manage your application connections. To provide further security measures when interacting with these decentralized applications (dApps), you can configure settings and create Policy rules specifically for Web3 interactions.
Connecting to dApps using Fireblocks
Fireblocks enables you to connect your workspace to Web3 dApps using the Fireblocks WalletConnect integration, the Fireblocks Chrome Extension, MetaMask Institutional, or the Fireblocks API. These integrations allow you to perform DeFi operations, trade and manage NFTs, execute governance, and more with the security of your Fireblocks wallet infrastructure for transaction approvals and signing.
Note
The Fireblocks Web3 integrations enable you to connect your Fireblocks wallets to Web3 dApps. However, any operation you perform using these connections is exclusively your responsibility. Fireblocks recommends thorough diligence of any Web3 dApp and smart contract you want to use before interacting with it.
Fireblocks WalletConnect integration
This integration allows you to connect to any Web3 dApp that utilizes WalletConnect without needing to install additional plugins or open extra extension windows. The Fireblocks WalletConnect integration supports Web3 operations on both EVM-compatible blockchains and non-EVM blockchains.
Learn more about the WalletConnect integration.
Fireblocks Chrome Extension
This integration allows you to connect to any Web3 dApp that utilizes Rabby. Applications recognize the Fireblocks Chrome Extension as Rabby, so you can connect in the same way you would using Rabby. However, when a transaction requires a signature, the extension sends it to Fireblocks to be signed by your Fireblocks private key. The Fireblocks Chrome Extension supports Web3 operations on EVM-compatible blockchains only.
Learn more about the Fireblocks Chrome Extension integration.
MetaMask Institutional
MetaMask Institutional (MMI) is a Web3 wallet that offers a suite of institutional portfolio management solutions, such as native token swapping, NFT tracking, and profit and loss (P&L) reporting. With Fireblocks, you can integrate the MMI extension into your workspace to connect to Web3 dApps and utilize MMI’s features.
Learn more about the MetaMask Institutional integration.
Fireblocks API
You can also use the Fireblocks API to create and manage your Web3 connections. The Fireblocks Web3 Wallet Link feature utilizes several API endpoints that allow your users to connect their Fireblocks wallet addresses directly to dApps, without them needing to use their wallet or any other application.
Learn more about the Wallet Link feature.
NFTs
You can use the NFTs page to view and manage the non-fungible tokens (NFTs) in your Fireblocks Vault. Fireblocks allows you to view NFTs from a variety of standards and blockchains. You can also transfer NFTs directly within the Console.
Learn more about managing your NFTs in Fireblocks.
Swaps
Fireblocks allows you to swap tokens directly in the Fireblocks Console. Swapping involves trading one token for another on the same blockchain. While you use the Fireblocks platform to initiate the transaction, swaps are performed by the Uniswap protocol. You can also wrap and unwrap tokens using the Swap page.
Learn more about swapping tokens in Fireblocks.
Additional Web3 features
Fireblocks offers additional features and integrations for managing your Web3 interactions.
Policies for Web3
All Web3 operations pass through your existing Policies before they can be approved. You can create Policy rules around contract call transactions that have different restrictions and approval flows than other transfer types, allowing you to implement specific policies for your Web3 activities.
Learn more about creating Policy rules for governing Web3 interactions.
Security best practices
Since Web3 operations require interaction with smart contracts, you incur unique security risks that may lead to theft or loss of funds. Limiting smart contract interactions to whitelisted addresses, requiring multiple approvers, and reducing the amount of funds you store in vault accounts for Web3 can help secure your funds when interacting with dApps.
Learn more about our recommended best practices for interacting with Web3.
Amount cap for Approve transactions
Because you cannot include ERC-20 tokens directly on a contract call, Web3 activities require you to complete an Approve transaction before the actual operation. Approve transactions grant a dApp the ability to withdraw the maximum amount of funds possible to complete the operation. However, Fireblocks allows you to limit the amount that Approve transactions can grant.
Learn more about setting an amount cap for Approve transactions.
Contract call decoding
Interacting with Web3 dApps requires the execution of custom smart contracts. The details of these contract calls are encoded when broadcast to the blockchain. Fireblocks decodes contract calls to show you the details of the transaction, such as the Web3 dApp involved and the operation used.
Learn how Fireblocks decodes contract calls.
Web3 integration for non-EVM networks
Fireblocks enables you to connect to Web3 dApps on some non-EVM blockchains using the Fireblocks WalletConnect integration. However, interacting with these dApps differs from the experience of interacting with EVM-compatible dApps.