How to set up a full Web3 starter with Quasar Cloud Sync in under 2 minutes âš¡
Hey Product Hunt community! 👋
When building dApps, developers usually face a frustrating trade-off: either surrender control to closed, custodial WaaS (Wallet-as-a-Service) silos, or spend weeks writing custom glue code for transaction lifecycle states and complex local webhook testing.
We built TUWA and Quasar to eliminate this friction entirely.
Here is what the end-to-end flow looks like:
Instant Scaffolding: Spin up a production-ready Next.js 16 + React 19 app in seconds via npx @tuwaio/create-cosmos-playground, powered by @tuwaio/sdk, viem, wagmi, and @solana/kit.
Zero WaaS Lock-in: Drop your credentials into .env to enable non-custodial transaction indexing and cross-device sync. Keys stay strictly with the user; only transaction metadata is indexed.
Tunnel-Free Local Debugging: Register your webhook directly as http://localhost:3000/api/webhooks/quasar inside the Quasar Dashboard and stream verified HMAC-SHA256 events to your local machine using our open-source CLI (npx @tuwaio/quasar-sdk listen) without ngrok or third-party proxies.
📺 Watch the 90s video demo: Check out the full walkthrough on X: https://x.com/TUWA1025123/status/2099732444241141892?s=20
Explore our ecosystem hubs:
Website: https://www.tuwa.io/
Docs: https://docs.tuwa.io/
Dashboard: https://quasar.tuwa.io/
We’d love to hear your feedback: How are you currently managing client-side transaction lifecycles and local webhook testing in your Web3 stack?

Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.