-
Notifications
You must be signed in to change notification settings - Fork 98
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
Show bonding / redelegation transactions #808
Comments
Note that even if the ending transactions are presigned and sent automatically, the user will need to open Voyager again after the three-week period has passed; if the transactions are broadcast before they are valid they'll just fail. |
can we break down the flow for each use case? bonding
unbonding
redelegation
|
I think bonding works immediately. |
Consider #355 |
This second unbonding transaction is extremely user unfriendly. Let's make it easier on the user and have Voyager automatically make the second unbonding transaction once the unbonding period is over. That's much less work for our users. All we have to do is show pending unbonding periods on the user's transaction history. To resolve the part about the user having to re-open voyager after 3 weeks to finish unbonding, let's consider the idea of a Voyager Daemon
It runs at all times on the user's computer. It can be placed in the system tray on Windows, and in the menu bar for macOS. It's main purpose is to offer hub notifications to the user. Events like:
Users can also click on it to launch Voyager instantly. |
I agree; the second transaction UX is terrible. |
I agree with Chris. If this has such a big scope, let's look for another solution first. |
On our radar but not going to happen this week, made an issue in the SDK repo - cosmos/cosmos-sdk#1525. |
Linking #148 |
|
Split 🍌 |
UI Version: 0.6.2
Description:
The bonding / unbdonding and redelegation transactions need to be visualized. Those transactions have a period when they are running but are not in full effect. For unbonding the user needs to send another transaction that finishes the unbonding. The same goes for redelegation. The SDK team agreed, that not sending these transactions will not have a negative effect for the user. But it will not free up funds. And it is desired that redelegations are closed to clean up. So we should incentivize the user to close these redelegations.
Maybe the ending txs could be send automatically by Voyager (optin/optout by the user).
pulling in @jolesbi @nylira
The text was updated successfully, but these errors were encountered: