Creating a Proposal
Structure
Any member of the Star Atlas community may draft a PIP as long as it adheres to the Star Atlas ecosystem’s guiding principles and the requirements outlined below.
A PIP must contain the following information:
Specification
Provide a detailed description of the proposed changes or actions. This should be the most comprehensive section of the Proposal. Include:
Definitions of key terms or concepts
Specific changes or new features being proposed
How these changes will be implemented — keep it functional & non-technical.
Any new processes or systems that will be introduced
Stakeholder Impact
Describe the potential impact this proposal might have on different stakeholders and parties within the Star Atlas ecosystem. Include:
A list of the different stakeholders and how this proposal might affect them.
Stakeholders that are affected positively and those affected negatively!
Implementation Details
Outline the plan for executing this PIP if approved. Provide a summary of the steps needed to implement the proposal in chronological order. Make sure to include:
Information for off-chain actors
Parties responsible for each step
Any technical requirements or changes needed
Potential challenges and how they will be addressed
Hosting solution (if off-chain service)
Timeline
Estimated implementation timeline. Provide a realistic timeframe for implementation. Include:
Expected start date — This could be expressed as a time window after the PIP was approved.
Key milestones or phases (if applicable)
Estimated completion date — This could be expressed as the number of days/weeks/months after implementation kicked off.
Any dependencies on other projects or (proposal) implementations
Cost & Resource Allocation
One-time Costs: Costs of making the initial implementation
Breakdown of all monetary and nonmonetary costs (such as efforts or other resources)
Justification for the proposed expenditure
Source of funding (e.g., DAO treasury)
Consideration of alternative funding sources (if applicable)
Ongoing Costs: Ongoing costs after a potential implementation
Breakdown of all monetary and nonmonetary costs (such as efforts or other resources)
Hosting & maintenance costs (if it's a software solution)
Justification for the proposed expenditure
Source of funding (e.g., DAO treasury)
Consideration of alternative funding sources (if applicable)
Who is going to manage these ongoing efforts?
If any (sub)section is not applicable, please answer it with N/A. This way, no one will have to ask if you considered it or if it should have been a part of your proposal.
Clarifications
Some additional clarifications on the above structure can be found below.
Summary
If a proposal contains parameters (values) that could be changed later through a follow-up PIP, please leave them out of the summary.
Example 1: If you propose to make a one-time donation of ATLAS to a specific charity, please include the exact amount in the summary.
Example 2: If you propose to send some ATLAS to a charity every month, please leave the amount you initially want to set this at out of the summary. That detail should be mentioned in the Specification.
Motivation
Consider the following:
How does it align with the DAO's goals and values?
What benefits will it bring to the Star Atlas ecosystem?
Implementation Details
Outline the plan for executing this proposal if/when approved. Provide a summary of the steps needed to implement the proposal, including information on necessary off-chain actors. Provide the steps needed to implement the proposal in chronological order.
Make sure to include instructions for all involved parties. The instructions should allow each party to implement this proposal without requiring further clarification from you.
Make sure these details are concrete! Nothing here should be vague or open to interpretation.
Conflicts of interest
Start with yourself or any parties/entities/organizations/stakeholders you represent. If one of the parties involved in the implementation stands to benefit when this proposal passes, and you have any kind of relationship (e.g., employee, owner, family member, friend) with that party, this constitutes a clear conflict of interest.
Example: If you want a website built and you found a for-profit company willing to do this, but you are also an employee (or owner even) of that company, then there is a conflict of interest.
Note: Other PVP Stakeholders are not considered as a party with whom there may be a conflict of interest. This section refers to other entities that can be (potentially) identified beyond PVP holders.
Additional Notes
Resubmission
You can resubmit a stranded PIP, and there are no limits to how often you can do this. Of course, if you make no changes, there is no reason to expect a different outcome.
Note that if the Star Atlas Foundation flagged any concerns, they must be solved before the PIP can be brought back up for a vote again.
Additional Requirements
Beyond the structural requirements, a PIP must adhere to the rules laid out in PIP Requirements.
Tips
Keep it Simple
Keep your proposal as simple as possible. Try to propose only one key thing and leave embellishments and/or extensions for a follow-up proposal. This will improve the chances of your PIP passing.
If a PIP can be split into multiple smaller (sub-)proposals, we recommend doing so. If these sub-PIPs could go separately through the legislative process, we strongly suggest going down that route. If there is a need to pass them together, or you just want to do it this way, it is recommended you copy the above structure for each sub-proposal and prepend the PIP titles with A), B), etc. At the very least, make sure you cover all included sub-proposals while writing your draft using the PIP structure above.
Last updated