TUWA Ecosystem Overhaul: Core primitive sync & unified 3-tier docs

Following the Quasar Community release, we have executed an ecosystem-wide architectural synchronization across the entire TUWA stack.

Here is what went live over the past 48 hours across our core primitive layers:

• Orbit (v0.3.2): Viem transports, Solady smart accounts & normalized Solana Kit clusters

• SIWX (v0.4.0): CAIP-122 multi-chain auth, native ed25519 Web Crypto & persisted session store

• Satellite Connect (v0.6.1): Headless wallet connection store, auto-connect resilience & Safe detection

• Pulsar (v0.8.1): Reload-safe transaction pool, Zustand storage journaling & speed-up/cancel detection

The Core Shift: 3-Tier Web Architecture

We are eliminating documentation drift and redundancy by splitting resources into a strict hierarchy:

1. Central Hub (https://docs.tuwa.io/): The macro view. Interactive dependency graph with live npm versions and hover tracing, cross-layer architectural guides, and embedded sandboxes.

2. Sub-Docs (*.docs.tuwa.io): The micro view. Standardized TypeDoc API references and package READMEs without duplicate setup snippets.

3. Landing (https://www.tuwa.io/): Transparent /pricing ($0 self-hosted Community vs. usage Cloud) and an interactive 8-phase roadmap.

In the Active Pipeline:

• Nova UI Kit: Strict bundle tree-shaking so EVM-only builds never bundle @solana/kit (and vice-versa).

• SDK Metapackages: Harmonizing @tuwaio/sdk with the new core releases.

Everything is 100% open source under Apache-2.0.

GitHub Organization: https://github.com/TuwaIO

We’d love to get feedback from fellow Web3 builders: how are you currently handling multi-chain session state and transaction persistence across page reloads in your dApps?