As previously mentioned, the SIP process exists to manage changes to the Stacks blockchain. SIPs themselves are design documents that outline key features, procedures, or standards for the blockchain, while the SIP process is what community members go through to propose, get feedback on, and review their ideas for blockchain improvement. The SIP council is comprised of 6 editors who help community members develop and draft SIP ideas, 18 Consideration Advisory Board or CAB members who review and recommend/reject SIPs for ratification, and 3 steering committee members who have the power to ratify or veto SIPs. Outside of these officially recognized roles, there is also a broader community of SIP contributors who participate in the process via the weekly SIP call and SIP discussions on Github, the Stacks Forum, and Discord.
The SIP process takes place almost entirely off-chain. The only time a SIP might result in on-chain activity is if it requires a consensus-breaking change, i.e. a hard fork. Because hard forks affect the entire network, it is often recommended that the Stacks community vote to implement them. To date, we have held two community-wide votes, with the last vote resulting in the implementation of the Stacks 2.1 upgrade. We anticipate another vote in Q4 to implement the upcoming Nakamoto Release.Blockchain Governance Highlights
The SIP process has grown and matured immensely, due in large part to the work of Community Governance Resident, Hero Gamer. In the last 12 months, we’ve been able to...
- Fill the majority of SIP roles. Two steering committee members and all CAB members and SIP editors were recruited and onboarded in the last year.
- Ratify 9 SIPs, including SIP-015 & SIP-020 which outlined the Stacks 2.1 upgrade, SIP-018: Signed Structured Data, SIP-019: Notifications for Token Metadata Updates, and more.
- Increase voter turnout from 28 to nearly 500 community members between the last two votes.
- Host over 55 community SIP calls, fostering collaboration between core developers and the broader community on a regular basis.