Metamask: Fixing the “Contract Identified” Error in Metamask NFT Viewer
As a Metamask user, you are probably familiar with the frustration of trying to access Ethereum or Polygon Non-Fungible Token (NFT) in the MetaMask Mobile Viewer. One of the most commonly reported errors is the “Contract Identified” message that appears when trying to view NFTs on the platform. Don’t worry; we’ve got you covered! In this article, we’ll walk you through the steps to resolve the “Contract Identified” error.
What is an Unidentified Contract?
Before we dive into the solutions, it’s crucial to understand what causes the “Contract Identified” error on Metamask. When you try to view your NFTs in MetaMask, the contract (a self-executing smart contract) that indicates the ownership and origin of the token is unidentified. There may be several reasons, such as:
- Incorrect or outdated metadata for NFTs
- Incomplete or missing contract code
- Network congestion or latency issues with the blockchain
Troubleshooting steps:
- Check your contract metadata:
Make sure you have provided accurate and complete metadata for your ERC721 NFTs, including:
- Name and description
- Symbol (e.g. .png, .jpg)
- Token ID and type
- SPDX license (e.g. MIT, Apache)
Check the contract metadata in the NFT MetaMask tab by clicking “NFT” > “Show contract” or by pressing Ctrl + Shift + I (Windows) or Cmd + Shift + I (Mac). Make sure all fields are filled in correctly.
- Update contract code: Verify that the contract code is up to date and complete. You can do the following:
- Use a smart contract compiler like Remix or Truffle to compile your contract code.
- Make sure you are using the latest version of MetaMask (version 1.8. 0 or higher) on both the Ethereum and Polygon blockchains.
- Disable Contract Optimization: Disable contract optimization as it can cause issues:
- Go to MetaMask > Settings > Advanced > Contract Optimization
- Turn off the “Optimize Contracts” option
- Check Network Congestion: If you are experiencing network congestion or latency issues with your blockchain, try:
- Check your internet connection and make sure your upload speed is stable.
- Use a different network (e.g. mobile data or Wi-Fi) to reduce latency.
- Network Verification: Verify that your NFTs have been successfully deployed from the Ethereum or Polygon blockchain. You can do the following:
- Verify the contract installation in the blockchain explorer (e.g. Etherscan, PolygonScan).
- Use a tool like MetaMask’s “NFT Deployment” service to validate the contract deployment.
Resolution Steps:
If none of the troubleshooting steps resolve the issue, try the following:
- Reinstall the contract: Try redeploying your NFT contract from scratch using a code editor or IDE (e.g. Remix, Truffle).
- Check for errors: If you recently installed a contract code update, check for any known errors that may be causing this error.
- Contact MetaMask Customer Support:
Contact the MetaMask Support team to resolve this issue. They can provide more specific guidance and troubleshooting steps based on your situation.
Conclusion:
The “Contract Unidentified” error is a common issue when viewing NFTs in Metamask, but don’t worry; we’ve gone over the troubleshooting steps and solutions. By checking contract metadata, updating contract code, disabling optimization, checking for network congestion, checking contract installation, reinstalling contracts, checking for errors, and contacting customer support, you can fix this error and access your Ethereum or Polygon NFTs without any issues.
Additional Resources:
- MetaMask Documentation: [
- Metamask NFT Viewer Guide: [
Leave a Reply