Stacks Developers

The @Stacks Hackathon: $20,000 Prize Pool Submission open March 2. Register now to take part! Bounties include best use of USDCx, most innovative sBTC use, and AI for Bitcoin x402 integrations. See replies to register below 👇

5/Codelens config enhancements give you more flexibility in your LSP setup. Separately, cost analysis now checks client capabilities first, so editors that don't support it won't throw errors. Read more about the full release below github.com/stx-labs/clari…

4/ #[env(simnet)] This release fixes edge cases where annotations at end of line were being ignored, and now simnet-annotated code gets dimmed in VS Code with DiagnosticTag::Unnecessary. So, your test-only code is visually distinct from production logic right in the editor.

Release incoming: Clarinet v3.15.1 just dropped! Linter expansion, stronger encrypted mnemonic options, simnet annotation polish, and LSP upgrades. Here's what's new for builders. 1/5

Stacks devs: give your AI agent the full context 🧠⚡ llms-full.txt = our entire docs in one clean, LLM-ready file. No HTML parsing. No guesswork. Just straight markdown knowledge. Plug it into your workflows & let your tools actually understand Stacks.

Hit that "Join Group" button: skool.com/stackers/about

Want to join a private community for developers building on Bitcoin with Stacks? You get direct support, a step-by-step guide to building on Stacks, and a community doing the same thing you are. Apply for joining the group below. ⬇️

Register for the call here: addevent.com/event/h0tncsjx…

The next Stacks blockchain call is taking place on Tuesday, 24 March, at 10AM ET. As a Stacks builder, it's the moment for you to get feedback, discuss core network topics, and talk directly to Stacks Labs core engineers. Make sure to add it to your calendar. ⬇️

This is one of the biggest security upgrades to Clarity yet. each entity protects its own assets — users via post conditions, contracts via restrict-assets? and as-contract?. Full docs here: #restrict-assets" target="_blank" rel="nofollow noopener">docs.stacks.co/reference/clar…

The new `as-contract?` in Clarity 4 builds this in by default. Every as-contract? call now implicitly wraps with deny-all behavior for the contract's own assets. You explicitly grant what's allowed. old as-contract is gone. contracts are secure by default now.

If you're still writing Clarity contracts without `restrict-assets?` you're doing security the hard way. Post-conditions are security features you'd write client-side protecting the user, but now that feature is also available within Clarity to protect contracts.

@toony1908 @ECBSJ @x402stacks how many dev office hours appearances has it been for you so far tony

@ECBSJ @x402stacks totally!! let's do it!

Day 5 of posting until I get a million txs! Just shipped a new version of the @x402stacks facilitator! Major improvements are live to make the experience better!

@RaphaStacks if the @aibtcdev fever continues, stacks will become the default layer for ai

what’s the settlement layer for ai stacks — here’s why bitcoin defi: programmable BTC settlement for AI agents, trustless and without intermediaries what’s your number one reason 👇

@toony1908 @x402stacks Every hackathon submission = a few more tx toward 1M

Day 7 posting every day until @x402stacks hits 1M transactions! If you want to build something using x402, this is your time! There is a big Stacks hackathon running. 🛠️

For the full deep dive on these post-condition improvements check it out on our YT channel: youtu.be/SMQ7RaUyRko?si…

NFT post conditions currently only have two options: yes or no. But real builders needed a "maybe." `may send` is coming and it closes a real gap for complex contract logic.