'Token 0x1cc80d3249a364d3f7944365d44c351283bb71c2 not found' when trying to deploy to a custom contract created from Token Factory

[skogard]

I was getting a message: 'Token 0x1cc80d3249a364d3f7944365d44c351283bb71c2 not found' when I tried to publish my lazy minted NFT for my custom contract to Rarible.com endpoint for the first time. Here's my contract https://rinkeby.etherscan.io/address/0x1cc80d3249a364d3f7944365d44c351283bb71c2

It was throwing the error for several hours

But after several hours I tried again, and it seems to have been created correctly and I do not get any errors.

Here's the relevant info:

{
    url: 'https://api-staging.rarible.com/protocol/v0.1/ethereum/nft/mints',
    method: 'post',
    data: '{"@type":"ERC721","tokenId":"52103307166765014994970427877263908096137622415890461988507142335625903374694","uri":"/ipfs/bafkreia4y3kgzc5kugp3jb5goke2ka4fznbxccrkt3wf2ou655mdtvjqui","contract":"0x1cc80d3249a364d3f7944365d44c351283bb71c2","creators":[{"account":"0x73316d4224263496201c3420b36cdda9c0249574","value":10000}],"royalties":[],"signatures":["0x20ac5b8bba81aaea15d54c42d4c36b6e5c3d0b029677f655707fface588c78d17b698da086b622d716c0a36311765272f056e7598deb62985b3a7149620c41461b"],"metadata":{"name":"😎","description":"sunglasses","image":"/ipfs/bafkreif4xyzphpfbp2thwsemb4ov2tumnubvygxcjy26zp5uiphtblfddq"},"tokenURI":"/ipfs/bafkreia4y3kgzc5kugp3jb5goke2ka4fznbxccrkt3wf2ou655mdtvjqui"}',
 ...
}

and the error message I was getting earlier:

{
      status: 404,
      code: 'TOKEN_NOT_FOUND',
      message: 'Token 0x1cc80d3249a364d3f7944365d44c351283bb71c2 not found'
}

Is there something additional I need to do AFTER deploying the contract through the token factory to make sure it's immediately mitable instead of having to wait for hours?

[antho1404]

I'm missing a bit of context here, but according to the title "Token 0x1cc80d3249a364d3f7944365d44c351283bb71c2 not found," it might be that you were fetching the token based on the address of the smart contract and not the actual token ID.

Here you have 2 information:

• Contract also called collection in some case that is the contract you've created correctly with the factory (0x1cc80d3249a364d3f7944365d44c351283bb71c2 in your case)
• The tokenId that is required to create an order, for example (52103307166765014994970427877263908096137622415890461988507142335625903374694 in your case)

If this information was correct tho, the delay might come from the following:

• The transaction was not yet minted (pretty unlikely as you had your token id, which is readable only when the tx is minted)
• The chain had a reorg, and basically, on the new version of the chain, your transaction was not yet minted (also quite unlikely as rinkeby is a proof of authority, so should not have any reorg)
• The indexer was slow to synchronize with the chain either because they have some delays in the blocks to avoid issues with reorg, or they just had issues with some nodes that were not in sync.
• They simply have a bug in the API.

You shouldn't have to do anything after creating a new token, but unfortunately, you cannot do anything to speed things up also.
Definitely good to keep track of that and monitor if a delay like that happens again because a few minutes are normal but having the issue for several hours means there is something wrong.

[skogard]

Just happened again. As of right now, it's been exactly 2 hours since the transaction has been mined 0x6a988d6f7e28c67e41bd94720792ce6fbdeeff8c but still not showing up on Rarible.

I don't know if this is a testnet issue and it's working fine on mainnet, but don't want to risk gas fee on mainnet until at least the testnet version is working.

[antho1404]

I also have the error on ropsten with this tx that as for now was minted 20+ minutes ago and which is still not indexed.

Edit: I am now able to fetch the token after 34min

Note: I was also unable to get the balance on this token for the same period of time (I was not using the API but directly the contract through an Alchemy provider). This might help debug, and maybe the issue is actually not from the indexer/API but somehow from the blockchain events.

[evgenynacu]

@skogard sorry for late reply
There were many problems with rinkeby and ropsten nodes lately.

May be you know, ropsten network had many problems latest weeks (including many nodes going into forks)
Our rinkeby node had some problems too. Will think how to fix these errors once and for all