Enhancement Request: Improve Feedback for the 'Collect' Button

[sugoibtc]

Issue
User confusion: "Does it require multiple clicks to successfully claim rewards?"

Steps to Reproduce

1. Navigate to the "Pillars/Staking/Sentinel" tab.
2. Click on "Collect."
3. Observe the behavior and see the potential for improvement.

Expected Behavior
I propose adding an animation or indicator to the "Collect" button while the wallet is processing the reward collection. This would give users clear feedback that the action is underway.

Actual Behavior
Currently, after the wallet sends the "account published" message, the "Collect" button resets to its original state. This can make it unclear for users whether the rewards have been successfully collected during that block or if additional action is required.

[0x3639]

This would be a nice improvement.

[maznnwell]

I don't think it's a matter of did the wallet or not process the reward collection. But a matter of whether the network/blockchain processed the collect request and has synced the data. Obviously, it takes more than 1 momentum.

In some case, there is an extra delay that is added inside the wallet, after a block is created. It has 31 seconds. So it looks like it takes some time for data to be synced.

I am currently working on a refactor of the desktop app. But I don't think adding an extra delay, to make the button continue on spinning for another 31 seconds is a good idea.

The user might also have some other transactions to be processed. Before processing the receive collect block. You might see the loading keep on spinning for 5 minutes. And the user will keep staring at the screen.

For a start, I think adding more details to the notification title would be enough. "Collect account published, please be aware that the reward data takes some time to sync."

[coinselor]

For me personally, the dual-transaction model has been confusing coming from most other chains. While users can check the notification or transaction tabs to view account blocks, the pending status of transactions isn't immediately clear.

A simple temporary solution could be to add a small counter next to the plasma icon showing the number of pending transactions.

I would not worry too much about it when the eventual bottle neck will be the user, and not the network 👽. However, the implementation would still be useful for Bitcoin/EVM chains, etc.

[maznnwell]

For me personally, the dual-transaction model has been confusing coming from most other chains. While users can check the notification or transaction tabs to view account blocks, the pending status of transactions isn't immediately clear.

What exactly is unclear about the pending status of a transaction? Why does the blockchain implement pending transactions? Bitcoin implements unavailable balance. Every blockchain has it's quirky part.

A simple temporary solution could be to add a small counter next to the plasma icon showing the number of pending transactions.

Adding this counter next to the plasma icon will be confusing for users that have plasma fused, because they don't have to wait for PoW to receive a transaction.

I would not worry too much about it when the eventual bottle neck will be the user, and not the network 👽. However, the implementation would still be useful for Bitcoin/EVM chains, etc.

What implementation would be useful? Adding that counter? Having worked with all three blockchains, I don't use how that counter next to the plasma icon would be useful for BTC or EVM.

Getting back to the main issue, a robust solution would be to add a periodic request that, after the user clicks collect, checks if the data has synced or not. This check would consistent in verifying if there are still rewards to be collected. If I am not mistaken, when making this check it doesn't matter whether the user actually received the rewards block, just that the network received the collect request.

Another simpler solution, would be to add a refresh button inside the widget, as in Latest transactions, so that the user can refresh the information inside the widget. This is what I will implement with the refactor because it's easy to do and quite useful.