I transferred an ERC-721 token to another address yesterday, then I tried to get my own NFTs from this endpoint https://deep-index.moralis.io/api/v2/0xE69545aaC953cd71617921bd1481D6B2CB32D6a5/nft it still got the NFT that transferred to another one in the response, why?
It seems like working fine now. But I am curious what did cause the problem?
It could have been related to a caching issue on our side.
How to prevent this problem? because my site relies on this endpoint.
I use this endpoint to get users’ NFTs.I had transferred an NFT to another wallet, but it persisted in my wallet.
when you have problems you can post here and we will investigate, this is not expected to happen
What I mean is the NFT that I transferred was saved on the blockchain, but I still see the NFT from this endpoint https://deep-index.moralis.io/api/v2/{wallet_address}/nft
this is still happening now?
No. It was happening yesterday.
ok, if you get into similar problems in the future, you can post here and we will investigate
1 Like
Hi, It occurred to me again.
according to this transaction https://rinkeby.etherscan.io/tx/0x67147ed5d54dcd04756d032d8b256f73b59a6b364cebb1d6051722f847b203a4
account1 = 0xe9c6e64f40eb8d0aee1bac3568d48ca848acb166
account2 = 0x05f6033ab88ee6ed3f5a38a978aa27155c78e183
account1 has transferred the token to account2, but when I use this endpoint https://deep-index.moralis.io/api/v2/0xe9c6e64f40eb8d0aee1bac3568d48ca848acb166/nft the token that been transferred since 10 days ago still exists on the response.
How do I make sure this problem will not happen in production site?