Quantus Android Node (working title)

Android-only, open-source app that runs a Quantus Network (QTC) full node on a phone.

Purpose: decentralization, not profit. This node does not mine and earns no rewards. It syncs, verifies every block itself, and relays data to peers — so the network depends a little less on a small number of servers, and a little more on ordinary people with hardware they already own.

Status: Phase 1 MVP — running on a real device. The node now runs on a Pixel 9a (GrapheneOS): on 2026-11-03 it started on-device, connected to 12 peers and was syncing the mainnet chain (block #61,642 of #341,089). Still in progress: full-sync completion and the remaining on-device checks (hours of uptime, pruned database size, battery/heat, stop/restart). There is no public release yet. The release gates are listed in docs/RELEASE.md. Design: docs/DESIGN.md.

Product concept: make the node's pulse visible — live block/peer visualization with a quiet "presence" (KEHAI) design, a local record of your contribution, and a quantum-threat watch. The UI speaks 9 languages (see docs/I18N.md; native-speaker improvements are very welcome). Telemetry listing is opt-in only (default off).

Usage

New to the app? Start with the Usage Guide — available in all 9 languages the app speaks: English, 日本語, 简体中文, Español, हिन्दी, العربية, 한국어, Русский, Français. Requirements, installation, the first sync, settings, and troubleshooting.

Scope

• A non-validator full node for Quantus mainnet: sync, verify, relay, local status.
• No mining. No wallet. The app never handles seed phrases or reward keys — by design, there is no asset secret inside the app worth stealing.
• Devices: not Pixel-only. Requirements: Android 12+ on arm64 — the implementation has no Google-services or Pixel-specific dependency (it runs on GrapheneOS, which ships without Google services). Verified so far: Pixel 9a running GrapheneOS. Other devices are expected to work but are unverified; OEM battery savers (Samsung, Xiaomi, …) may stop the resident service. Device reports via GitHub Issues are welcome — the verified list grows from them.

What we know so far

• Upstream: quantus-node v1.0.5 (Quantus-Network/chain), Substrate-based, QPoW / Poseidon2, ML-DSA signatures.
• The node cross-builds for aarch64-linux-android. Two small patches are needed, both in patches/: one makes explicit pruning values take effect (next bullet), and one stops DNS resolution from panicking when the node runs as a plain process outside an Android app runtime (vendored ndk-context / hickory-resolver with a fallback). The build recipe is fixed in docs/BUILD-android.md. Release-profile binary: ~53 MB stripped (debug: ~123 MB).
• Upstream forces archive storage on all nodes; a minimal patch (respect explicit numeric pruning) enables a phone-sized database. Details in the design doc.
• Official minimum specs list 100 GB storage (validator-oriented); a pruned non-validator node is expected to be far smaller. On-device measurement is pending.

Roadmap (summary)

• Phase 0: feasibility spikes (mainnet DB size with warp + pruning; Android port blockers)
• Phase 1: node MVP (sync/verify/relay, status UI, foreground service)
• Phase 2: daily-driver hardening (power, data, storage caps; GrapheneOS soak tests)
• Phase 3: security review, reproducible builds, public release prep
• Phase 4: mainnet release and wider Android device support

Security first

The only secret is the node's P2P identity key, kept in app-private storage and excluded from cloud backup (allowBackup=false). RPC stays on loopback only. No analytics, no ads, no remote code loading — native code ships inside the signed APK only. Distribution is planned as signed APKs on GitHub Releases (and F-Droid), gated by docs/RELEASE.md.

License

To be confirmed — Apache-2.0 is the leading candidate, matching upstream.