You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Increasing self stake for validators is not fixed completely. Using 3.0.0-rc.1 on Windows 11.
300,000 are already on stake, 19k+ are available. If I set stake to 310k, it shows the error.
Replicate the issue: Go to "Validators -> My validator profile -> Edit stake" and try to increase self-stake
Solution (you can thank przemer): Fix the issue for the page located at "Validators -> My validator profile -> Edit stake"
It only works if you search for a validator and go from the validators list to the validators profile but not if you go from "Validators -> My validator profile -> Edit stake".
Question: Why do you have two different sites for the validator profiles depending on how I access it? You should only have one site, no matter how I land there. It just doubles your work, or?
This example shows how it currently doesn't work and how it works:
The text was updated successfully, but these errors were encountered:
Increasing self stake for validators is not fixed completely. Using 3.0.0-rc.1 on Windows 11.
300,000 are already on stake, 19k+ are available. If I set stake to 310k, it shows the error.
Replicate the issue: Go to "Validators -> My validator profile -> Edit stake" and try to increase self-stake
Solution (you can thank przemer): Fix the issue for the page located at "Validators -> My validator profile -> Edit stake"
It only works if you search for a validator and go from the validators list to the validators profile but not if you go from "Validators -> My validator profile -> Edit stake".
Question: Why do you have two different sites for the validator profiles depending on how I access it? You should only have one site, no matter how I land there. It just doubles your work, or?
This example shows how it currently doesn't work and how it works:
The text was updated successfully, but these errors were encountered: