[4.10.1] Bug: incorrect locked and available balances

[fyang1024]

Bug found testing Hiro Wallet build undefined, 4.10.1.

The locked and available STX balances are incorrect. As shown on the screenshot, the wallet shows 186,193 STX locked and 5,104.728335 STX available, however, the wallet has all the balances locked in the XVerse pool and no STX is available. It used to lock 186,193 STX in solo stacking dozens of cycles ago, and the wallet seems to use the outdated information now.

[friedger]

The screenshot shows that you have delegated 191k to xverse ("You are pooling..").
Note that delegated/pooled amount can be different to the balance.
You can check what happened using https://fast-pool-ui.vercel.app/u/SP1234 (with your address).

You will see that you are currently pooling with a different pool at the moment. That means that the xverse pool manager can take over your stacking for cycle #65 only.

The bug is that the current stacking information on the right are mixed with the actual delegation information for future stacking.

[fyang1024]

Obviously I don't quite understand the concepts of "Locked", "Delegated", "Available" in stacks. I thought STX is either locked in solo mode or in a pool, and the rest is available.

[friedger]

I thought STX is either locked in solo mode or in a pool, and the rest is available.

That is 100% correct. However, the pool operator decides how much to lock and for how long.

How long? With xverse and the other pools it will be 1 cycle and the extended by 1 cycle.

How much? The pool operator can only lock up to the maximum of your stx balance and the delegated amount.

For you, the previous pool operator locked 186k, then you delegated 191k to a new operator. They will be able to lock your 191k if you have it in your account.

Does it make sense?

[fyang1024]

Please let me know if I read the information correctly from the screenshot below
I initially delegated 186194 STX, but the pool operator decided to lock up only 186193 STX for some reason since Cycle 60.
For some reason, even though the pool operator locked 186193 STX in Cycle 60, the stacked amount is 0. The stacked amount became 186193 in Cycle 61 and remain so in the current cycle 62. In current cycle, I delegate 191297 STX. Because only 186193 out of 191297 STX is locked now, about 5000 STX is truly available so that I can move them. From next cycle, the pool operator will decide how much to lock up, but up to the maximum of my STX balance and the delegated amount. Am I right?

[friedger]

Yes, that sounds correct. Cycle 60, 0 STX locked because pool operator only locked during cycle 60. 1 STX left over so that you can make revoke transaction/stop pooling. 11.07.2023 14:00:53 Fei Yang ***@***.***>:

…

Please let me know if I read the information correctly from the screenshot below I initially delegated 186194 STX, but the pool operator decided to lock up only 186193 STX for some reason since Cycle 60. For some reason, even though the pool operator locked 186193 STX in Cycle 60, the stacked amount is 0. The stacked amount became 186193 in Cycle 61 and remain so in the current cycle 62. In current cycle, I delegate 191297 STX. Because only 186193 out of 191297 STX is locked now, about 5000 STX is truly available so that I can move them. From next cycle, the pool operator will decide how much to lock up, but up to the maximum of my STX balance and the delegated amount. Am I right? [https://user-images.githubusercontent.com/20808865/252654387-a926ebda-6d9e-42b9-8eca-9531add6ab81.png][Screenshot 2023-07-11 at 9 49 33 pm][https://user-images.githubusercontent.com/20808865/252654387-a926ebda-6d9e-42b9-8eca-9531add6ab81.png][https://user-images.githubusercontent.com/20808865/252654387-a926ebda-6d9e-42b9-8eca-9531add6ab81.png] — Reply to this email directly, view it on GitHub[#1213 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AALBYWP7NECIKUD23R7RVW3XPU57LANCNFSM6AAAAAA2FRYSUE]. You are receiving this because you commented.[Verfolgungsbild][https://github.com/notifications/beacon/AALBYWIF4MATA6UAMSKL7M3XPU57LA5CNFSM6AAAAAA2FRYSUGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTBGJY24.gif]