Is your feature request related to a problem? Please describe.
There a one cycle delay (which is about 34min) between the time you sell rolls (and they disappear from your wallet) and the time the coins are credited in your wallet. They do not appear as 'candidate' during this time, for example when using wallet_info. This can create panic and generate unnecessary support messages for the unwary user.
Describe the solution you'd like
In the massa-client (but also in our wallet apps and in other third party related projects), we should display the frozen token in a 'delayed' or 'deferred' category when showing the wallet state with wallet_info.
Describe alternatives you've considered
We could instead perhaps show the frozen coins as 'candidate' in the existing framework, if that semantics is acceptable.
They can't written as candidate as it's a totally other purpose but yes we could add a line for this. For now, it's currently possible to see them when making a get_addresses [your_addr] in the client.
Is your feature request related to a problem? Please describe. There a one cycle delay (which is about 34min) between the time you sell rolls (and they disappear from your wallet) and the time the coins are credited in your wallet. They do not appear as 'candidate' during this time, for example when using
wallet_info
. This can create panic and generate unnecessary support messages for the unwary user.Describe the solution you'd like In the massa-client (but also in our wallet apps and in other third party related projects), we should display the frozen token in a 'delayed' or 'deferred' category when showing the wallet state with
wallet_info
.Describe alternatives you've considered We could instead perhaps show the frozen coins as 'candidate' in the existing framework, if that semantics is acceptable.
Additional context