Skip to content
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.

[clarity | signer] Voting Mechanics #404

Open
1 task
setzeus opened this issue Nov 10, 2023 · 0 comments
Open
1 task

[clarity | signer] Voting Mechanics #404

setzeus opened this issue Nov 10, 2023 · 0 comments
Assignees
Labels
clarity design Designing or fleshing out the implementation of a feature or task.

Comments

@setzeus
Copy link
Collaborator

setzeus commented Nov 10, 2023

Description

One of the last remaining discussion items revolves around the voting mechanics that are possibly required. As noted previously, this might include, but is not limited to, the following:

  1. Next cycle aggregate public key
  2. Adding / updating protocol contracts
  3. Minimum deposit value
  4. Maximum fee
  5. Threshold %

It's been discussed & confirmed that (1) is an absolute need. Currently, that lives in PoX-4 & will likely remain there.

However, it wasn't made clear how the next four items are voted upon & where that data lives. It was suggested votes could be done with signatures / not in a contract.

Either way, a deciion has to be made here on:

  1. Which data will support vote
  2. Where that data & logic will live

Acceptance Criteria

  • Remaining Vote Mechanisms are closed out
@setzeus setzeus added clarity design Designing or fleshing out the implementation of a feature or task. labels Nov 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
clarity design Designing or fleshing out the implementation of a feature or task.
Projects
None yet
Development

No branches or pull requests

2 participants