Clarity Working Group — passing the baton from Setzeus

Clarity Working Group — Notes, Oct 27, 2026
Written from the call with Hugo, Rapha and others. Everything below is under active development, and plans may change. Please correct or add in the thread below.

Clarity

Clarity WASM (Hugo, Rapha)
The team is rewriting the Clarity specification as preliminary work for a Clarity-to-WASM compiler. Hugo noted that WASM may speed up some operations, such as raw math, but it may not change much for I/O-heavy contracts. Under the current plan, the compiled binary would become the source of truth, and the team is looking at ways to verify that a given Clarity source produced a given binary, similar to contract verification on Ethereum.

Transparency (Rapha, Hugo)
Rapha asked whether compiled WASM code would stay human-readable and transparent enough for legal and audit purposes. Hugo said the team would like to offer tools, such as a CLI or a website, to check source code against binaries. There was also a brief discussion about attaching metadata to contracts, such as a repository link, a license, the author’s name, or the KYC-style fields some Ethereum contracts use.

Two questions remain open. Should providing source code at deployment be mandatory or optional? And how do we balance legal transparency and metadata with a move to compiled binaries?

Clarinet v4 (Hugo)
Hugo hopes to release Clarinet v4 around late this week or early next week. The aim is to make Simnet behave more like Mainnet by adding gas fees, post-conditions (including deny mode), and nonces. Because of this, some unit tests that rely on Simnet’s current behavior may fail. Clarinet would also reuse more of the Stacks node code, so unit tests and app code stay closer together. The upgrade won’t be mandatory, but Hugo suggested it for new projects.

Stacks.js (Hugo)
Later, Stacks.js may change so builders can use the same syntax to broadcast transactions on Simnet and Mainnet, instead of Clarinet’s own simnet.call syntax. The idea is to simulate full workflows, including fees and post-conditions.

Devnet vs Testnet (Hugo)
Devnet runs locally in Docker and resets when the container is destroyed, which suits quick, private iteration. Testnet is an external network where contracts stay deployed longer before Mainnet.

Off topic

Rapha is testing a pegged limit order book and automated loop market-making strategies written in Clarity. Rapha also wrote a simple Clarity contract that collects donations to help Africa build.

Next session
In two weeks. Everyone is welcome to join and share updates.

Action items
Everyone is invited to try the full app user flow on Clarinet Simnet once v4 iminutes on the Stacks forum and organize the next session.
Rapha is testing a pegged limit order book and automated loop market-making stRapha also wrote a simple Clarity contract that collects donations to help
Africa build.

Next session
In two weeks. Everyone is welcome to join and share updates.

Action items
Everyone is invited to run their test suites on Clarinet Simnet once v4 is out, including full user flows with fees and post-conditions. Rapha will post these minutes on the Stacks forum and organize the next session.