Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bonding Review UI progress bar issue #1413

Open
2 tasks
newbreedofgeek opened this issue Jun 15, 2024 · 1 comment
Open
2 tasks

Bonding Review UI progress bar issue #1413

newbreedofgeek opened this issue Jun 15, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@newbreedofgeek
Copy link
Member

newbreedofgeek commented Jun 15, 2024

  1. I have 2 Data NFTs on Mainnet, and wanted to review the Liveliness for both
image
  1. 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
image

  1. And then I renewed the 2nd one - which was Trailblazer (, the TX sent '@01' for the renew:
    https://explorer.multiversx.com/transactions/98e55ad62d6487de96356a540e994a64987ae22fa38c0fb7f509196a26105403

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?

  • UI is showing wrong data
  • Smart Contract lookup is showing wrong data @bucurdavid pls confirm
@newbreedofgeek newbreedofgeek added the bug Something isn't working label Jun 15, 2024
@bucurdavid
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants