TUWA is an open-source (Apache-2.0) TypeScript toolkit for self-custodial apps on EVM and Solana: wallet connection (Satellite Connect), multi-chain sign-in (SIWX), transaction tracking that survives page reloads (Pulsar), React components (Nova UI Kit) and a backend you can self-host (Quasar). This week we put the Solana side to a public test.
Why we ran a benchmark
web3.js v3 and wallet-adapter v3 shipped this week, both rebuilt on Solana Kit. That s good news for everyone building on Solana, and it raises a fair question: why add TUWA if the official stack now runs on Kit too?
Instead of answering with opinions, we built the same app on both stacks: connect a Wallet Standard wallet, sign in with a server-side session, then send and track a SOL transfer. Same mock wallet with a real ed25519 key, same local RPC with 400 ms slots, bundles built with esbuild and gzipped, React excluded.
What we measured
Tired of bloated, legacy wallet connection libraries? Exhausted by WaaS vendor lock-ins like Privy or Dynamic?
You are in the right place.
I built TUWA because the Web3 infrastructure space has become a mess of monolithic dependencies and proprietary traps. TUWA is a headless-first, modular Web3 stack designed for both EVM and Solana. I built this for purists who value self-custody and local-first architecture.
Here is what makes TUWA the definitive standard:
Strict Modularity: I completely separated Logic from UI. Choose exactly what you need: Orbit (Core), Satellite (Auth), Pulsar (State), or Nova (UI).
Chain-Agnostic SIWX: I engineered a native SIWX (Sign-In with X) module based on the CAIP-122 standard directly into the Satellite layer for seamless, multi-chain authentication.
Clean Dependencies: Powered strictly by viem, wagmi, and gill. You will find zero ethers.js or web3.js legacy code here.
True Lifecycle Tracking: I built the only solution offering comprehensive client-side transaction tracking (from Pending to Replaced/Confirmed/Failed) without relying on proprietary APIs.
No Vendor Lock-in: The keys always stay with the user. Zero reliance on MPC.
To solve the final piece of the puzzle—cross-device transaction history synchronization—I am also rolling out Quasar. Quasar is a cloud-based SaaS extension for the TUWA ecosystem that acts as a Sync & History API. It is powered by Alchemy for robust infrastructure and strictly respects privacy: it stores metadata, but it never touches or stores keys.
If you are ready to stop fighting with rigid templates and want absolute control over your dApp's infrastructure, TUWA is your toolbox.
Explore the stack at https://www.tuwa.io/ and drop your technical questions below. Let's get straight to the point and build Web3 the right way.