Skip to main content
All CollectionsAccount Management
Managing Wallet Overrides
Managing Wallet Overrides

Learn how to manage wallet overrides to ensure Hana Wallet is used instead of MetaMask, Polkadot.js, or Keplr when interacting with dApps.

David avatar
Written by David
Updated over a week ago

Managing wallet overrides in Hana is a powerful feature that allows you to ensure Hana Wallet is used in place of other popular wallets like MetaMask, Polkadot.js, and Keplr. This feature is only available in the desktop extension version of Hana.

Step-by-Step Guide to Enabling Wallet Overrides

  1. Open Hana:

    • Launch the Hana Wallet extension on your desktop.

  2. Click or Tap the Hamburger Menu:

    • In the top right corner of the Hana interface, click or tap the hamburger menu (three horizontal lines).

  3. Click or Tap Settings:

    • From the dropdown menu, select "Settings" to access the wallet settings.

  4. Click or Tap Advanced:

    • In the settings menu, select "Advanced" to view advanced options.

  5. Toggle Wallet Overrides:

    • Simply toggle the options to override MetaMask, Polkadot.js, and/or Keplr. This ensures that Hana Wallet will be used instead of these wallets when interacting with dApps.

What Does Overriding a Wallet Mean?

When you override a wallet like MetaMask, Polkadot.js, or Keplr with Hana, it means that whenever a dApp presents login capabilities for these wallets, Hana Wallet will automatically take over.

Instead of the selected wallet's interface popping up, Hana will handle the connection, authorization, and interaction with the dApp.

Overriding MetaMask

  • Why Override MetaMask? MetaMask is one of the most popular Ethereum wallets, widely supported across many dApps. However, if you prefer using Hana Wallet, overriding MetaMask ensures that you can still use Hana even when a dApp only presents MetaMask as an option.

  • How It Works: Once the override is enabled, whenever a dApp prompts for MetaMask login, Hana Wallet will step in to authorize the connection instead. This integration allows you to enjoy the functionality of Hana Wallet across a broader range of dApps.

Overriding Polkadot.js

  • Why Override Polkadot.js? Polkadot.js is the go-to wallet for interacting with Substrate-based blockchains like Polkadot and Kusama. By overriding Polkadot.js, you can use Hana Wallet to interact with these ecosystems, even if the dApp doesn't directly support Hana.

  • How It Works: When a dApp requires Polkadot.js for connection, enabling the override will allow Hana Wallet to handle the connection process. This ensures that all your Substrate-based interactions can be managed through Hana.

Overriding Keplr

  • Why Override Keplr? Keplr is a popular wallet for the Cosmos ecosystem. If you prefer using Hana Wallet, enabling the override will let you use Hana for Cosmos-based dApps that typically require Keplr.

  • How It Works: With the override enabled, Hana Wallet will replace Keplr in the connection process, allowing you to manage your Cosmos assets through Hana Wallet even on dApps that primarily support Keplr.

Benefits of Using Wallet Overrides

  • Broader Compatibility: Overriding ensures Hana Wallet can be used with a wider range of dApps, even those that don’t explicitly support Hana.

  • Unified Wallet Experience: Manage all your assets across different blockchains in one place with Hana, without needing to switch between different wallet extensions.

  • Enhanced Control: Take full control of your dApp interactions by choosing to use Hana Wallet for everything, regardless of the default wallet the dApp supports.

Managing wallet overrides in Hana Wallet gives you the flexibility to use Hana across a broader range of dApps, ensuring a seamless and unified experience. Whether it’s MetaMask, Polkadot.js, or Keplr, Hana Wallet can take over the connection process, allowing you to interact with your favorite dApps using Hana.

Need Help?

If you have any questions or need further assistance, visit our Support Center for more articles and resources, or contact our support team.

Did this answer your question?