What is WalletConnect?

WalletConnect is an open protocol that allows secure communication between wallets and Web3 decentralized applications (dApps). Any transaction or off-chain message payload passed through WalletConnect is symmetrically encrypted through a shared key between the dApp and the wallet.

WalletConnect is one of the most widely used Web3 integrations with hundreds of dApps that are currently supported through it. Fireblocks has integrated WalletConnect as part of our infrastructure, allowing you to interact with Web3 with the security benefits of the Fireblocks Vault.

You can use the Fireblocks WalletConnect integration in your workspace to seamlessly:

1. Create connections to new dApps that work with WalletConnect.
2. Access and manage your existing connected dApps.
3. Sign contract calls within your secure Fireblocks Vault, without installing additional extensions or relying on external gateways.

Your first step to initiate a connection between a dApp and one of your Fireblocks vault accounts is through the dApp's website, not your Fireblocks Console. The steps to connect are summarized below.

Connecting to a dApp using WalletConnect

You can use your computer or mobile device to connect to dApps via WalletConnect.

Computer

1. Access the dApp's website, and select Connect to a wallet. The instructions or button name might vary dApp to dApp.
2. Select WalletConnect.
3. Select Desktop, and then select Fireblocks from the list of wallets.
   
4. Select a vault account to connect to the dApp, the blockchain network you want to connect through, and a preset fee rate. You can only connect one instance of the same dApp to each vault account.

Mobile

1. Access the dApp's website, and select Connect to a wallet. The instructions or button name might vary dApp to dApp.
2. Select WalletConnect. If connecting to a dApp on the Osmosis network, select Keplr Mobile. If connecting to a dApp on the Tezos network, select Trust Wallet.
3. In your Fireblocks mobile app, tap Scan or select Settings > Connect DeFi App.
   
4. Scan the QR code that the dApp displays.
5. Select a vault account to connect to the dApp.
   • If you have multiple user accounts on the same device, first select your user from the list.
   • You can only connect one instance of the same dApp to each vault account.
6. Choose a preset fee rate and the blockchain network you want to connect through.
   

   Note

   If you are connecting to a dApp that does not support this network, the connection will fail.

You're now connected! What's next?

After you're connected to a dApp, transactions you create on that dApp will be processed through Fireblocks and submitted through your user account for approval and MPC signing.

Your WalletConnect sessions automatically expire after seven days. After this expiration, you must reconnect to the dApp to continue using it. Fireblocks recommends disconnecting from dApps when not actively using them.

Managing your WalletConnect connected dApps

In your Fireblocks Console, navigate to Web3 Access from the left-hand menu. All your existing connected dApps for your workspace are listed in this tab.

To switch the view from all connected dApps to only the ones you are connected to, select All Connections in the top-right corner of the page. Select My Connections to view just your connected dApps again.

Configuring a connected dApp

To configure a connected dApp, select that dApp's card. You may:

• Change the vault account linked to this dApp.
• Change the preset fee.

Select Submit to complete the changes.

Disconnecting from dApps

To disconnect your workspace from a dApp, select X when hovering over the dApp’s card. Alternatively, you can select the card and then select Disconnect. Only Non-Signing Admins, Admins, or the user who created the connection can disconnect from the dApp.

You can reconnect to the dApp when needed.

Rate limits when using WalletConnect

In order to provide stability and security, Fireblocks continuously monitors WalletConnect traffic to identify patterns that may negatively affect the platform.

If traffic between a workspace and a dApp is too high, we may temporarily restrict the dApp session. We only use these rate limits when traffic appears abnormal.