Forum Stacks Forum

For anyone who wanted the real flow rather than a loop: a full recording of opening a stream on mainnet, from wallet to live stream. If you try it and anything breaks, especially in the wallet step, post it here or DM me. Reports from this room are the fastest way I find and fix issues. More updates on X: @Stackstream0X .

Clarity Working Group — Notes, Sept 29, 2026 Written from the call with Brice, Hugo, Ryan and others. Please correct or add in the thread below. Clarity Language redesign and spec (Brice) A clean redesign of Clarity is under way. The goal is a precise written spec that becomes the source of truth, instead of whatever the interpreter happens to do. Why it matters: today Clarity’s meaning is effectively defined by one implementation. A second implementation (such as the WASM compiler) has to copy that implementation exactly, because any difference between nodes is a consensus split. A spec gives both a target to be checked against. Brice will share the draft publicly for feedback. WASM compilation Compiling Clarity to WebAssembly promises large execution speedups, especially for compute-heavy contracts and chains of contract calls, with a possible path to machine code. It runs on standard, widely tested WASM engines, which means fewer bugs that exist only in Stacks. It opens the door to other languages compiling to WASM and running on-chain later. Cost tracking could use WASM’s native fuel metering. That simplifies gas accounting and may allow higher block limits while keeping costs under control. The redesign and the spec feed directly into this: once it’s clear what the language should do, there’s nothing ambiguous left for the compiler to match. Cost estimation (Hugo) Clarinet already shows worst-case costs per function before deployment. Exact costs depend on inputs and con

𝗛𝗲𝗿𝗺𝗲𝘀 𝗖𝗵𝗿𝘆𝘀𝗼 𝗨𝗽grade Today we’re expanding Hermes. The 𝗖𝗵𝗿𝘆𝘀𝗼 upgrade turns Hermes into a liquidity gateway for Stacks. What started as a focused way to move USDC now supports a wider set of assets and chains, with a simpler flow and more flexibility in both directions. You can now move value from solana, @base , @0xPolygon , @avax , @arbitrum , Ethereum and other supported networks into Stacks, and move value back out when you need to. More routes will continue to be unlocked over time. One of the biggest changes is the experience itself. The previous flow involved multiple steps, approvals, and signatures. Chryso reduces that to a much simpler process. You can connect your wallet and send, or just send the funds yourself on your own terms. Your keys, your terms. Chryso also introduces 𝗠𝗶𝗻𝗶𝘀𝘄𝗮𝗽𝘀, so you can start with very small amounts if you want to test a route first. Hermes v1 remains available for large native USDC transfers. Chryso builds on top of it.This is the next step. Read More: https://docs.hermesbridge.xyz/docs/v2/overview/what-is-hermes-v2 Chryso: Bridge assets · Hermes Bridge

We made a design decision in stacks-passkey-wallet that’s worth putting in front of this forum: the wallet is derived from the passkey rather than stored anywhere. The path: WebAuthn PRF output → HKDF → BIP-39 entropy → Stacks and Bitcoin keys. A pure function, so the same passkey always yields the same keys, and they’re re-derived each time they’re needed. The seed phrase is still fully available to the user: they can reveal it, write it down, and restore in any standard Stacks wallet. The honest limit: a key derived on demand in a browser session is hot-wallet-class security, and we treat it that way. The library is MIT, open source, with two separate kinds of evidence: 81/81 on its internal suite, and 43/43 plus 5 negative controls on an independent vector verifier that imports nothing from the library. Full write-up: We Re-Derive It. We Never Keep It. — DeOrganized Design questions are argued in the open in the repo’s GitHub Discussions: DeOrganized/stacks-passkey-wallet · Discussions · GitHub Happy to go deep on the derivation choices here.

We made a design decision in stacks-passkey-wallet that’s worth putting in front of this forum: the wallet is derived from the passkey rather than stored anywhere. The path: WebAuthn PRF output → HKDF → BIP-39 entropy → Stacks and Bitcoin keys. A pure function, so the same passkey always yields the same keys, and they’re re-derived each time they’re needed. The seed phrase is still fully available to the user: they can reveal it, write it down, and restore in any standard Stacks wallet. The honest limit: a key derived on demand in a browser session is hot-wallet-class security, and we treat it that way. The library is MIT, open source, with two separate kinds of evidence: 81/81 on its internal suite, and 43/43 plus 5 negative controls on an independent vector verifier that imports nothing from the library. Full write-up: We Re-Derive It. We Never Keep It. — DeOrganized Design questions are argued in the open in the repo’s GitHub Discussions: DeOrganized/stacks-passkey-wallet · Discussions · GitHub Happy to go deep on the derivation choices here. 1 post - 1 participant Read full topic

This Week’s News & Stories - Fri, 25 Sep 2026 View this on stackssnacks.com and subscribe to receive updates via email. Gm 👋 😋 Stacks Snacks Anchorage Digital is building Bitcoin Staking support on Stacks . Institutions can fund a BTC Bond from their Anchorage account, earn weekly BTC rewards, and reclaim principal at maturity, with Bitcoin held in Anchorage's institutional custody at a federally chartered bank ⚓︎ Zest's Bitcoin Collateral Vaults are now live : deposit native BTC into a self-custodial vault on Bitcoin L1 and borrow Ethereum USDC against it, with your Bitcoin under your custody. Even WallStreetBets noticed 👀 Twitter tweet 📆 Coming Up Alex Miller joins the Bitcoin Treasuries Conference panel "When DATs and DeFi Collide" with Jeff Park (ParaFi Capital) and Bill Barhydt (Abra). Stacks is at Korea Blockchain Week . Muneeb will keynote "Bitcoin's Next Frontier: From Store of Value to Productive Capital" on the BitGo stage. Set a reminder for next week’s Stacks Monthly Ecosystem Update . 👀 Other Tasty Content Whale activity is climbing on Zest's Stacks market . One position added $490,000 in borrows while earning 0.82% APY net 🍊 BoostX is bringing Bitcoin Tags to X, tags like STX₿, sBTC₿, and ZEST₿ that surface a live Bitflow swap quote on hover. The team is joining a space today where you can learn more 🚀 Rand Group makes the case for Stacks as the leading Bitcoin L2 . An inside look at the first institutional Bitcoin bond on Stacks . Happy staking 🟠 Stacks is a Bi

Posting a receipt, not a claim: a real mainnet stream, STX Transaction - 0xe8367…89148 , Stream ID 11, 1.2 USDA over 2,160 blocks, created and then claimed. The read-only calls are public, so you can query it directly or paste the ID into the dashboard lookup. This one is between our own wallets, labelled as such. Happy to walk anyone through the Clarity side, including claim maths and cancellation edge cases. Sharing a stream receipt end to end, in case it helps with your own milestone evidence. Everything checks out in the explorer, which saves a lot of “trust me” in grant reports. Standing offer: a test stream between our projects, and I will set it up. Weekly numbers on X: @Stackstream0X . stackstream.xyz StackStream Real-time money, settled on Bitcoin. Streaming payroll, grants, and subscriptions for DAOs, merchants, freelancers, and grant programs on Stacks.

Posting a receipt, not a claim: a real mainnet stream, STX Transaction - 0xe8367…89148 , Stream ID 11, 1.2 USDA over 2,160 blocks, created and then claimed. The read-only calls are public, so you can query it directly or paste the ID into the dashboard lookup. This one is between our own wallets, labelled as such. Happy to walk anyone through the Clarity side, including claim maths and cancellation edge cases. Sharing a stream receipt end to end, in case it helps with your own milestone evidence. Everything checks out in the explorer, which saves a lot of “trust me” in grant reports. Standing offer: a test stream between our projects, and I will set it up. Weekly numbers on X: @Stackstream0X . stackstream.xyz StackStream Real-time money, settled on Bitcoin. Streaming payroll, grants, and subscriptions for DAOs, merchants, freelancers, and grant programs on Stacks. 1 post - 1 participant Read full topic

quick update on privara: the product has moved quite a bit since the original post. we now support private payments to bns names, usdcx transfers, improved stealth-address flows, sponsored spending, and a much cleaner receiving experience around private identities and recovery. i’ve also moved privara to a new home at useprivara.xyz , which is now the main place to try the product and follow the project as it develops. still building, testing, and tightening the privacy model, but the experience is starting to feel much closer to what i originally wanted: share a normal stacks identity, receive through fresh private destinations.

Reviving this thread because I’m building exactly this gap. @raphasierra.id.block , thanks for documenting it so clearly, and @PeaceLoveMusic.btc for the USDC → USDCx route. What I’ve found so far: the sbtc SDK’s buildSbtcDepositAddress returns a plain P2TR address with the deposit and reclaim scripts baked in. Anything that can send BTC to a bc1p address can fund an sBTC mint. Exchange withdrawals already work (as Pillar described), and Transak’s widget accepts a custom walletAddress on the Bitcoin network. What’s missing is the glue: generating the address just-in-time, watching it for the incoming tx, calling Emily automatically, and showing a live paid → confirmed → minted status. I’m building that as an open-source embeddable React component plus a small backend (card → BTC → sBTC), with an all-in cost comparison across routes. I’m testing Transak staging this weekend and will post what I find, including whether bc1p destinations are accepted. Two questions: Pillar team: did you settle on a flow since January? Would you be open to trying this as a design partner? Has anyone run Transak, Ramp or Banxa to a bc1p sBTC deposit address in production? Any minimums, fees or gotchas? I’m also planning to apply to this quarter’s Endowment grants with this, so feedback on what would make it useful for your apps is very welcome. Repo (WIP)