-
Notifications
You must be signed in to change notification settings - Fork 56
Validator nodes screen is confusing #646
Comments
The new design of the map turned the old map implementation useless, and given that it is a separate effort, I decided to go without it first. All the rest items are valid concerns and we will address them asap |
Partially address #646. # Test Plan * [x] existing tests pass without changes * [x] the page displays all the current validators on mainnet (59) on a single page * [x] the regular updates do not crash CPU (without the change in the Context, it did x4 more re-renders since each individual state dispatch triggered re-render)
Re No.4: Let's sunset the proposals tab and merge the current validators set, the next validators set, and the proposal into a single list using the label ("Active", "Kicked Out", "Next Epoch", "Proposal") to distinguish them. Notes:
|
@ilblackdragon Re No.6: Having a list of |
The information about the pools is present in smart contract name.near.
This info is what https://near.zavodil.ru/?pools= presents.
…On Tue, Jun 8, 2021 at 5:10 AM Vlad Frolov ***@***.***> wrote:
@ilblackdragon <https://github.com/ilblackdragon> Re No.6: Having a list
of *.poolv1.near accounts on the page would not help me to make any
decision on whether I want or don't want to delegate to them. Pools
advertisements should probably happen somewhere outside of Explorer, WDYT?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#646 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABK27U3ZDNIYT3YB4CEX53TRYCFBANCNFSM45WMRH4Q>
.
--
Best regards,
Illia Polosukhin
|
Partially resolves #646 (points 1 and 2)
It was only addressed partially, so I reopen it now. |
To increase connectivity of the repository, current validators refactoring: #955 |
Details
Steps to reproduce
The text was updated successfully, but these errors were encountered: