-
Notifications
You must be signed in to change notification settings - Fork 9
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
No option to delegate to myself as a drep after delegating to Abstain #904
Comments
The missing delegation buttons on the 'self' drep appear probably all the time: https://www.loom.com/share/310530ffd4a040a795520cff3e45563d?sid=32d30642-f48d-48ca-9cd8-c129d18afe46 |
'Yourself' label wrong place mentioned in Loom comment (#904 (comment)) tracked here |
@m-i-k-e is it the concept of 'Delegating to Myself' replaced by being 'Sole Voter'? DW: @MSzalowski |
@pmbinapps @MSzalowski. The concept of sole voter and delegating to oneself are similar, but different. So someone might be a sole voter for a while, and then decide to become a Drep. In current govtool, they would have to become drep first, and then do a second action to delegate to themselves. Yes, this should be improved on the UX design side. But this is our current state. To answer your question "is it the concept of 'Delegating to Myself' replaced by being 'Sole Voter'?" : No. However, if we make some User Experience tweaks, we can either mandatorily or optionally get the user to transfer their Voting Power when they become a Drep. To add to the confusion, if I am a DREP, and then become a Sole Voter, my own voting power is automatically transferred to my Sole Voter account. |
To check showing Voting power value. |
Original Issue - with US with this feature here |
…o-myself-as-a-drep-after-delegating-to-abstain [#904] No option to delegate to myself as a drep
First attempt to see the button on DRep list was fine - Delegate button was shown - but transaction somehow failed with msg not enough founds - this is to be explored. Next, button was not visible any more: To reproduce:
|
@pmbinapps Can you say why this is blocked? |
@m-i-k-e a deployment is not effective, fix is not visible on test, and dev envs, in the moment. |
@pmbinapps I don't understand. If this is closed, then does that mean it won't be fixed? |
@m-i-k-e from event logs looks like it was auto-closed when a PR was made, from my perspective is in QA and is not finished yet. @MSzalowski it could be that an Github action is Closing issues whey they are merged |
Yes, we should have the config that doesn't move issues to done once they are merged. But this is not as important as the integration parts that we have currently in scope |
@pmbinapps should that still be assigned to you? |
Context & versions
staging.sanchonoe
https://www.loom.com/share/2fbab1772d424095b0de8833c029b559?sid=7f22a55c-2a29-441a-977a-a5ddbb7cf313
Steps to reproduce
Actual behavior
There is no delegate button on the 'your' dRep list 'card' or detail page, hence, not possible to self-delegate
Expected behavior
Able to self-delegate
The text was updated successfully, but these errors were encountered: