Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Staking Page | Customing Name of Validator Key needs long to be reflected #2062

Closed
1 task done
daGscheid opened this issue Sep 14, 2024 · 0 comments · Fixed by #2157
Closed
1 task done

[Bug]: Staking Page | Customing Name of Validator Key needs long to be reflected #2062

daGscheid opened this issue Sep 14, 2024 · 0 comments · Fixed by #2157
Assignees
@MaxTheGeeek
Labels
bug Indicates a bug or unexpected behavior in the application.

Comments

@daGscheid
Copy link
Member

Environment

Development

Bug Description

When using a custom name for a validator key, the Staking Page needs a long time to reflect that. We should improve the loading of the page after setting one.

Launcher Version

2.2.2

Operating System

Windows

Affected Service (if applicable)

--

Logs (if applicable)

--

Acknowledgment

  • I have checked the existing bugs and confirmed this issue is not already reported.
@daGscheid daGscheid added the bug Indicates a bug or unexpected behavior in the application. label Sep 14, 2024
@daGscheid daGscheid changed the title [Bug]: Customing Name of Validator Key needs long to be reflected [Bug]: Staking Page | Customing Name of Validator Key needs long to be reflected Dec 17, 2024
@MaxTheGeeek MaxTheGeeek mentioned this issue Dec 19, 2024
Merged
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MaxTheGeeek MaxTheGeeek

Labels
bug Indicates a bug or unexpected behavior in the application.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix Staking Page Issues MaxTheGeeek/ethereum-node
2 participants
@MaxTheGeeek @daGscheid