POLICY 004: WeavrDAO Proposal System

The purpose of this post is to inform the community about the status quo on WeavrDAO proposal system and potentially open up a discussion or continue the conversation on this topic.

Mandate:
Define the voting system for different types of policy proposals.

Proposal System
There are three types of Proposals which are relevant to Weavr Protocol:

  1. Common Proposals: These proposals are common to both Weavr and Threads.
  2. Weavr Proposals: These proposals are only relevant to Weavr and only verified WEAV token holders can vote for such proposals.
  3. Thread Proposals: These proposals are only relevant to the Threads and only verified Thread token holders can vote for such proposals.

The quorum for each proposal vote is 10%.

Common Proposal

  1. Paper Proposal

This is a proposal to issue a statement agreed upon by a DAO or Thread about a decision. The creator decides if it requires a super majority to pass. This lets a DAO or Thread limit paper proposals to only be binding if a super majority approves of it, with standing policies allowing ignoring proposals improperly issued without requiring a super majority.

Voting Requirement

supermajority

  1. Upgrade Proposal

Upgrade proposal let’s a contract upgrade itself or a contract it owns, and can specify data to call upgrade with. This data is validated on chain before the proposal is executed, ensuring we don’t upgrade with invalid data. The Frabric also has the ability to upgrade release channels which are pieces of codes that threads default to.

Voting Requirement

supermajority

  1. Token Action Proposal

It can mint, transfer, sell, cancel a sell order, put token up for auction , or do multiple of the previous actions dependent on what flags are set, in relation to what other flags.

Voting Requirement

supermajority - if mint is true

simplemajority for other flags

  1. Participant Removal Proposal

This proposal specifies a participant to be removed, along with a percentage fee to charge them intended to recover any financial damages. If the proposer, combined with the parties who voted by signature, have more than 10% of the supply, the amount of votes required for the proposal to have sufficient participation and pass, the assets of the participant are frozen for the length of this proposal.

Voting Requirement

simplemajority

Weavr Proposal

  1. Participant Proposal

Used to propose participants. It is specific for governors and the rest and not the standard vouch process

Voting Requirement

simple majority

  1. Remove Bond Proposal

Proposes removing a governor’s bond from the Bond contract, either to return their bond if it’s not in active use or to slash it if the governor misbehaved. Slashing bond sends it to the Frabric to decide what to do with it.

Voting Requirement

simplemajority

  1. Thread Proposal

Proposes a new Thread, of the specified variant, of which there is currently just variant 0: a Crowdfunded Thread. Has the given name, symbol, and descriptor applied, with data to be passed to the ThreadDeployer for its deployment.

Voting Requirement

simplemajority

  1. Thread Proposal Proposal

This is a proposal to propose proposals on the Thread. It has the given thread address, proposal type, data and info.

Voting Requirement

simplemajority

Thread Proposal

  1. Descriptor Change Proposal

This proposal is created to change the descriptor of a thread.

Voting Requirement

simplemajority

  1. Frabric Change Proposal

This proposal is to migrate from on Frabric smart contract to the other.

Voting Requirement

supermajority

  1. Governor Change Proposal

This proposal is created to change the thread governor.

Voting Requirement

supermajority

  1. Ecosystem Leave with Upgrades Proposal

This is carried out by the thread to leave the Frabric ecosystem. When it is executed, it enables the thread to set a stand alone ecosystem and change their governor, while enabling upgrades.

Voting Requirement

supermajority

  1. Dissolution Proposal

This is called when a thread investor wants to buy out the property and dissolve the thread.

Voting Requirement

supermajority

1 Like

Thanks for this.

I want to federate this into the governance charter, but I want to add that I wanted to combine the governance framework as you’ve described with the proposal flow in a 2-stage process as described in the process here and here.

Would like your thoughts on whether your proposal type consider emergency proposals as a separate category altogether or an actual flow which could work in all categories.

1 Like