You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the BSQ balance listed on the Wallet Info screen should be the value of BSQ currently owned (i.e., amount that is "available for spending"), not this amount combined with the merit value of BSQ earned in the past.
If not, it might be nice to add a small note specifying otherwise.
Version
1.5.2
Steps to reproduce
Compare "Available for spending" value in DAO > BSQ Wallet to the BSQ wallet balance listed in Account > Wallet Info.
The value I see on the Wallet Info screen is Available for spending + Merit value, not Available for spending.
The text was updated successfully, but these errors were encountered:
Its not merit value, it is BSQ that has been requested but not issued yet. I agree that it should not be displayed in the wallet info screen since it is not valid BSQ until the vote is approved.
From the failed cycle you'll have BTC that failed to become BSQ. You can recover that from your BSQ wallet, in DAO -> Bsq Wallet -> Send. In the group under "My wallet balance" there should be a field called Available non-BSQ balance (BTC). Scroll to the bottom of that screen and you should see an extra group of fields titled Send BTC funds => fill in your BTC receiving address and the amount.
Description
It seems like the BSQ balance listed on the Wallet Info screen should be the value of BSQ currently owned (i.e., amount that is "available for spending"), not this amount combined with the merit value of BSQ earned in the past.
If not, it might be nice to add a small note specifying otherwise.
Version
1.5.2
Steps to reproduce
Compare "Available for spending" value in
DAO
>BSQ Wallet
to the BSQ wallet balance listed inAccount
>Wallet Info
.The value I see on the Wallet Info screen is Available for spending + Merit value, not Available for spending.
The text was updated successfully, but these errors were encountered: