[feature] Add a voting power recharge function to cli_wallet #573

Closed
opened 2023-12-06 22:26:27 +00:00 by christophersanborn · 8 comments
christophersanborn commented 2023-12-06 22:26:27 +00:00 (Migrated from gitlab.com)

Currently, to recharge your GPOS voting weight, you need to broadcast an account_update operation that either (a) changes your voting slate, or (b) keeps the same voting slate but sets the update_last_voting_time extension field. Aside from manually constructing a transaction, there are very few options to achieve (b).

One such option was implemented in MR !217+, which modified the vote_for_son function to set the extension when no changes are actually made to the SON votes. However, similar modifications are not made to the other vote_for_ functions, and usage is not entirely intuitive.

A user of cli_wallet might prefer an explicit voting recharge function that is used solely when the user wishes to recharge their GPOS voting power without changing their voting slate.

A possible name for this wallet function could be vote_recharge_gpos or similar, and the command synopsis could be:

vote_recharge_gpos voting_account broadcast
Currently, to recharge your GPOS voting weight, you need to broadcast an `account_update` operation that either (a) changes your voting slate, or (b) keeps the same voting slate but sets the `update_last_voting_time` extension field. Aside from manually constructing a transaction, there are very few options to achieve (b). One such option was implemented in MR !217+, which modified the `vote_for_son` function to set the extension when no changes are actually made to the SON votes. However, similar modifications are not made to the other `vote_for_` functions, and usage is not entirely intuitive. A user of cli_wallet might prefer an explicit voting recharge function that is used solely when the user wishes to recharge their GPOS voting power without changing their voting slate. A possible name for this wallet function could be `vote_recharge_gpos` or similar, and the command synopsis could be: ```plaintext vote_recharge_gpos voting_account broadcast ```
christophersanborn commented 2023-12-20 13:54:24 +00:00 (Migrated from gitlab.com)

assigned to @bgerze

assigned to @bgerze
bobinson commented 2023-12-20 14:02:19 +00:00 (Migrated from gitlab.com)

unassigned @bgerze

unassigned @bgerze
bobinson commented 2023-12-20 14:15:54 +00:00 (Migrated from gitlab.com)

assigned to @vampik

assigned to @vampik
vampik commented 2023-12-22 05:41:08 +00:00 (Migrated from gitlab.com)

mentioned in commit b0c06beb271491d5bc33deb0908906f167ff008b

mentioned in commit b0c06beb271491d5bc33deb0908906f167ff008b
vampik commented 2023-12-22 05:42:47 +00:00 (Migrated from gitlab.com)

mentioned in merge request !261

mentioned in merge request !261
vampik commented 2024-01-03 07:59:46 +00:00 (Migrated from gitlab.com)

mentioned in commit 8421da3c7bfaeb9937105cda0b03c5e0877bf90c

mentioned in commit 8421da3c7bfaeb9937105cda0b03c5e0877bf90c
vampik commented 2024-01-04 06:07:39 +00:00 (Migrated from gitlab.com)

mentioned in commit 24b0327eb6

mentioned in commit 24b0327eb6c9df545bc478f48f87d8f9fb670526
vampik commented 2024-01-04 06:07:39 +00:00 (Migrated from gitlab.com)

mentioned in commit 52209dbbeb

mentioned in commit 52209dbbebd76745932448c9213464d53df41e26
vampik (Migrated from gitlab.com) closed this issue 2024-01-05 11:32:50 +00:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Peerplays_Blockchain/peerplays_migrated#573
No description provided.