Skip to main content

Metamask

Metamask suffers from several known bugs documented below.

Clearing stuck transactions​

Sometimes transactions in Metamask can get stuck without being performed. You can verify whether a transaction is stuck in Metamask or not by looking up your wallet on Etherscan and comparing the transactions there to the ones visible in your wallet.

caution

Transactions can get stuck in Metamask due to a bug in the UI. This is not the same as transactions that have stalled due to too low gas fees.

To clear transactions stuck in Metamask you'll have to reset the wallet. Do this by opening up Metamask and then click the multi-coloured circle to enter the settings panel.

Metamask wallet browser extension

Go to Settings → Advanced → Reset Account and confirm.

Unknown ENS name​

MetaMask gets its ENS name metadata from OpenSea APIs, which sometimes experience delays in updating new data from the blockchain. These delays can cause ENS names in MetaMask to show up as "unknown". To fix this follow the instructions in:

info
OpenSea: ENS Name Doesn't Show

Doesn't show ENS tokens​

Metamask may not show ENS governance tokens by default. To show them, click on Assets, and then Refresh list.

Metamask wallet browser extension

You will see a notification that Metamask has found a new token for the wallet. Next, click Import.

Metamask wallet browser extension

danger

Be sure the imported ENS token address is: 0xC18360217D8F7Ab5e7c516566761Ea12Ce7F9D72 Avoid interacting or importingtokens that are unknown, as they could be scam tokens.

For more information on token scams, see

Now your ENS voting tokens and/or ENS domain tokens should be visible in your Metamask wallet.

Exaggerated gas costs​

Metamask has a known bug where users are shown an incredibly high gas fee estimate if there isn't enough ETH in the wallet to cover the actual transaction costs.

Metamask wallet browser extension

This can be solved by transferring more ETH into the wallet to cover the actual transaction cost which should be a lot less than what Metamask shows when it's encountering this bug.