[ARFC ADDENDUM] Updating rules for ARFC and TEMP CHECK Proposals

Governance
1

Summary

Before a proposal is brought to a vote by a 3rd party, the proposer must indicate they wish to submit that proposal a vote.

Motivation

Recent events have highlighted this gap in the proposal rules. Submitters should have time to revise proposals and should not have their name attached to a proposal they have not chosen to submit.

I am open to consider other proposal related rules that the community thinks should be included.

Details

The proposer must indicate they wish to have a proposal submitted before a 3rd party can submit it for a vote, such as by replying “formally submitting” on the proposal’s forum thread.

Specification

As this proposal pertains to governance guidelines, it does not require any on-chain action or protocol change.

Disclaimer

Codeknight is not presenting this ARFC on behalf of any third party and is not compensated for creating this ARFC.

Next Steps

  1. If consensus is reached on this ARFC, escalate this proposal to the Snapshot stage.

  2. If the Snapshot outcome is YAE, this proposal will be considered canon, and the guidelines will be adopted.

Copyright

Copyright and related rights waived via CC0.

11 Likes
2

Hello, Thanks for submitting this proposal,

It’s a welcome addition to fix the previous loophole exploited recently. I think we should do a larger revisit of the framework, but this quick fix is a good idea, thanks for leveraging the ARFC ADDENDUM tool that was meant for these small scope proposals.

3 Likes
4

Sounds good. I am ready to escalate to snapshot.

5

The current proposal has been escalated, under Skywards, with explicit consent from the author, @Codeknight, to ARFC Addendum Snapshot.

Vote will start tomorrow, we encourage everyone to participate.

3 Likes
6

The current ARFC Addendum Snapshot has just ended, reaching out both YAE and Quorum with 648K votes.

Therefore, [ARFC ADDENDUM] Updating rules for ARFC and TEMP CHECK Proposals has PASSED.

This proposal is Canon now, meaning that from now on, every proposal that needs to be escalated to either TEMP CHECK Snapshot, ARFC Snapshot, ARFC Addendum Snapshot, need explicit consent from the author to be escalated, shared via forum in the same proposal, in those cases where the a third party is the one submitting it for a vote.

5 Likes