Open newbreedofgeek opened 5 months ago
On 2: if we look here, https://api.multiversx.com/transactions/c0bb1dd1cd5bbb8e55ace7559b37eaeb2d3efe20993b7ce2d72bb6d85f0be710 the timestamp of transaction is:
"timestamp": 1718441178
and inside the contract storage we have:
"(bond_timestamp.....02(bond_id)": "1718441178",
"626f6e645f74696d657374616d700000000000000002": "666d54da",
and the mapping for bond_id 02 is:
"(bonds_idsid.....02)":"DATANFTFT-e936d4...07",
"626f6e64735f69647369640000000000000002": "00000010444154414e465446542d6539333664340000000000000007",
So the renew was correct for the NFT 07
Same for the other transaction. cc: @newbreedofgeek
I have 2 Data NFTs on Mainnet, and wanted to review the Liveliness for both
I first renewed the BiTz XP liveliness (first one on UI list), the TX sent '@07' for the renew: https://explorer.multiversx.com/transactions/c0bb1dd1cd5bbb8e55ace7559b37eaeb2d3efe20993b7ce2d72bb6d85f0be710
After the TX passed, on the UI, the OTHER Data NFT (Trailblazer) shows a full liveliness bar. This is an issue, as BiTz XP DAta NFT was renewed
After the TX passed, on the UI, the first Data NFT (BiTz) shows a full liveliness bar.
View Recording of issue:
https://drive.google.com/file/d/16iV4J8c_pbT_4WhFQQrVGROEUYbgx53O/view?usp=sharing
What could be wrong?