Wait for confirmations

[ankur2136]

After minting a NFTs sometimes the MyMints screen still shows the old NFT count probably because the transaction is not yet complete when we fetch the details.

[ankur2136]

As per code we are already waiting for confirmations with a timeout for 30 seconds. So unsure why the rpcs are sometimes spitting older information. Maybe there is a delay in processing somewhere.

[ankur2136]

I think the issue here is that when we mint, we wait for the commitment to be Finalized but when we are polling the NFTs on the account we are waiting for CONFIRMED

the discrepancy might cause the diff in data.

[Funkatronics]

when we mint, we wait for the commitment to be Finalized

I don't think this is true, I am looking at the code now and our commitment level is CONFIRMED

when we are polling the NFTs on the account we are waiting for CONFIRMED

this does make sense/is not relevant. the my mints page only reads data, it does not send any transactions.

We can:

• bump up our transaction commitment level to FINALIZED (tho IME this will not 100% solve the problem, only help)
• fetch and return the created NFT in the perform mint use case (much like the metaplex NFT client does), then use this NFT model to update the local nft cache/database optimistically
• We could manually create the NFT object from the input/mint details, then use this NFT model to update the local nft cache/database optimistically

[creativedrewy]

Is this done @ankur2136 @Funkatronics ?