Zero AuthorityZero Authority
Governance Policies

Consideration for Technical SIPs

Scope and membership of the Technical advisory board.

considerations/technical.md· fetched 2026-09-21

Consideration for Technical SIPs

Chairperson: Jesse Wiley

Members:

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

Created-by: SIP-000

Biographies

Aaron Blankstein: Aaron is a staff engineer at Stacks Labs, contributing to the Stacks blockchain and Clarity. He has been working on the Stacks blockchain for 7+ years, working on Proof-of-Transfer consensus, Clarity, and other projects.

Brice Dobry: Brice is a staff engineer at Stacks Labs, working on Clarinet and other developer tools, and contributing to the Stacks blockchain. Coming from a background in compilers, programming languages, and analysis tools, he is passionate about helping developers build productively, efficiently and safely.

j2p2: Computer Engineer and Clarity Developer. Won First and Second place in Clarity Course Cohort #2 Hackathon. Contributed to Stacks as a SIP editor; co-founded leos.guru, an educational platform, and chat.stacksgpt.xyz, a Q&A bot for Stacks & Bitcoin.

Friedger: Friedger is an entredeveloper based in Europe. He contributed to the Stacks ecosystem in various forms.

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.

Radu: Radu is a testing expert with several years of experience in fuzz testing. He is co-creator of Rendezvous, the first fuzzer for Clarity smart contracts, and a core contributor to the Stacks blockchain. He has been building on Stacks for 4+ years and has contributed to multiple decentralized protocols, including PoX-related, DeFi, and GameFi projects.

Setzeus: Setzeus is the founder of StrataLabs, a Bitcoin studio that consults L1 & L2s (such as Stacks) / launched a Bitcoin development environment (BitScript). Through his work at TrustMachines he's been hacking away on sBTC & is eager to continue contributing to the Stacks community in anyway.

Vlad: CTO and co-founder of multiple Stacks and Bitcoin based projects, including Asigna, STX20, and sOrdinals. Contributor to the multisig SIP and its implementation, as well as to the Stacks ecosystem opensource projects.

About this CAB

The technical CAB reviews SIPs related to technical implementations to the blockchain, including consensus-breaking changes. SIPs that are technical in nature and must be vetted by users with the relevant technical expertise belong in this SIP track.

Considerations

In-scope

The following items would be considered in-scope for this CAB:

  1. Changes to Clarity syntax and semantics
  2. Changes to Clarity functions or keywords
  3. Changes to the Stacks blockchain’s consensus mechanisms
  4. Changes to the Stacks blockchain’s wire formats
  5. Changes to the networking protocols in the Stacks blockchain
  6. Proposed standards for Clarity contracts

Out-of-scope

The following items would be considered out-of-scope for this CAB:

  1. Changes to the consensus protocol that are strictly limited to financial or economic considerations

Questions for SIP Review

  1. Are there any consensus consequences for the proposal? If so, what are they?
  2. What components of the network are impacted?
  3. What are the activation requirements? Can non-technical users participate in activation?

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

Process

The Technical CAB can ask the SIP author(s) to present their proposal. The recommendation of the CAB is made by simple majority vote by CAB members. A minimum of 50% of CAB members must participate in the vote for a recommendation to be made to the Steering Committee.

Results of votes and associated minutes (if any) are recorded under considerations/minutes.

The minutes include any discussion topics that came up about the SIP. Also, whenever there are opposing votes, those members have the opportunity to write a dissenting opinion which will be included in the minutes.

Bylaws

We choose to adopt the bylaws Steering Committee member @jcnelson set out in this doc: https://gist.github.com/jcnelson/3fcc635ede20ce98d1eae60941eb127a

Starting from those bylaws, this CAB will continue to evaluate what works, what doesn't work, and use the feedback and lessons learned to improve the process and increase involvement along the way.

If this CAB interests you and you wish to join the effort, please reach out to @Hero-Gamer or Steering Committee members @jcnelson and @GinaAbrams

    Shapes