In the api, https://deep-index.moralis.io/api-docs/#/token/getAllTokenIds, it mentions the order of results in descending order of mining. But many times we are getting out of order results. This causes problem from us, since we rely on ordering to sync the data in our backend db. Can you please look into this. I think this is easily reproducible for contracts which are actively minted.
It would be easier to check if you give examples
Hey, I took the screenshot when the issue happened.
In the above image , token_id 50 was minted long before , but in the result it came in the first position.
can you paste that token_address?
0xC71a0306a0A628C616DAC42097bDc21EcDBc5d9d
1 Like
we updated the documentation in web3api page, it is not sorted on mint time