Talk:DAO Governance Framework
NOTE
Anyone can contribute. To edit this wiki create an account.
Click 'Add topic' to separate subjects.
Please sign all comments by typing 4 tildes (~).
- To answer, use colons (:) to indent
- Use two colons (::) to indent twice
- Etc.
- Etc.
- Use two colons (::) to indent twice
Craig Calcaterra (talk) 04:26, 27 March 2023 (CDT)
Former Attempts
CRDAO: Bid Escrow Architecture by Odra
Voting Technical Issues
The Validation Pool is the heart of the system, so voting with REP is always a major issue. I have always preferred as ideal the notion that each DAO run its own blockchain to keep track of its own REP list. The major problem with voting is scaling. In order to have regular automated votes there is a lot of messaging that is needed if it is to remain decentralized. There is also a major difficulty in keeping the vote hidden until the period is ended. These issues have been explored in the literature and I'm confident there are solutions. But I'm ignorant about the existence of a robust product we can simply adopt.
https://vitalik.ca/general/2021/05/25/voting2.html
Craig Calcaterra (talk) 00:02, 2 March 2023 (CST)
Idea: Using the forum conception of a node as a sub-forum. I'm using SPD as an example.
Question
Agree/Disagree/Qualify (ADQ):
The WDAG will consist of 2x main REP classes (WREP, CREP) - RREP and GREP can be thought of as different kinds of WREP types. CREP types aren't as important.
FU: Different REP types have their own validation pools.
FU2: Governance REP should be a required WREP type.