User:MichelineKohn98

img width: 750px; iframe.movie width: 750px; height: 450px;
Fireblocks wallet extension setup and dapp recovery guide



Fireblocks Wallet Extension Setup and DApp Recovery Process Guide

Install the browser add-on solely from the authorized developer portal to prevent counterfeit software.

Initial Configuration Steps

After adding the tool to your browser, launch it. You will not create new credentials; instead, you will establish a connection to an existing institutional vault. This requires multi-party approval.


Log in to your enterprise custody platform using your corporate credentials.
Navigate to the 'Browser Add-on' section within the platform's settings panel.
Generate a unique pairing code. This code is time-sensitive and expires after 5 minutes.
Switch back to the add-on interface and input the provided code.
Approve this connection request from your mobile authorization device. A minimum of two authorized personnel must typically consent for institutional accounts.

Defining Transaction Policies

Before interacting with decentralized applications, configure governance rules. These are set within the main custody dashboard, not the add-on.


Specify which web domains are permitted for interactions.
Set transaction volume limits per day and per single operation.
Designate which asset types can be transferred (e.g., ETH, USDC).
Assign specific authorizers for different transaction tiers.

Reconnecting Decentralized Applications

If your browser cache clears or you switch machines, applications lose their linkage. Re-establishing access is a permissions exercise.


Visit the desired application's website. When prompted to select a connection method, choose the institutional add-on from the list. The add-on will display a detailed connection request, showing the application's name and requested permissions. Scrutinize this. Authorize the link via your mobile device, following the same multi-signature protocol as a fund transfer. The application's interface will then reflect your vault's address and balances.

Addressing Failed Linkages

Failed connections usually stem from policy blocks. Check these three areas in the custody platform:


Domain Allowlist: Confirm the application's exact URL is approved.
Pending Approvals: The connection request may be awaiting consent from other stakeholders on the internal platform.
Feature Status: Ensure the browser integration feature itself is still active and not administratively disabled.


Never share your pairing codes or approve connection requests from unrecognized websites. Treat each link request with the same scrutiny as a payment transaction.

Fireblocks Wallet Extension Setup and DApp Recovery Guide

Install the software directly from the official Chrome Web Store or Firefox Add-ons marketplace to guarantee authenticity and avoid malicious clones.


Configuration requires defining transaction policies within your enterprise console before the browser tool becomes operational; assign specific user roles and approval thresholds for different asset types or volume limits, which enforces internal controls automatically during every interaction.


If you lose access to a browser profile, reconnect the application by scanning a new QR code with your mobile device–the vault’s security model and delegated signing authority remain intact, as private keys never leave the institution’s custody.


For re-establishing connections with decentralized applications, manually re-approve the linked addresses in the interface’s 'Connected Sites' section; this resets permissions without affecting underlying account structures or requiring fresh on-chain transactions.


Test a small transfer first.

FAQ:
I installed the Fireblocks browser extension but can't connect my existing vault. What am I doing wrong?

The most common issue is attempting to connect a vault that wasn't initially created or configured for use with the Fireblocks browser extension. The extension is designed to work with a specific type of vault: a **MPC-CMP wallet**. If your existing vault is a different type (like an MPC-ECDSA wallet), it cannot be linked to the extension. You must create a new vault specifically through the extension's setup flow. Log into your Fireblocks Console, go to the "Web3" section, and follow the "Create New Wallet" process from there. This will ensure you generate the correct wallet type that is compatible with the browser extension.

How do I actually connect the Fireblocks extension to a dapp like Uniswap?

Once the extension is installed and you've set up a compatible MPC-CMP vault, connecting to a dapp is straightforward. First, navigate to the dapp's website. Look for a "Connect Wallet" button, which is usually in the top corner. Click it, and a list of wallet options will appear. Select "Fireblocks" from this list. Your browser extension should automatically trigger a pop-up window asking you to approve the connection. Review the dapp's permissions in this pop-up and confirm. The dapp will then show your connected wallet address, and you can begin transactions, which will require additional approvals via your Fireblocks policy workflow.

My laptop broke. How do I recover my Fireblocks extension wallet on a new computer?

Recovery is possible because your wallet is managed by the Fireblocks platform, not stored solely on your old device. On your new computer, simply install the Fireblocks browser extension again. When you open it, choose the "Sign In" or "Recover Access" option. You will be redirected to log into your main Fireblocks Console account using your organization's credentials. After authentication, you will see a list of vaults under your control that are compatible with the extension. Select the correct MPC-CMP vault you used before. Your access is restored immediately, as the extension is just an interface; the wallet's security model and keys are maintained by Fireblocks's infrastructure.

What's the difference between approving a transaction in the extension and in the Fireblocks web console?

The browser extension acts as a gateway for initiating and approving certain types of transactions, specifically those involving dapps and Web3 interactions. When you approve a transaction in the extension, you are providing one part of the multi-party computation (MPC) signature. However, this single approval is typically not enough. Most enterprise setups require additional approvals based on your organization's pre-defined policy rules. These further approvals must be completed by other designated users within your organization via the main Fireblocks web console or mobile app. The extension starts the process, but the console enforces the security policy.

Can I use the extension with multiple vaults or switch between them easily?

Yes, the extension supports multiple compatible MPC-CMP vaults, but you can only be actively connected to one at a time within a specific browser profile. To switch between vaults, click on the Fireblocks extension icon in your browser's toolbar. In the pop-up window, you should see your currently connected vault address. Look for a "Switch Vault" or similar option. This will present a list of all your eligible vaults. Selecting a different one will change the active connection. Remember that any dapp you are connected to will be disconnected when you switch, and you will need to reconnect the dapp using the new vault's address.

I installed the Fireblocks browser extension, but my existing dapps don't recognize it as a connected wallet. How do I fix this?

This is a common issue. The Fireblocks extension operates differently from standard personal wallets like MetaMask because it connects to your institutional Fireblocks workspace. First, ensure you are logged into the correct workspace within the extension. Then, visit the dapp you want to use. Instead of the dapp automatically detecting the extension, you must manually connect it. Look for a "Connect Wallet" button on the dapp's website. Click it and select "Fireblocks" or "WalletConnect" from the list of wallet options. If you choose WalletConnect, a QR code will appear. Click the QR code icon in your Fireblocks extension to scan it. This establishes the connection directly between the dapp and your Fireblocks-managed vault. You may need to approve this connection request from your Fireblocks mobile app, following your organization's transaction policy.

If my computer crashes and I need to set up the Fireblocks extension on a new machine, what steps guarantee I can recover my access and dapp connections?

Recovery depends entirely on your access to the Fireblocks platform itself, not on local browser data. On your new computer, simply install the fireblocks wallet browser extension extension from the official Chrome Web Store or Firefox Add-ons site. When you open it, you will log in using your Fireblocks credentials (email and authentication method). This authenticates you with the Fireblocks cloud platform. Your vaults, assets, and user permissions are managed centrally there, so they will appear immediately after login. For dapp recovery, you will need to reconnect to each decentralized application manually, as described in the previous answer. Your transaction policies and whitelists are part of your workspace settings and remain intact. The critical point is that your private keys are never stored on your browser or computer; they are secured in Fireblocks' infrastructure. Therefore, setting up a new device only requires verifying your identity as an authorized user of the platform.