We just rolled out Quasar Community Edition v0.2.0, solving one of the biggest dilemmas in Web3 developer tools: vendor lock-in.
Start on Quasar Cloud for convenience, move to your own self-hosted server whenever you want without losing data, transaction history, or breaking your live apps.
Here is how the Cloud Community Edition migration works:
We just rolled out a major stack-wide update across the entire TUWA ecosystem, syncing all 11 repositories to bring developers a seamless, sovereign Web3 building experience.
Here is what just went live:
CAIP-2 for Solana: Full end-to-end alignment using the genesis hash (CAIP-30). Synced across Orbit 0.4, SIWX 0.5, Satellite Connect 0.7, Pulsar 0.9, Nova UI Kit 0.8, and SDK 0.3. Full backward compatibility for existing solana:devnet sessions.
Excited to share an official milestone for the TUWA ecosystem: Quasar Community Edition is officially public under Apache-2.0, tagged at v0.0.3.
Most dApp developers hit a common roadblock: either they get trapped in closed WaaS silos with per-user fees and vendor lock-in, or they write fragile custom scripts to track transaction states across page refreshes and network switches.
Quasar Community solves this by giving you a standalone, 100% self-hostable indexing engine with zero telemetry and no MAU limits.
We ve hit another massive milestone for the TUWA open-source ecosystem: Quasar Community Edition is now 90% locked in.
We are building Quasar as a sovereign, self-hostable L5 transaction indexing and webhook engine. Here is where we stand on stripping out enterprise SaaS bloat and preparing for our v0.0.1 public release:
We ve just locked in two major milestones for Quasar Community Edition (part of the TUWA open-source ecosystem): Phases 3 & 4 are officially completed.
Most modern developer tooling gets bloated with enterprise marketing layers, heavy dashboards, and SaaS overhead. We took the opposite approach: stripping Quasar down to a pure, sovereign, and self-hostable L5 transaction engine.
We re currently deep in the process of open-sourcing the Quasar Engine under the Apache 2.0 license as Quasar Community Edition.
Quasar is designed as a high-performance, durable tracking layer for multi-chain Web3 transactions across EVM and Solana. As part of our Build-in-Public journey, we wanted to share our approach to decoupling a private SaaS into a lean, self-hosted community node:
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.
True decentralization requires sovereign infrastructure. If the client stack is open-source and non-custodial, the transaction indexing and synchronization backend has no right to remain a closed black box.
We have officially kicked off the transition of Quasar Engine to Open Source (Apache 2.0)!
The Quasar Community Edition is not a stripped-down demo. It is a full enterprise-grade sovereign infrastructure node designed to be self-hosted with zero vendor lock-in.
What is currently in active development for the OSS Community release:
Account Abstraction promised to solve the clunky UX of Web3: sponsored gas, atomic batching, and no manual seed phrase bottlenecks.
Yet, mainstream adoption took a massive shortcut by pushing teams into closed Wallet-as-a-Service (WaaS) suites. Developers traded sovereignty for convenience, tying application frontends to proprietary relayer clouds and vendor-locked key schemes.
True Account Abstraction requires no custodial or vendor-locked compromises. By decoupling the Signer (key authority) from the Account (on-chain execution engine), engineering teams can build ultra-lean smart accounts while keeping keys 100% sovereign.
