Quasar Community Edition is 90% locked: Build determinism over semver hype

Hey Product Hunt community! 👋

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:

1. Codebase at 90% & Automated Upstream Sync

• The standalone FOSS engine is compiled and fully operational.

• Automated AST pruning and a cryptographically signed CI/CD sync pipeline directly from our private upstream is active.

2. FOSS Compiler & Security Gate

• Snapshot generator purged 73 dead modules via AST reachability analysis.

• Verified immutable @sha256: container digests across the entire supply chain.

• Automated sanitization for all internal hostnames and secrets.

3. Toolchain Stability: Why We Froze on TypeScript 6.0 LTS

We made a deliberate engineering decision to pause the TypeScript 7 migration:

• Critical AST transformers, bundler plugins, and linters in the broader ecosystem still throw blockers on TS 7.

• All core TUWA packages (@tuwaio/orbit, pulsar, satellite, nova, siwx, sdk) already operate on modern, type-safe LTS standards (Node.js 24, Viem v2, Payload 3.88).

• When developers pull a self-hosted node, it must build deterministically with zero surprises. We don't break developer pipelines for semver vanity.

4. Staging Node Verified

• Live standalone deployment on real VPS infrastructure confirmed (<60s cold boots, zero telemetry leakage, zero external SMTP/S3 bloat).

What we are actively testing in the trenches:

Before tagging the official release candidate, we are running rigorous manual audits:

• Multi-chain tracking: Real-time lifecycle tracking across EVM (ERC-4337 bundlers & paymasters, Safe multisigs) and Solana.

• Single-admin sovereignty: Native credentials, RFC 6238 TOTP 2FA, and clean /admin routing without cloud auth crutches.

• Engine utilities: Transaction PDF receipt generation in the dashboard, BullMQ webhook dispatchers, and automated retry queues under load.

What’s next:

1️⃣ v0.0.1 Tag & Public Smoke Test: Releasing the public TuwaIO/quasar-community GitHub repo.

2️⃣ Self-Hosting Guides: Complete setup documentation for <60s local nodes (docker-compose.minimal.yml) vs. hardened production VPS nodes (Traefik v3 + Cloudflare Tunnels).

3️⃣ Public Docs & Tutorials: Full documentation refresh on https://www.tuwa.io/.

For the infrastructure and backend builders here: how do you approach toolchain stability vs. migrating to the latest compiler/language releases in production?