img width: 750px; iframe.movie width: 750px; height: 450px; Fireblocks wallet extension setup and dapp recovery Fireblocks Wallet Extension Installation and DApp Recovery Process <br>Install the provider's browser add-on exclusively from the official Chrome Web Store or Firefox Add-ons portal. Third-party download sources pose a significant security risk.<br> Initial Configuration Steps <br>After installation, the add-on will request a connection to your existing vault. You will need to authenticate using your existing institutional account credentials. This process does not create a new vault; it links the browser interface to your established infrastructure.<br> Defining Transaction Policies <br>Before initiating any transfers, establish clear transaction policies within your organization's dashboard. These rules govern approval workflows, specify allowed asset types, and set transfer limits. A typical policy might require two out of three designated administrators to approve any transaction exceeding 0.5 BTC.<br> Authorizing Browser Connectivity <br>Navigate to your organization's settings and explicitly grant permission for the newly installed browser add-on. This step authorizes the specific browser instance to act as a transaction endpoint, ensuring only approved devices can initiate actions.<br> Reconnecting to Decentralized Applications <br>If a decentralized application loses its connection to your funds, follow this precise sequence to re-establish the link.<br> Open the decentralized application in your browser and navigate to its connection interface. Click the browser add-on icon in your toolbar to activate it. Select the specific vault account you intend to use with the application. The application will receive a new connection request; confirm this request within the add-on's interface. <br>Transaction signing occurs directly within the add-on's window. For every operation, you will review details like recipient address, amount, and network fees. The approved transaction policy will dictate the required number of confirmations from your team before the action is broadcast to the network.<br> Managing Network & Gas <br>Configure default networks for each asset. For Ethereum-based operations, set a custom gas limit and max priority fee. For complex smart contract interactions, a gas limit of 300,000 units may be necessary to prevent transaction failure.<br> <br>Regularly audit connected sites via the add-on's settings. Revoke access for any applications no longer in use. This minimizes the attack surface and maintains a clean authorization list.<br> Fireblocks Wallet Extension Setup and DApp Recovery <br>Install the browser add-on solely from the official Chrome Web Store or Firefox Add-ons portal to eliminate the risk of counterfeit software. Immediately after installation, you must link the add-on to your institutional vault by scanning a QR code with your mobile device; this step physically separates transaction signing from your browser environment, a core security principle. Configure transaction policies directly within the web console, setting explicit rules for asset types, volume limits, and required approvals before initiating any on-chain interactions.<br> <br>If browser data is cleared or you switch machines, reconnect the add-on to your existing vault using the original QR code or backup configuration file–your assets and policy engine remain untouched on the server side. Re-establishing connection automatically restores access to all previously whitelisted decentralized application addresses and contract interactions, as these permissions are stored at the account level, not locally.<br> <br>For lost device scenarios, vault administrators can revoke that specific add-on's authorization via the policy manager, preventing any further signing attempts while a new instance is provisioned under the existing, unchanged corporate governance framework.<br> FAQ: I installed the Fireblocks browser extension, but my existing wallets aren't showing up. What did I do wrong? <br>This is expected behavior. The Fireblocks browser extension itself does not store or display your existing vaults and wallets. It acts as a secure bridge. To see your assets and transaction history, you must log into your main Fireblocks web console. The extension's purpose is to facilitate secure transaction approvals and dapp connections from that console. Once you initiate a transaction or dapp connection in the web console, a notification will appear in the extension for you to review and sign.<br> Can I recover access to my Fireblocks-managed assets using only the browser extension if I lose my computer? <br>No, you cannot. The extension alone holds no recovery information. Your access is tied to your Fireblocks Wallet extension download organization and its policy rules. Recovery is an administrative process. You would need to contact your organization's Fireblocks administrator. They can reassign your user account to a new device. You would then reinstall the extension on the new machine, log into the Fireblocks web console, and go through your organization's defined approval workflows to regain access. Your private keys remain secured in the Fireblocks infrastructure throughout this process.<br> How does connecting a dapp through the extension work? Does it expose my private keys? <br>The process keeps keys secure. When you connect to a dapp, you first initiate the connection from within your Fireblocks web console, not the dapp's website directly. The console generates a connection request. This request appears in your browser extension for review. You see the dapp's details and permissions. After you approve in the extension, Fireblocks creates a digital signature for the connection using its secure MPC technology. Your private keys are never exposed to the browser, the extension, or the dapp. The dapp receives only a public address and a signed message, granting it permission to interact with that specific address under the rules set by your Fireblocks policy.<br> What happens if I clear my browser cache or use a different browser? Will my dapp connections break? <br>Yes, they will likely break. The dapp connection session is often tied to the browser's local storage. If you clear this data or switch browsers, the dapp will lose the active session token. Your wallet address and assets remain safe in your Fireblocks vault. To reconnect, you must repeat the full connection process: go to the dapp, initiate a connection, open your Fireblocks web console to generate the request, and approve it via the extension in the new browser session. It's a fresh handshake each time the local session data is lost.<br> Is there a difference between approving a transaction and connecting a dapp in the extension interface? <br>The approval interface is similar, but the context differs. For a transaction, the extension will show details like amount, destination address, network fees, and the specific blockchain network. For a dapp connection, the extension displays the dapp's name (like Uniswap or Compound), the requested network (Ethereum Mainnet, etc.), and the permissions it seeks (like viewing your address). In both cases, you must verify these details match your intent before approving. The extension's role is to present this information clearly for your final review, blocking any attempt by a website to auto-approve.<br>