User:SusanneNfc

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



Fireblocks Wallet Extension Installation and DApp Account Recovery Process

Install the browser add-on exclusively from the authorized Chrome Web Store or Firefox Add-ons portal to avoid counterfeit software.

Initial Configuration Steps

After adding the tool to your browser, launch it. You will not create new credentials here. This instrument functions as an interface for an existing institutional-grade custody platform.


Select your organization's designated server environment (e.g., Production, Sandbox, Development).
A new browser tab will open, directing you to the platform's login page. Authenticate using your corporate Single Sign-On (SSO) credentials.
Post-authentication, return to the browser add-on. It will now display your accessible vaults and associated public addresses.
Define a unique nickname for this browser instance to differentiate it from other authorized sessions.

Approving Transactions

Any transfer of assets initiated through a connected decentralized application requires multi-party confirmation. The add-on will generate a transaction payload. This must be reviewed and approved by the configured number of policy administrators within the main custody platform dashboard, not in the browser itself.

Re-linking to Decentralized Applications

If your browser session refreshes or an application disconnects, follow this precise sequence.

Re-establishing Connection

Ensure the browser add-on is unlocked and displaying your vault information.
Navigate to the specific decentralized application (e.g., a trading or lending protocol).
Locate the application's "Connect" button, typically found in the top-right corner of its interface.
From the list of connection options, choose "WalletConnect". A QR code will appear.
Within the browser add-on, click the "WalletConnect" icon and select "New Connection".
Scan the QR code presented by the application using this interface. The link will establish automatically.


Critical: You are only linking to the application's front-end. Private keys never leave the segregated custody environment. Transaction signing always routes back through your organization's policy workflow.

Address Whitelisting for Efficiency

To minimize transaction approval delays for frequent interactions, pre-approve destination addresses within your organization's policy settings. Submit commonly used DeFi contract addresses (like Uniswap V3 Router or Aave Lending Pool) for internal review and whitelisting. This allows specific interactions to proceed with fewer manual confirmations.


Regularly audit connected applications within the add-on's settings. Revoke permissions for any protocols you no longer utilize to reduce potential attack vectors.

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.


Initial configuration mandates connecting your vault to the new interface; this requires administrator approval within your organization's policy engine. Define transaction policies–like multi-signature quorums and whitelisted addresses–before initiating any asset transfer. These rules are enforced automatically, preventing unauthorized withdrawals.


For re-establishing connectivity with decentralized applications, first ensure the browser plugin is active and logged into the correct institutional workspace. Then, navigate to the application's interface. You will typically encounter a prompt to select a connection method; choose the provider option and authorize the link. This grants the application permission to request transactions, which must still comply with your pre-set governance rules.


If an application fails to detect your connected vault, refresh its page and check the plugin's icon for a logged-in status. Clearing the browser's cache for that specific site often resolves persistent recognition issues. Never approve connection requests from unfamiliar domains.


Transaction signing occurs through your configured workflow. A pending operation will appear in the dashboard, notifying designated approvers via email or mobile alert. The process remains incomplete until the required number of confirmations is secured, adding a critical security layer against single points of failure.


Maintain operational integrity by routinely reviewing and updating address books and spending limits. Conduct periodic access audits for former team members. This proactive management minimizes friction during high-value or time-sensitive operations while preserving institutional security standards.

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

Connecting an existing vault requires specific access. First, ensure you are using the same Fireblocks account that manages the vault. The extension doesn't hold assets itself; it's a gateway. You need the proper policy permissions set within the Fireblocks console. An admin for your organization must have configured a "Connect Browser Extension" policy rule for your user role and designated the vaults you are allowed to access. Without this rule, the extension will not show your vaults. Check with your organization's Fireblocks administrator to confirm these settings are in place.

Can I recover access to decentralized applications (dApps) if I uninstall and reinstall the Fireblocks extension?

Yes, your dApp connections can be restored. The recovery process relies on your Fireblocks MPC-CMP key architecture. When you reinstall the extension and log in with your authenticated credentials, you regain access to your vaults. The extension itself does not store permanent connection data locally. To reconnect to a specific dApp like Uniswap or Aave, you simply visit the dApp's website and initiate a transaction or connection request. The Fireblocks extension will reappear, asking for transaction approval according to your organization's policies. Your wallet addresses remain unchanged, so dApps will recognize them, but you may need to manually re-approve the connection from the dApp's interface.

What's the difference between the Fireblocks extension and a regular MetaMask wallet?

The core difference is custody and control. MetaMask is a self-custody, single-user wallet where you alone manage a seed phrase. The Fireblocks extension is an interface for an institutional-grade custody platform. You are not managing private keys directly; signatures are generated through Multi-Party Computation (MPC) across separate nodes. Access is governed by customizable policies set by your organization, requiring multiple approvals for transactions over certain limits. It's designed for teams and businesses, not individuals. The extension provides a familiar browser-based way to interact with dApps, but the security and operational model behind it is fundamentally different.

After setup, my transaction is stuck on "Awaiting Approval" in the extension. What does this mean?

The "Awaiting Approval" status indicates your transaction is pending within Fireblocks' policy engine. It has been submitted but requires one or more additional approvals from other designated users in your organization before it can be broadcast to the blockchain. This is a security feature, not an error. Check your organization's workflow in the Fireblocks web console. You may need to notify other approvers. The transaction will also appear in the Fireblocks mobile app for those with approval rights. If the transaction times out, it will be rejected, and you will need to submit it again.

Is my browser data, like history or bookmarks, accessible to Fireblocks or my organization through the extension?

No. The Fireblocks browser extension is designed with a limited scope of permission. It operates only on specific web pages you visit, primarily to detect wallet connection requests or transaction prompts from dApps. It cannot read your general browsing history, bookmarks, or personal data. Its function is to inject a secure interface for transaction signing and to communicate with the Fireblocks backend when you interact with a supported dApp. Your organization's administrators cannot see your personal browsing activity through the extension.

I installed the Fireblocks browser extension but my existing dapp connections aren't working. How do I recover or reconnect my dapps with the new extension wallet?

Your dapp connections are tied to a specific browser and wallet address. Since the Fireblocks extension creates a new wallet interface, you'll need to reconnect each dapp manually. First, ensure you are logged into the correct Fireblocks workspace and vault account within the extension. Then, visit each decentralized application. When the dapp prompts you to connect a wallet, select the Fireblocks extension from your browser's wallet list. You will likely need to approve this connection request within the Fireblocks extension's interface, which may require policy approval from your workspace administrators. After approval, the dapp will recognize your new Fireblocks wallet address. Note that any existing transactions or data tied to your old wallet address within those dapps will not automatically transfer, as the blockchain sees these as separate accounts.

Can I use the Fireblocks extension with a vault account that already has assets, or do I need a new one?

You can absolutely use an existing vault account that holds assets. The extension is an interface for accessing and signing transactions from vaults already set up in your Fireblocks platform. During setup, after installing the extension and logging in, you will see a list of available vault accounts from your workspace. Select the vault you wish to connect to the browser. The extension does not create a new vault; it grants the browser permission to initiate transactions from the chosen vault. All existing assets and transaction policies for that vault remain in effect. This means any transaction you sign through a dapp will still require the same approvals defined in your Fireblocks workflow policies.