Proposal Structure

The Swell DAO Framework encourages proposal creators to incorporate the following sections within Swell Improvement Proposals (SWIPs):

Title

  • Precise wording, keep it short.
  • The [SWIP-NO] is added by a Community Moderator.

Abstract

  • A brief, two or three sentence summary of the SWIP.

Purpose

  • A statement explaining why the Swell community should adopt the SWIP.

Justification

  • An explanation of how the SWIP aligns with the mission and core values of the Swell community.

Technical Details

  • A comprehensive breakdown of the platforms and technologies to be used. This section allows you to elaborate on the reasoning behind your design choices. You can also discuss alternative designs that were considered and related work, such as how similar specifications have been successfully (or unsuccessfully) implemented in other chains or languages.

Implementation Steps

  • The steps required to implement the SWIP, including associated costs, manpower, and other resources for each step where applicable. SWIPs that involve transactions with third parties (like grants) must ensure that relevant legal documentation and procedures are also included.

Schedule

  • Relevant timing details, including but not limited to start date, milestones, and completion dates.

Total Cost

  • The complete cost to implement the SWIP. This section should include a breakdown of the total cost of the SWIP, including any associated costs for each step where applicable. Both fixed and recurring costs should be considered.

Sometimes, SWIPs don’t get approved on the first attempt. If a SWIP is not approved, the proposal creator can resubmit the SWIP after addressing the community’s concerns. The following additional sections should be included in the resubmitted SWIP:

Link to the previous SWIP

  • The link to the previous SWIP should be included in the resubmitted SWIP.

Reasons for previous rejection

  • The reasons why the SWIP was not approved should be included in the resubmitted SWIP.

Modifications to the SWIP

  • The changes made to the SWIP to address the concerns raised during the previous SWIP submission should be included.

Additional Information

  • More detailed intentions, specifics and implication details can help the community understand the revised SWIP, increasing the chances of it being approved.
1 Like