Thanks for the recap @HeroGamer — super valuable for those of us who couldn’t make the call.
Really excited about the new post-condition mode for epoch 3.4. Currently you have to write an exhaustive list of PCs describing every asset movement when all you really want is to protect the user’s account. This new approach is a huge quality-of-life improvement for builders. Kudos to Brice and the team.
Also stoked about the Clarity 5 bugfix bundle — especially the secp256r1 fix. We’re building Pillar, a smart wallet that uses WebAuthn/passkey signatures for transaction signing directly on-chain — no seed phrases, no custodians. The double hashing fix in secp256r1_verify unblocks native passkey verification in Clarity contracts.
Why this matters: solutions like Privy give you passkey login, but your keys still live on their infrastructure — it’s a custodial layer with a monthly bill. With clarity-webauthn, the passkey’s public key lives in the smart wallet contract itself. Any app can verify against it by calling the contract. No intermediary, no dependency on a third-party service staying online or keeping your keys safe.
Even better — because the credential store is on-chain, we can enable cross-app passkey sharing where one passkey works across multiple Stacks apps (Pillar, Zest, Bitflow, etc.) without any single company controlling the auth layer. The browser-level plumbing for this already exists via Related Origin Requests. The missing piece was a trustless shared credential store — and that’s exactly what a Clarity contract is.
Clarity 5 + epoch 3.4 is shaping up to be a big unlock for the builder experience on Stacks.