-
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
[Feedback] Staking section #781
Comments
thank you so much for your feedback @gamarin2 !! i have reviewed your suggestions and largely agree with your points and perspective. we will be discussing your suggestions on tuesday and i would expect to see many of your points implemented very shortly. |
leaving this here for relevance to staking improvements: #877 (comment)
|
This is a great idea--an app-wide atom balance. Due to its outsize importance, we could have a prominent bar that sits in the bottom of the page, stretching from one side to the other, like an XP bar in MMOs.
This is a good idea, but it should be an optional view. The one table view is still useful because it is easy to sort the entire table by a variety of different attributes (like uptime, slashes, stake %, etc).
The "Unbonded Fermion" bar lets the user visualize how much of their balance is available for delegating. It is useful, but it can be replaced by the app-wide atom balance suggestion.
Good point, we'll have to think of a fix for this.
If there's an interactive slider on the bar, that's a visual bug. This bar can be removed for the app-wide atom balance component. |
To me it sounds more intuitive to have it at the top, but maybe I'm wrong! As long as there is an easy way to see how many Atoms I have and how much are bonded/unbonding/unbonded I'm happy
You could still sort the sub-tables. I don't think it's that important to be able to sort the entire table. It seems natural for the validators I'm already delegating to always be at the top. I also want to see which validators I can delegate to in priority. If I sort by uptime and delegate to the the top 5 and 3 or them are only candidates and not actual validators, that's confusing. The 3 categories I outlines are clearly different and it would be natural to reflect that in the UI imo. |
ActionablesMake Issues for:
Discuss More then make Issues:
|
++
++
Liquid Atoms. This would mean: Blue = Bonded |
So White/Empty are really the most standard form of tokens, you can do whatever you want with them. 🚦With that in mind maybe Red, Yellow, Green would be the most recognizable signals? 🚦 |
Looking AWESOME @jolesbi. I left some feedback. |
What is needed to get this moved from |
Bumps [websocket](https://github.com/theturtle32/WebSocket-Node) from 1.0.30 to 1.0.31. - [Release notes](https://github.com/theturtle32/WebSocket-Node/releases) - [Changelog](https://github.com/theturtle32/WebSocket-Node/blob/master/CHANGELOG.md) - [Commits](theturtle32/WebSocket-Node@v1.0.30...v1.0.31) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
UI Version: 0.6.2
Some feedback on the current UI of the Staking section, as displayed when connected to the mock network.
Edit:
The text was updated successfully, but these errors were encountered: