We’re having fun, creating value, and moving fast. The discussions on the forums have been fruitful and we want to move forward as a community, but how do we know when we’ve collected enough opinions to confidently advance toward implementation?
All DAOs, communities, and teams have standards and guidelines.
I propose that we implement a standard Loot Improvement Proposal framework that will help guide our discussions and snapshot votes moving forward.
Phase 1: Community Feedback
- Introduce a proposal on the Loot Talk forums using the template provided below.
- Include a poll to capture initial community sentiment.
- Proposal author should remain ready to engage with the community e.g. by answering their replies, addressing concerns, and adjusting the proposal as necessary.
- The proposal will remain in the Community Feedback phase until the following criteria have been met:
** at least 3 days of discussion have taken place
** the proposal has received at least five comments from different community members
** at least 25% of poll votes are “For”
- After achieving sufficient engagement (defined above), the proposal author may request that the forum moderators assign the proposal an official LIP number (e.g., LIP-1234), after which the proposal may move to the Snapshot Voting phase.
Phase 2: Snapshot Voting
- Proposal author (or member of moderation team) should create the Snapshot proposal and include the LIP number in the title.
- Snapshot proposal should include the author’s username and the finalized version of the proposal details.
- Snapshot vote should be open for a minimum of 3 days to provide sufficient time for establishing quorum.
- In order for a vote to pass it needs to have a majority approval (>50%) and include a quorum of least 10% of eligible voters.
A simple description of the proposal’s end result and desired change; this should be non-technical and accessible to a casual community member. Summary should be no more than a few succinct sentences.
A short (~200 word) description of the proposed change, the abstract should clearly describe what will be done if the LIP is implemented.
This is the problem statement. Explain why this proposal is necessary or useful for the protocol. The author is encouraged to add visual elements such as charts to support their arguments.
Lay out your proposal - explain how the LIP is going to tackle the issue at hand. The overview should clearly describe how the new feature(s) will be implemented (including technical implementation details, if relevant).
For: I support this proposal.
Against: I am against this proposal.