Governance (SIPs)

SIP stands for Saddle Improvement Proposal.

Proposal Process

SIP stands for Saddle Improvement Proposal. An SIP is a design document providing information to the Saddle community about a proposed change to the system. The author builds consensus within the community and documents dissenting opinions.


The chart below shows a high-level view of the Saddle governance process:

Stage 1: Gauge Interest

If you have an idea for improving the Saddle protocol, the first stage is to test the waters. Go to Saddle on Discord and look for the Governance > #discussion channel. Share your idea and listen to what the community has to say.

If the initial reactions are positive and encouraging, start formalizing your idea into a post for polling on Discourse.

Stage 2: Poll on Discourse

Go to Discourse, look for the Proposals category, and post your proposal there (rec copying the formatting from a prev passing proposal, or using this template).

Here’s are a few handy tools to help draft your post:

  • Tips on posting proposals on Discourse: Link

  • Template for your post: Link

  • Before you click the submit button, check if your post has:

    • Sections: Simple Summary, Abstract, Motivation, Specification

    • Poll: Include a 72h poll (using the most appropriate poll type, typically Y/N or multiple choice)

All set! Last step is to ping a Saddle Core Contributor in Discord to blast your shiny new proposal on all the socials to maximize engagement.

Stage 3: Vote on Snapshot

If the Discourse poll passes after 72 hours, the SIP editor will step in to formalize the SIP. The voting process comprises:

  • Creating a vote on Snapshot (by SIP editor)

  • Creating a specific discussion channel on Discord (by Saddle core contributor or gov mod)

  • Announcing the vote on all socials (by Saddle core contributor)

  • 72-hour voting period for SDL holders

Stage 4: Fork SIP

Once the Snapshot voting is finished and passes successfully, the SIP editor will fork the SIPs repo and create a pull request (PR):

  • The PR will have a copy of your proposal

  • With the metadata filled out, notably discussions-to which will link to the Discourse post

  • The proposal will be named in the format:

  • Read SIP-0 for additional information (e.g., workflow, attaching images/diagrams, SIP editor responsibilities).

Stage 5: Execution

Lastly, a Saddle core contributor or SIP editor will coordinate with the community multisig to execute the proposed change.


The stakeholders for the governance process can be both internal and external. Various governance roles exist to ensure the stakeholders engage in delivering the type of value desired or expected. The key roles and responsibilities of Saddle governance are:

SIP Editor

Broadly, the SIP editor’s powers and responsibilities are:

  • Checks the incoming proposals for quality

  • Validate technical correctness

  • Check language and grammar, and other editorial aspects

  • Work with the SIP authors for revision, where required

  • Create vote on Snapshot

  • Formalize and document passed SIPs on GitHub

The editors don’t pass on judgement on SIPs, rather act as an administrative check-and-balance role.

Who: The current editors are @alphastorm, @penandlim, @hammeiam, and @ug02fast.

Saddle Core Contributors

Core contributor powers and responsibilities:

  • Provide feedback on proposals

  • Advise on how best to create a passing proposal

  • Create channels and shepherd discussions in Discord and Discourse

  • Post announcements of voting start on social channels (Discord, TG, Twitter)

Who: Anyone with a Saddle Team role in Discord

Governance Mod

Gov mod powers and responsibilities:

  • Moderating messages in communities and deleting inappropriate messages

  • Invite, ban, or suspend people who violate the community rules

  • Create channels and shepherd discussions in Discord and Discourse

  • Create vote on Snapshot

Who: No one as of now. Community members interested in contributing as a gov mod should ping zim#2649 on Discord.

Last updated