BSC Testnet NFT sync lost

Technical Issue Reporting
#1

Hello, maybe the topic is duplicated, sorry.

I can see that sync is lost on BSC testnet.

For example, the request “nft/{address}/owners” displays an old data:

curl -X 'GET' \
  'https://deep-index.moralis.io/api/v2/nft/0xd7FC216b871A1606F21808246F58D2cCa00E0eeE/owners?chain=bsc%20testnet&format=decimal' \
  -H 'accept: application/json' \
  -H 'X-API-Key:'

In response: “synced_at” : “2022-04-30T01:55:41.861Z”.

However “nft/{address}/transfers” shows an actual data with the latest ERC1155 transfer.

curl -X 'GET' \
  'https://deep-index.moralis.io/api/v2/nft/0xd7FC216b871A1606F21808246F58D2cCa00E0eeE/transfers?chain=bsc%20testnet&format=decimal' \
  -H 'accept: application/json' \
  -H 'X-API-Key:'

In response: “block_timestamp”: “2022-05-10T14:06:32.000Z”.

Tha latest transfer: https://testnet.bscscan.com/tx/0x4a16f12f2b96b8afdb2cd601518fb0234c8a7ab9dfec877ee9148d49e3375039

#2

did you notice issues in what nft owners endpoint returns for that contract, as of returned owners?

#3

Yes, but now it seems to be correct.

Before, there was wrong information in “nft owners” request.

Update: It seems like nft/{address}/transfers syncs faster than nft/{address}/owners. Now I have same issue.

#4

you say that in nft owners there is old information, and in nft transfers it is up to date?
what is the delay that you notice?

#5

Correct. The delay is at least several hours.

#6

you still have that issue now?

in case that you do, can you give an example?

#7

Now, it syncs on time. Thank you!

1 Like