Failed to import ERC721A(v4.1.0) contract on OpenSea

[jovijovi]

ERC721A(v4.1.0) contract deployed on Polygon(mumbai), but encountered some problems.

• Problems 1: Failed to import ERC721A contract on OpenSea.

  • Error message:

    We couldn't find this contract. Please ensure that this is a valid ERC721 or ERC1155 contract deployed on Mumbai and that you have already minted items on the contract.
    

    PS: It's OK if downgrade to v4.0.0

• Problem 2: Failed to verify contract code on https://mumbai.polygonscan.com

  • Error message:

    Error! Unable to generate Contract ByteCode and ABI
    

• A project repo for test ERC721A

  • Github: https://github.com/jovijovi/ether-minter/tree/v0.6.5
  • Tag: v0.6.5
  • Contract code: https://github.com/jovijovi/ether-minter/tree/v0.6.5/contracts/Avatar
  • Solidity compiler version: 0.8.9
  • deps:

    {
        "@openzeppelin/contracts": "4.6.0",
        "erc721a": "4.1.0",
        "ethers": "5.6.9"
    }

Thank you :D

[Vectorized]

Try the following:

• Publish on Rinkeby.
• Choose a different RPC provider (Infura, Alchemy).
• Mint several tokens in multiple transactions.
• npx hardhat clean; npm clean-install

If all else fails, just use the last configuration that works for you.

[jovijovi]

Try the following:

• Publish on Rinkeby.
• Choose a different RPC provider (Infura, Alchemy).
• Mint several tokens in multiple transactions.
• npx hardhat clean; npm clean-install

If all else fails, just use the last configuration that works for you.

Test ERC721A v4.0.0 & v4.1.0:

• Rinkeby
  • Publish on Rinkeby is OK 👍
  • Contract: https://rinkeby.etherscan.io/address/0x6Ae2749999fbdd2fFEFb97a59831b01a782e61fa
• Polygon mumbai
  • It will fail to import contract on OpenSea testnet if mint quantity >= 29 in one tx
  • Error msg:

    We couldn't find this contract. Please ensure that this is a valid ERC721 or ERC1155 contract deployed on Mumbai and that you have already minted items on the contract.
    

  • Contract: https://mumbai.polygonscan.com/address/0xcb4b54182401656991ce80b13fe38efe803953e8
  • Is this a limitation of OpenSea testnet?

[roderik]

I have the same, including on the mainnet for polygon

[alvinlubetkin]

Im having the same issue with mumbai, rinkeby, eth mainnet and polygon. Downgrading to 0.4.0 didnt seem to help either
Anybody know how to get around this?

[softmuneeb]

You should create this issue also on opensea repo.

[halversonmd]

I had this same problem. The solution for me wasn't with Opensea, it was the updated ERC721A API. One step Opensea takes to validate a contract is calling supportsInterface for ERC721. The old way to support this function is broken with v4.x. The breaking change and solution is documented here and here.

Make sure to test this method yourself with something like this:

const nftContract = new web3.eth.Contract(contract.abi, contractAddress)

// - IERC165: 0x01ffc9a7
// - IERC721: 0x80ac58cd
// - IERC721Metadata: 0x5b5e139f
// - IERC2981: 0x2a55205a
nftContract.methods.supportsInterface('0x80ac58cd').call(
    {}, 
    function(error, response) {
        // Opensea requires response to be true for an ERC721 / ERC721A contract
        console.log('supportsInterface response: ', response);
        console.log('error: ', error);
    }
)