Zero AuthorityZero Authority
Governance Policies

SIP Editors

Who the SIP editors are and what they are responsible for.

considerations/sip-editors.md· fetched 2026-09-21

Consideration for SIP Editors

Members:

Discussions-to: https://github.com/stacksgov/sips

Created-by: SIP-000

Invite tree:

  • HeroGamer recommended
    • AcrossFire
    • j2p2
    • Rafael Cárdenas
    • werner.btc

Biographies

AcrossFire: AcrossFire has experience as a DevOps engineer, Linux enthusiast, and a passionate Bitcoiner. He has experience with systems administration and enjoys automating maintenance tasks using tools like Puppet, Ansible, Docker, Kubernetes and others. He likes to bring this experience to Bitcoin by running Bitcoin and Stacks nodes and doing what he can to optimize the experience.

Jesse Wiley: Jesse Wiley is a seasoned DevOps expert - he makes sure all systems are running smoothly and the right security considerations have been made.

Claire Gadd: Director of communications for the Stacks Foundation.

werner.btc: Since 2021, Werner has been an active Stacks community member and helper. As an artist, tester, and jack of many traits, my contributions are rooted in a passion for supporting the Stacks ecosystem. Werner is dedicated to working towards a more equitable, open internet that is inherently safe through the adoption of Bitcoin technology.

About this SIP Editor Committee

The role of a SIP Editor is to identify SIPs in the Draft status and help transition them to Accepted status. A SIP editor must be able to vet a SIP to ensure that it is well-formed, that it follows the ratification workflow faithfully, and that it does not overlap with any already-Accepted SIPs or SIPs that have since become Recommended or Ratified.

The SIP Editors are responsible for maintaining the "inbound funnel" for SIPs from the greater Stacks community. SIP Editors ensure that all inbound SIPs are well-formed, relevant, and do not duplicate prior work (including rejected SIPs).

SIP Editors should be open and welcoming towards enthusiastic users who want to help improve the greater Stacks ecosystem. As such, SIP Editors should encourage users to submit SIPs if they have good ideas that may be worth implementing.

In addition, SIP Editors should respond to public requests for help from community members who want to submit a SIP. They may point them towards this document, or towards other supplemental documents and tools to help them get started.

Considerations

In-scope

The following items would be considered in-scope for this SIP Editor Committee:

  1. To be updated.

Out-of-scope

The following items would be considered out-of-scope for this SIP Editor Committee:

  1. To be updated.

Questions for SIP Review

Questions to facilitate SIP review:

  1. To be updated.

Note: above considerations subject to changes and iterations from ongoing lessons learned

Bylaws

  1. To be updated.

If becoming a SIP Editor interests you and you wish to join the effort, please reach out to @Hero-Gamer or Steering Committee members @jcnelson and @GinaAbrams

    Shapes