Fireblocks Wallet Extension Installation and DApp Account Recovery Process
Install the browser add-on directly from the Chrome Web Store or equivalent marketplace; verifying the publisher’s authenticity prevents counterfeit software. This component acts as your primary gateway, requiring configuration before any transaction can be signed. You will need administrator approval from your organization’s policy engine to link this interface with your institutional vault.
Establish a connection by generating a new key pair within the add-on’s interface. This action produces a QR code, which must be scanned using your mobile device running the institutional custody application. The pairing process cryptographically links the browser tool to your secured holdings without exposing private keys, which always remain in hardware-isolated environments. Finalize by assigning a specific, descriptive name to this browser profile for clear identification among multiple endpoints.
Should you encounter a new browser or a cleared cache, regaining access to decentralized applications is straightforward. Re-install the browser plug-in and select the option to restore an existing connection. You will again be prompted to authenticate via your mobile device–no keys are lost, as they are managed separately. This process reinstates transaction signing capabilities for all previously connected applications, preserving your operational history and permissions.
Configure transaction policies within your organization’s administrative console before initiating transfers. These rules define approval workflows, whitelisted addresses, and transfer limits. Each interaction with a smart contract or transfer request will route through these governance protocols, requiring the stipulated number of confirmations from designated co-signers. This layered approach ensures no single point of failure can compromise asset movement.
FAQ:
I installed the Fireblocks wallet extension but can’t connect it to my Fireblocks account. What am I doing wrong?
The most common issue is attempting to use the wrong login method. The browser extension does not use your regular Fireblocks Platform email and password. Instead, you must generate a specific “Browser Extension Key” from within your main Fireblocks Platform account. Log into the web platform, navigate to the “Browser Extension” section in your settings, and create a new key. You will receive a one-time code. Use this code, along with your platform email, to log into the extension itself. The extension is a separate client that authenticates via this special key, not your primary platform credentials.
How do I recover access to my decentralized applications (dApps) if I switch browsers or computers?
Your dApp connections and wallet permissions are not stored in the browser’s local storage like some non-custodial wallets. Since Fireblocks is an institutional-grade service, all configuration is tied to your organization’s policy engine and your user account. To recover access, simply install the Fireblocks extension on the new browser or machine and log in using your Browser Extension Key. Once authenticated, your vault accounts will populate. You can then reconnect to any dApp (like Uniswap or Aave) by approving a new connection request. Your transaction policies and approved addresses remain intact as they are managed on the Fireblocks Wallet recovery phrase backend, not locally.
Is there a difference between the Fireblocks web platform and the browser extension? I’m confused about their roles.
Yes, they serve distinct purposes. The Fireblocks web platform is your administration and policy hub. Here, administrators set transaction rules, manage vaults, and review approvals. The browser extension is your operational interface for interacting with dApps. It acts as a bridge: when you initiate a transaction on a dApp, the extension intercepts it and sends it to the Fireblocks platform for policy checks and approvals. You manage funds and rules on the web platform; you sign and execute transactions on-chain through the extension. Both need to be set up and linked for the system to work.
Can I connect multiple vault accounts from my organization to a single dApp using the extension?
The extension supports connecting multiple vault accounts. When you connect to a dApp, a pop-up window will display the list of vaults your user account has permission to access. You can select one or several accounts to link to that specific dApp. Later, when performing transactions on that dApp, you can choose which of the connected vault accounts you want to use for the action. This allows for flexible management of different asset pools or departmental funds within a single dApp interface. The transaction will still be subject to the policies set for the chosen vault in the Fireblocks web platform.
I installed the Fireblocks browser extension but my dApps don’t detect my wallet. What are the most common fixes?
First, ensure the extension is active and unlocked. A small icon in your browser’s toolbar should be colored, not grayed out. Next, check which network the dApp is using. The Fireblocks extension might be set to a different blockchain (like Ethereum Mainnet) while the dApp is on a testnet (like Goerli). Switch the network in both the extension and the dApp to match. Also, some dApps require you to manually connect your wallet. Look for a “Connect Wallet” button on the dApp’s site, click it, and select “Fireblocks” from the list of options. If problems continue, try clearing your browser cache or restarting the browser entirely.
