Clarity WG: Intro Thread

[setzeus]

👋 Introduction:

Clarity is the native smart contract language used to write & express logic for a chain change in the Stacks ecosystem. Stacks smart contracts are flexible, decidable & powerful, allowing them to write anything from a simple STX transfer to a complicated send-to-many scheme involving NFTs & FTs.

🎯 Objective & Scope:

The key objective of the Clarity Working Group is to provide Clarity support on both specific Stacks projects & ecosystem-wide contracts. Examples of specific projects include milestones such as Nakamoto & sBTC, which both require multiple contracts such as PoX-4, the sBTC asset contract, & so on. Examples of ecosystem-wide/macro contracts include the Clarity-Bitcoin contract.

📦 Deliverables

Boot Contracts
All boot contracts (or protocol contracts) are zero-address contracts loaded by a Stack node. An example of these is the PoX-3.clar contract.

Ecosystem Contracts
In addition to boot contracts, there are a handful of useful, universal contracts used throughout the ecosystem that aren’t strictly boot contracts. An example of these is the PoX-3.clar contract.

Tutorial Contracts
In addition to both writing & maintaining boot & ecosystem contracts, our role

Supporting Documentation
Along with our contracts, our group is also accountable for any documentation that goes along with the mentioned contracts.

📅 Timeline

We have multiple, continuous timelines. Check the sBTC & Nakamoto WG for those specific timelines. Outside of those dates, there is also a loose date of mid-November for Clarity-Bitcoin v5.

👑 Lead

@setzeus (GitHub | Twitter)

🤝 Team

@friedger
@FriendsFerdinand
@Jo-tm
@MarvinJanssen

We’re always looking for more Clarity members that are hungry to contribute to Stacks! Reach out & contact Setzeus to get you looped into our meetings.

🗣️ Meeting schedule and format:

Meetings for the Clarity Working Group are scheduled for twice a week on Tuesdays & Thursdays for the following days:

Tuesday @ 7:30 am EST
Thursday @ 7:30 am EST

✍ Additional Context:

Our watering-hole exists on Discord, if you’re curious about anything Clarity, give us a shout out!

[mhb11]

Hey everyone! I'm excited to share something we’ve cooked up with the Clarity WG.

For those of you I haven’t had a chance to meet yet, I am the lead at BitcoinL2 Labs. For almost a year, we have been a core contributor to the Stacks ecosystem, with our primary focus to date having been Nakamoto. Our commitment to core development will remain a staple of our operations going forward, but as the ecosystem grows, we’re excited to share that we have allocated $1m in funding to the Clarity WG to offer expanded security resources to builders.

Thanks to layers like Stacks, Bitcoin DeFi is growing. This also means the attack surface area is growing along with the things builders need to keep track of to keep themselves and their users safe. We want to support founders who are pioneering this space. After all, security is one of the fundamental value propositions of building on Bitcoin. We’re excited to build upon what others have started in the ecosystem to bring founders even more resources to leverage as they build unique experiences for Bitcoiners.

The initial $1m in funding is intended to allow the Clarity WG to bring new tools and services online that enhance security at the application layer. In addition, we will collaborate to identify and educate vendors, whitehat hackers, and other security-minded talent that builders can work with and benefit from. Led by @setzeus, the Clarity Working Group, along with members of the Stacks DeFi Working Group, have already been moving fast with initial Whitehats put under contract and a Stacks integration with Hypernative in the works.

Aligning security resources:

The Clarity WG will liaise with the community to set resourcing and tooling priorities and to train and vet security experts on Stacks and Clarity. The Clarity WG is an established group in the ecosystem that has been playing a major role in core development. It consists of many of the top Clarity developers in the Stacks ecosystem. Members of the Stacks DeFi Working Group have also been extremely helpful in identifying high-impact places to invest and will remain a key voice in how these funds are deployed.

In addition to the immediate work with Whitehats and Hypernative, the Working Groups have put together an initial 90-day plan that includes:

• Continued development of open-source smart contract testing tools such as a Clarity Fuzzer
• Vetting/testing/due diligence and budget for potential partnerships or integrations that would benefit builders in the ecosystem from a security perspective
• An open set of shared security resources for builders with commonly caught issues so that new founders can leverage the lessons of previous builders more readily.

Why whitehats?

We’ve observed that the whitehat approach is working well on the core development side and want to ensure founders are applying this resource to their Clarity contracts and application designs as well. Secure base layers need to be complemented by secure code and protocols atop those layers!

We believe a multi-faceted approach that is not overly dependent on any one aspect of application security - such as audits, the developers themselves, bug bounty programs, or test coverage - is the best way to reduce risk as this sector continues to grow. We believe supplementing everything founders need to do on their own with an accessible whitehat resource like this is a clear way to bolster the ecosystem.

How it helps founders:

If you’re a builder, this may already be obvious, but it’s worth outlining the ways we hope this effort directly helps the teams bringing us these amazing new experiences:

• Even more eyes on code!
• Benefit of whitehats who have experience in attacking not strictly code vulnerabilities, but spotting holes in the design of the system that can be exploited. With the Clarity smart contract language preventing many typical exploits, these contract/app design issues are what has primarily impacted Stacks teams.
• Added hostile/real-world components to the layers of testing builders can readily access.
• Reduction in cost of bug bounties paid out by founders.
• Reduction in reliance on auditors to catch issues.
• More shared information so hard lessons only need to be learned once!

Next steps and resources:

• Setzeus from the Clarity Working Group is already onboarding Whitehats suggested and vetted by builders, they will go through a real-world training exercise by performing audits on notable apps in the ecosystem that will serve as a baseline for their learning.
• Partnership conversations to integrate security-focused tools and services with Stacks/Clarity are underway.
• Get in touch with Setzeus via the Clarity WG if you’d like to offer feedback, or be involved with these efforts.