Pillar Wallets — smart wallets, built for your app.
Gasless, passkey-native smart wallets on Stacks, adapted to your use case (credit cards, games, creator networks, consumer DeFi). We’re the facilitator — you focus on your users, we run the wallet + gasless infra.
Site + waitlist: https://www.pillarwallet.xyz/
30-sec look: https://www.youtube.com/watch?v=Zy39LdCk1ZY
Related topic: Clarity-webauthn: Passkey Verification Library for Clarity 5 [Follow-up] - #12 by Rapha23
Great initiative, Rafa.
From the perspective of building a consumer-facing app/game on Stacks, I think this direction is genuinely important. 
Even if someone builds a super-app, the first-user experience can still break at the wallet layer: installing a wallet, understanding seed phrases, saving them safely, funding gas, and only then trying the app. For many mainstream users, that is not just friction, it can be the point where they leave before experiencing the product.
I don’t think passkey smart wallets should replace traditional wallets for everyone. Leather/Xverse and other crypto-native wallets are still important. But users need a choice, especially for their first dApp experience.
Rafa has also helped us explore how this kind of architecture could fit into Strike on Stacks future PvP / game onboarding flow, and it made the problem very clear: if we want real consumer adoption, wallet UX has to become part of the product design, not an obstacle before the product starts.
Excited to see this being pushed forward on Stacks. 
The next blocker after capabilities: funding the SW.
A freshly-created passkey wallet is empty, so getting the first sats in is the real launch gate. Three layers to it:
Builder-sponsored to start. Builders can sponsor txs on behalf of their users at launch (paymaster), so a user can transact before they hold any sBTC. Enough to prove the loop and get people through the door.
CEX → sBTC bridge → SW. Users can withdraw BTC straight from a CEX through the sBTC bridge into their smart wallet — the cheapest real funding path today. This raises one fair question: the bridge reclaim path — if a deposit ever needs to be reclaimed and the user only has a smart wallet, who controls the reclaim key? It’s solvable cleanly: @friedger demonstrated deriving a deterministic seed from a WebAuthn passkey. We use that derived key as the reclaim pubkey, so the same passkey that governs the SW also controls the BTC reclaim path — no separate seed for the user to back up or manage. Reclaim stays in the user’s hands without breaking the no-seed-phrase promise at onboarding.
The real gap — credit-card funding. On-ramps like MoonPay exist, but integration runs ~$5k/year iirc. The wave of smaller builders experimenting with smart wallets via SWaaS can’t justify that cost — yet letting their users top up a smart wallet with a credit card would be a massive unlock for consumer onboarding. If anyone from Stacks leadership is reading: a shared / ecosystem-level CC on-ramp for smart wallets — so individual builders don’t each have to eat a $5k integration — could be one of the bigger adoption unlocks available right now. Happy to help scope it.
Here’s a quick blog entry to explain it simply: fak.fun
Great work !
BigMarket is currently rolling out cross chain predictions for evm/stacks and coming soon support for ed25519 wallets.
This work maybe points the way to integrating BigMarket with fingerprint auth via secp256r1-verify in our contracts @Rapha23 ?
