Clarity Working Group (Clarity WG) – Meeting Recap – Tue, 11 Nov 2025

Working Groups
1

Clarity Working Group (Clarity WG) – Meeting Recap

Date: November 11, 2025, at 9.00am ET
Hosted by: Setzeus
Duration: ~60 mins
Participants: Setzeus, Gary, BowtiedRadone, Dylan @ Bitflow, Raghav, Victor, HeroGamer

1. Agenda Overview

  • Clarity V4 Activation & Feature Overview

  • Contract Security Enhancements

  • Rendezvous Testing Framework Deep Dive

  • Project Updates & Developer Support

2. Key Meeting Highlights

Clarity V4 Release Overview - by @setzeus

  • Activated today with focus on security improvements and developer experience.

  • Major new features:

    • Allowances system – contract post conditions with 5 supported types (STX, FT, NFT, stacking, any asset).

    • Contract hash function – verifies contract deployment integrity.

    • ASCII helper function – converts values to ASCII strings for debugging/logging.

  • BowtiedRadone confirmed availability to assist with implementation questions.

Contract Security Enhancements

  • as-contract function overhauled: now requires explicit restriction statements for asset safety.

  • Must pair with ((with-stx|with-ft|with-nft|with-sfacking)*|with-al1-assets-unsafe)

  • This is noted by Setzeus as probably the most valuable security feature in the this V4 release, enabling safe context switching.

  • Contract hash limitations: small formatting changes (comments, whitespace) alter hashes – documentation to emphasize this caveat.

  • Introduced new current-contract keyword for cleaner syntax and secp256r1-verify function (docs pending).

Rendezvous Testing Deep Dive - Education by @garyriger

  • Custom fuzzer for Clarinet contracts introduced.

  • Two core methods:

    • Property testing – tests that functions behave correctly under varied random inputs.

    • Invariant testing – ensures overall system consistency after any series of operations.

  • Property tests accumulate state between runs, unlike unit tests.

  • Documentation: https://stacks-network.github.io/rendezvous

  • BowtiedRadone open for repo reviews & feedback on X/Discord.

  • Some DeGrants projects may now require Rendezvous-based testing in addition to Clarinet tests.

Project Updates & Support

  • Raghav aka. Rv404 on X (Finding Nakamoto project): Raised NFT trait security concerns – traits define interfaces only, not logic; not suitable for security enforcement.

  • Victor on X (CineX project): Requested visual learning materials for Clarity; onboarding curve noted as steep.

    • BowtiedRadone planning demo videos and v1 roadmap.

    • Recommended starting with “always true” test patterns to build testing intuition.

  • HeroGamer: Introduced himself to be joining future calls to support WG calls documentation, accessibility, visibility, and alignment with Foundation governance’s goal.

Things to Celebrate

  • Successful Clarity V4 activation – milestone for smart contract security and tooling.

  • Growing developer participation (project leads, auditors, educators).

  • Ongoing collaboration between ecosystem projects and Clarity core contributors.

:speech_balloon: Key Speakers Insights

  • Setzeus: Emphasized the milestone nature of V4 and encouraged community testing and documentation improvements.

  • Gary: Emphasized using Rendezvous and Clarinet tests together: use Rendezvous for property-based and invariant testing in Clarity, and use TypeScript/Clarinet SDK for external interactions, events, and complex scenarios.

  • BowtiedRadone: Highlighted Rendezvous as a major step forward for automated testing; offered mentorship for developers.

  • Raghav: Brought clarity on trait usage in security patterns – education needed to prevent misuse.

  • Victor: Stressed importance of educational content and approachable materials for onboarding new Clarity devs.

  • HeroGamer: Will assist with increasing visibility and alignment of Working Groups with governance and communication best practices.

Action Items / Next Steps / Decisions

Topic Responsible Next Step Timeline
Clarity V4 Documentation Setzeus + BowtiedRadone Update docs to clarify contract hash behavior and as-contract restrictions
Rendezvous Testing Guide BowtiedRadone Publish beginner demo videos and roadmap
WG Visibility & Docs HeroGamer Support documentation process and connect with Foundation governance Ongoing

:link: Resources & References

:open_book: Call-To-Action

  • Update comments for Contract hash limitations aka. small formatting changes alter hashes
  • Schedule a workshop on fuzz testing with Rendezvous to help developers adopt property and invariant testing practices.
  • Expanding Clarity Working Group (WG) participation — Developers, auditors, educators, and grant project teams are all invited to join the Clarity Working Group! Connect with Gary on X to get access to the group chat and the bi-weekly Google Meet link - we are here to support your Clarity programing journey!
2 Likes
2

This is awesome, I missed the meeting. I’m a Clarity dev working on a decentralized Fashion social platform for fashion creators built on stacks to enable them to share their work and earn in BTC

2 Likes
3

Sounds fascinating. Happy to invite you to our dm group. Find me @garyriger on X.