img width: 750px; iframe.movie width: 750px; height: 450px;

Fireblocks Wallet Extension Setup and DApp Recovery Process Guide

Install the browser add-on directly from the Chrome Web Store or Firefox Add-ons marketplace. Verify the developer’s name matches the official provider to avoid fraudulent copies. Before proceeding, ensure you have your institutional account credentials and necessary authorization permissions ready.

Configuration requires linking the add-on to your institutional vault. This process involves scanning a QR code with your mobile device running the corresponding mobile application. Multi-party authorization is typically mandatory; confirm all required approvals are in place to finalize the connection. The tool will not function without this secure handshake.

For re-establishing access to decentralized applications, first ensure the browser plugin is active and unlocked. Navigate to the application’s interface. You will often encounter a prompt to select a connection method; choose the option for institutional-grade providers. The system should then present a list of your vault accounts. Selecting the correct one automatically restores your portfolio view and transaction capabilities.

If the application fails to recognize your account, clear the browser’s cache for that specific site and refresh the page. Check the connected network within the application–it must match the network of your assets. Persistent issues may require you to re-initiate the connection from the add-on’s interface, manually approving the application’s request for access.

FAQ:

I installed the Fireblocks browser extension but can’t see my existing vault accounts. What’s wrong?

This is a common point of confusion. The Fireblocks Wallet browser extension browser extension itself does not hold your assets; it’s a connection tool. Your assets remain secured in your Fireblocks MPC-CMP vault, which is a separate, institutional-grade custody environment. The extension only provides a secure interface for your web browser to request transaction approvals from that vault. To see your assets and balances, you should log into your main Fireblocks web dashboard. The extension will then be ready to facilitate transactions from those vault accounts when you interact with a decentralized application.

Can I recover access to my dapps if my computer crashes and I lose the Fireblocks extension setup?

Yes, because your access is not tied to a single browser or device. Recovery involves two steps. First, re-install the Fireblocks extension on your new machine. Second, and most critically, you must use your existing Fireblocks login credentials and multi-factor authentication methods to authenticate. Since your wallet’s private keys are never stored on your device but are managed by the Fireblocks MPC network, your authorization through the official Fireblocks platform restores the connection. Once logged in, the extension will be able to request approvals from your vault as before, re-establishing access to all connected dapps.

How does the transaction approval process work with the extension and multiple users?

The process follows the policy rules set for your Fireblocks workspace. When a dapp initiates a transaction, the extension creates a secure signing request. This request is sent to the Fireblocks backend, not handled locally. Your workspace’s configured transaction policy then activates. For example, a policy might require 2 out of 3 designated approvers to confirm. These approvers receive the notification via the Fireblocks mobile app or email, not necessarily through the browser extension. Only after the required approvals are collected on the Fireblocks platform does the transaction execute on the blockchain. The extension is the initiator, but the approval happens on the broader, secure Fireblocks infrastructure.

Is there a risk that a malicious dapp can drain my vault through the extension?

The extension is designed to minimize this risk through explicit transaction review. A malicious dapp cannot initiate transactions silently. Every transaction request must be visually confirmed by you in the extension’s pop-up interface, which clearly shows the recipient address, amount, and network. You must click “Approve” within the extension for the request to proceed to your workspace’s policy approval stage. This creates a critical checkpoint. Always verify these details match your expected interaction. Combined with your workspace’s multi-user approval policies, this system provides strong protection against unauthorized transfers, even if you visit a compromised website.

What’s the difference between connecting a vault account and a personal wallet in the Fireblocks extension?

These are distinct access modes. Connecting a “Vault Account” uses your organization’s main Fireblocks custody setup, where transactions are governed by enterprise policies and multi-user approvals. This is for institutional asset management. The “Recovered Wallet” or personal mode is for individual use. It allows you to connect a self-custody wallet (like one recovered via seed phrase) through the extension’s interface, giving it the security and user experience of Fireblocks for signing, but without the multi-user policy controls. Your choice depends entirely on whether you are transacting with institutional vault assets or personal wallet assets.