What type of campaigns or outcomes are you looking to see here? It’s a great idea since it’s one of Stacks’ strongest brands. I grapple with the growing desire for privacy. I have rena.btc and use it seldomely since I don’t want to have wallet interactions noted. What other uses/awareness would help Stacks with BNS? I’m all ears 
1 Like
Reply to Treasury Committee 2026 Wishlist
A few items from the trenches.
Smart wallets and account abstraction are underexplored on Stacks. Sponsored transactions, session keys, social recovery — these UX primitives let apps onboard users who’ve never touched crypto. Related: sponsored txs need relayers. x402 endpoints could let facilitators relay and cover fees, removing friction while keeping trust assumptions clean. BitFlow’s Keeper architecture is a reference.
Clarity 5 ships soon with the secp256r1 fix — native Face ID / Touch ID auth becomes possible. No seed phrases. That’s a marketing moment worth coordinating around, not just a changelog.
On-ramps and off-ramps — would love to see more focus here. Fiat → sBTC / STX with minimal friction is table stakes for user growth. What’s the current state? Are there gaps worth prioritizing?
Would love to see providers like Privy and Turnkey enable Apple Pay and Google Pay flows into the Stacks ecosystem. That’s a real onboarding unlock.
3 Likes
On/Off ramps are on the plan! Key focus to reduce friction.
Re smart wallets and account abstraction – could you go further? Wondering if this could be rolled out by the wallet operator directly?
2 Likes
Noted!
1 Like
Re smart wallets: Yes — wallet operators could roll this out directly. Pillar is our proof-of-concept: passkey auth, spending limits, session keys, guardian-based auto-deleveraging. Early beta users are asking for Moonshot integration for on-ramps, though we haven’t fully evaluated options yet. As my collaborator Grant puts it: “We want the simplest onboarding possible.”
One thing worth flagging: Clarity 5 enables native secp256r1 (passkeys/Face ID), but there’s a gap between how WebAuthn signs and how message hashes are verified on-chain. I’ve outlined this in a follow-up post. Not sure yet how much work it is, but it seems like a good candidate for ecosystem-wide tooling to ship alongside Clarity 5.
First step imo would making BNS more visible in Leather and Xverse. Accounts there still only say Account 1, instead of showing my primary BNS name. Also, Leather doesn’t even link to BNS in its Browser Tab. Better profile pages that are easily shareable on the web (via a linktree style app) would also be cool. In general, better / easier DNS integration would be great (via btc.us?).