Activation of Technical Consideration Advisory Board (CAB)

brice · September 22, 2022, 9:23pm

Dear all Stacks community,

We would like to formally announce the activation of
Technical Consideration Advisory Board (CAB)

This advisory board will support the robustness of Stacks Improvement Proposal (SIP) process by reviewing all relevant SIPs coming through.
The activation of this CAB will pave the way for greater involvement of the Stacks community’s voices and expertise, increasing the decentralization of decision-making of Stacks blockchain. You can read more about the SIP process in SIP-000: sips/sip-000-stacks-improvement-proposal-process.md at main · stacksgov/sips · GitHub
All details about this CAB will be logged officially on Github under stacksgov / sips
Link: sips/considerations at main · stacksgov/sips · GitHub

----------------—--------------------------—-----------------------
Chairperson: Brice Dobry

Discussions-to: GitHub - stacksgov/sips: Community-submitted Stacks Improvement Proposals (SIPs)
Created-by: SIP-000

Members Bio
----------------—--------------------------—-----------------------

Aaron Blankstein
Aaron is a staff engineer at Hiro, contributing to the Stacks blockchain, Clarity, and Hiro’s subnets implementation. He has been working on the Stacks blockchain for 5+ years, working on Proof-of-Transfer consensus, Clarity, and other projects.

Brice Dobry (Chairperson)
Brice is a senior engineer at Hiro, 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.

Dan Trevino
Dan is the founder of Boom Cypto and an advocate for open standards. Dan has contributed to the Stacks community as an advocate, developer, speaker, and mentor since 2016.

Daniel Fritsche
Daniel is the co-founder of Byzantion, a cross-chain infrastructure and trading platform creating seamless cross-chain experiences for developers and users. Prior to Byzantion, he was the Vice President of Data Strategy at Stephens Inc.

Jamil Dhanani
Jamil is the Founder and CEO of Gamma.io, the leading marketplace and creator platform for NFTs on Bitcoin, built on Stacks. Prior to founding Gamma, he worked as a Machine Learning Engineer and Researcher at Apple, and studied Computer Science at Stanford and the University of Toronto.

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.

Mike Cohen
Advocate of Bitcoin, Stacks, Lightning Blockchain web3 technologies and the User Owned Internet.
Working in The Clarity Innovation Lab - a research and development centre focused on the Clarity Smart Contract programming language - pushing the boundaries of decentralised apps on Bitcoin.

Terje Norderhaug
Independent software developer. Clarity developer.

Thomas Osmonson a.k.a aulneau
Thomas is co-founder and CEO of Fungible Systems, a web3 and crypto focused product studio. Fungible Systems works extensively in the Stacks ecosystem building public goods, open source tooling, and helping projects such as Gamma, Zest, Trust Machines, and others. Previously, Thomas was part of the early core team that helped build the Stacks network.

About
----------------—--------------------------—-----------------------
The SIP is technical in nature, and must be vetted by users with the relevant technical expertise.

Considerations
----------------—--------------------------—-----------------------

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

Changes to Clarity syntax and semantics
Changes to Clarity functions or keywords
Changes to the Stacks blockchain’s consensus mechanisms
Changes to the Stacks blockchain’s wire formats
Changes to the networking protocols in the Stacks blockchain
Proposed standards for Clarity contracts

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

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

Questions to facilitate SIP review:

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

*Above considerations subject to changes and iterations from ongoing lessons learned

Bylaws
----------------—--------------------------—-----------------------
We choose to adopt the bylaws Steering Committee member @jude set out in this doc: CAB Bylaws · GitHub
----------------—--------------------------—-----------------------
This is just the beginning. As we implement this CAB into the SIP process we will find out first hand what works what doesn’t work, and will use the feedback and lesson learned to improve the process and involvement along the way.

We look forward to give back to the Stacks community. Thanks for reading!
Bitcoin

If this CAB interests you and you wish to join the effort, please reach out to @jennymith and @HeroGamer or Steering Committee members @jude and @Gina

Activation of **Technical Consideration Advisory Board (CAB)**

Activation of Technical Consideration Advisory Board (CAB)