• SIPs
  • SIP Types
  • SIP Statuses
  • Contributing

SharedStake Improvement Proposals (SIPs) describe standards for the SharedStake Decentralized Autonomous Organization.

SIP Types

• Governance Operations - Proposals for improving the DAO operations, Governance, Partnerships and other social events.
• Core - Proposals that affect the core functionality of SharedStake.
• Contracts - Improvements on SharedStake Contracts including gas efficiency, security, reliability etc. Functional changes and core implementations should take place in Core Proposals.
• Interface - Proposals that improve the User Experience and User Interface. These proposals may include Core proposals with smaller effects. Visual changes on the main website should take place as an issue in the UI repository↗
• Meta - Improvements on SIPs, see SIP-1

SIP Statuses

• Proposed - a SIP that is ready to be reviewed in a governance call.
• Approved - a SIP that has been accepted for implementation by the SharedStake community.
• Implemented - a SIP that has been released to mainnet.
• Rejected - a SIP that has been rejected.
• Withdrawn - a SIP that has been withdrawn by the Author(s).
• Deferred - a SIP that is pending another SIP/additional change that should be bundled with it.
• Moribund - a SIP that was implemented and is now obsolete. It requires no explicit replacement.

Contributing

1. Review SIP-1.
2. Fork the repository by clicking “Fork” in the top right.
3. Add your SIP to your fork of the repository. There is a template SIP here.
4. Submit a Pull Request

Before you begin writing a formal SIP, you should vet your idea with the SharedStake community. Ask if an idea is original to avoid wasting time on something that will be be rejected based on prior research. When you believe your SIP is mature and ready to progress, ask to have your issue added to the next governance call where it can be discussed for inclusion in a future platform upgrade. If the community agrees to include it, the SIP editors will update the state of your SIP to ‘Approved’.

If your SIP requires images, the image files should be included in a subdirectory of the assets folder for that SIP, using the following naming convention: assets/sip-X (for sip X). When linking to an image in the SIP, use relative links such as ../assets/sip-X/image.png.

Copyright

Copyright and related rights waived via CC0.