TIP-026 Threshold Improvement Proposals (TIPs): Flows and Template

:wave: Intro:

This proposal standardizes the TIP flow and TIP template to provide more structure to the growing Threshold governance process ahead of our first Governor Bravo (GB) vote. The flow is a detailed extension of the one previous validated in the Threshold DAO v2 proposal. No GB parameters have been changed.

Threshold’s governance system is polycentric. With the introduction of GB there are a few categories of likely future Threshold proposals:

  • DAO-wide proposals that require and trigger immediate onchain action
  • DAO-wide proposals that do not require and do not trigger immediate onchain action
  • SubDAO specific proposals. SubDAO refers to individual Threshold Guilds, Threshold Council

This proposal was reviewed by @dougvk, @Nous, @Derek, @jakelynch and Chris before publishing.


:chains:DAO-wide proposals that require and trigger immediate onchain action:

These are votes that directly impact the protocol and require immediate onchain actions such as adjustments to tBTC v2 governable parameters.

This process applies to both the Token Holder DAO and the Staker DAO.

Step One — Forum Post

  • Anyone can post a potential proposal
  • Must have sponsor from an elected DAO representative such as a council member or guild committee member (reduces spam)
  • Post lives on forum for 3 days to be discussed and debated by the DAO. During this time edits and adjustments can be made to the proposal based on feedback.

Step Two - Temperature Check

  • Proposal is moved to snapshot
  • Edits can no longer be made to the proposal
  • Proposal must receive >50% support on the snapshot
  • 25M T quorum on snapshot
  • Temp check snapshot is 3 days

Step Three - Proposal Creation

  • Community member meeting proposal threshold vote weight creates onchain proposal
  • Two day delay before voting begins

Step Four - Vote Period

  • Onchain Proposal voting remains open for 10 days

Step Five - Execution

  • Proposals that pass according to criteria of our validated gb dynamics move onto execution phase (2 day time delay)
  • Proposal that don’t pass are automatically canceled

:no_good_man:DAO-wide proposals that do not require immediate onchain action:

GB is fantastic but it is not the best (or most cost effective) way to query the DAO for decision making in every instance. Proposals that do not require immediate onchain action will still leverage snapshot for more efficient off chain voting.

Step One - Forum Post

  • Anyone can post a potential proposal
  • Must have sponsor from an elected DAO representative such as a council member or guild committee member (reduces spam)
  • Post lives on forum for 3 days to be discussed and debated by the DAO. During this time edits and adjustments can be made to the proposal based on feedback.

Step Two - Vote

  • Proposal is moved to snapshot
  • Edits no longer can be made to proposal
  • 5 day vote window
  • 1.5% quorum

Step Three - Execution

  • Two day time delay after the proposal passes before it is considered fully validated
  • Council can veto the result of the proposal during time delay
  • If it is not vetoed during this period the proposal is considered validated and off chain action can be taken

:tea:Threshold SubDAO Specific Proposals:

Threshold SubDAO votes will continue to be handled on a per group basis. For example, the Threshold Marketing Guild currently has a separate thread on the forum for to be considered proposals and the Threshold Treasury guild can continue to internally vote on ecosystem liquidity incentives.


:key: Threshold Improvement Proposal Template:

This template is the suggested format to follow for TIPs but is not absolutely required in every case.

TIP Number and Title:

Vote Type:

DAO Elected Representative Sponsor:

Overview:

Milestones and Deadlines:

Who is Involved:

Why:

Detailed Summary:

Tx Details (If required):

Additional Info (Optional):

If the TIP involves a major product change or feature addition the following categories should be added:

Scope:

  • Must Have:

  • Nice to Have:

  • Not in Scope:

6 Likes

Thanks @Will, this is highly needed and I appreciate a lot the effort to organize this. I agree with most of it, but I have three specific comments:

  • For the standard process, I think the 100M T quorum requirement on snapshot it’s too high. This is a “temperature check” and it can produce voting fatigue to require an amount that’s very close to the real quorum requirement. Something like 25 M (which is the threshold to be able to post a proposal) seems more aligned with the essence of this step, although we have several snapshot votes in the past that passed with less than 10 M.
  • For the snapshot-only process, the 2.5% quorum rule is more strict than the one for normal proposals, which is odd. I would leave it as 1.5%, which is the current quorum threshold.
  • This proposal can also add a documenting process where each TIP is added to some repo. I’d suggest creating a Github repository where proposals can be added as text files in Markdown format.
3 Likes

Good points @davidnunez! I agree with you and updated the proposal based on this feedback.

2 Likes