Soft Enhancement Proposals

Soft Enahancement Proposals (SEPs) describe standards for the Soft platform, including core protocol specifications, client APIs, and contract standards.

Contributing

  1. Review SEP-1.
  2. Fork the repository by visiting the SEPs repo and pressing "Fork" in the top right.
  3. Add your SEP to your fork of the repository. There is a template SEP here.
  4. Submit a Pull Request to Soft's SEPs repository.

Your first PR should be a first draft of the final SEP. It must meet the formatting criteria enforced by the build (largely, correct metadata in the header). An editor will manually review the first PR for a new SEP and assign it a number before merging it. Make sure you include a discussions-to header with the URL to a discussion forum or open GitHub issue where people can discuss the SEP as a whole.

If your SEP requires images, the image files should be included in a subdirectory of the `assets` folder for that SEP as follow: seps/assets/sep-X (for sep X). When linking to an image in the SEP, use relative links such as ../assets/sep-X/image.png.

When you believe your SEP is mature and ready to progress past the Draft phase, you should reach out to a Soft Council member on discord by searching members with the "Soft Council" role or finding them within the #governance channel. The Soft Council will schedule in a call with the SEP author to go through the SEP in more detail.

Once assessed, a SEP is moved into Feasibility and a Core Contributor is assigned. The Core Contributor will work with the author to conduct a feasibility study. Once the Author and the Core Contributor are satisfied, a SEP is moved to SC Review Pending. Once the Soft Council has formally reviewed the SEP during the SEP presentation they can either move it to a vote or send it back to Feasability. A vote is conducted within the INSERT ENS NAME snapshot space connected on the staking dApp. If a vote by the Soft Council reaches a super majority, the SEP is moved to Approved, otherwise it is Rejected.

Once the SEP has been implemented by either the protocol DAO or the SEP author and relevant parties, the SEP is assigned the Implemented status. Community members who successfully reach this stage are entitled to a reward from the Soft Protocol.

SEP status terms

  • Draft - The initial state of a new SEP before the Soft Council and core contributors have assessed it.
  • Feasibility - a SEP that is being assessed for feasability with an assigned Core Contributor
  • SC Review Pending - a SEP that is awaiting a Soft Council Review after the Author and Core Contributor are satisfied with feasibility
  • Vote Pending - a SEP that is awaiting a vote.
  • Approved - a SEP that has successfully reached a super majority Soft Council vote in favour.
  • Rejected - a SEP that has failed to reach a supermajority Soft Council vote in favour.
  • Implemented - a SEP that has been released to main-net.

SEPs

  • SEPs

Soft Enhancement Proposals (SEPs) describe standards for the Soft platform, including core protocol specifications, client APIs, and contract standards.