radicleart / stxeco-vote

Upgrade for voting
GNU Affero General Public License v3.0
1 stars 0 forks source link

Suggestion - SIP Voting #62

Open radicleart opened 7 months ago

radicleart commented 7 months ago

Lessons from Nakamoto SIP Voting

The following refers to the recent Nakamoto SIP vote on stx.eco in which three voting mechanisms were provided;

Problems

Solo stacker voting

Many solo stackers were unable to send the bitcoin transaction from their reward address, due to address rotation in the wallet. The majority of solo stacker votes, as many as two thirds, had to be excluded from the count.

Pool stacker voting

Pool stackers sent a stacks transaction from the address they had used to join a stacking pool. However, the majority of vote transactions came from addresses which were not stacking, indicating that the web site and instructions had not been clear.

Liquid stacking

Liquid stackers were represented as a block vote.

Improvement proposal

The following changes are proposed to simplify the interface for voting on stacks upgrades.

  1. replace method 1 voting with sending a stacks transaction from the solo stacking stacks address - i.e. no bitcoin transactions.
  2. improve the ui/ux for stacker voting

Under this proposal, methods 1 and 2 from the Nakamoto vote will be combined - solo stackers no longer send bitcoin transactions. Solo stackers with stacks split across several wallets will have the flexibility of voting from any or all of their stacking addresses.

Liquid stackers vote in exactly the same as solo and pool stackers.

The tabulating software performs the task of indexing the pox and stStx contract data to determine the voting power of a given address.

The stx.eco ui/ux is improved to ensure the stackers understand the voting criteria before sending the vote transaction - e.g. the voting QR codes are shown after some user interaction.

Where stackers = same method for solo/pool/liquid stackers.

cuevasm commented 7 months ago

Housekeeping: You reference Methods 1, 2, and 3 here but do not summarize them, will be easier for others to follow this conversation if you specify what those are in this post: 🙏

My thoughts on the proposal: I generally like it, in my mind, it is more a reframing of methods and instructions than a fundamental change to the design/ethos of the voting system.

My suggestions:

To explore: stackers -> vote here (send 0.000001 stx) non stackers -> vote here (send vote tx)

Having different methods these parties have to self-select from actually seems unnecessary to me, so could we further simplify? With the STX address, I believe you could work backwards with API calls to see if they are a non-Stacker or Stacker without them needing to do anything?

Imagine that there is one yes address and one no address and all people had to do was send a dust amount (or auth if they happen to use an Xverse or Hiro wallet) from any address they own, Stacking or not - from there, the rest is tabulated and sorted based on the address history automatically. Elegant ya?

radicleart commented 7 months ago

Housekeeping: You reference Methods 1, 2, and 3 here but do not summarise them

Good point - updated.

API calls to see if they are a non-Stacker

Voting using the DAO contracts, for non stackers, prevents double voting. Open question if this is also possible using balance at height from start of voting ?

many solo Stackers will not have any STX available in their wallet

Is sponsored transactions possible to overcome this - may not help with current desktop wallet but maybe possible via cold storage connected to web wallet ?

radicleart commented 7 months ago

From a 'complete L2' perspective, people should be able to vote using BTC

I agree but this feels dangerous if the reality of this is that 2/3 of voters are excluded based on technical know how - what if they had wanted to vote against but didn't know how ?

Does voting with sBTC transaction mitigate this problem in future?