Skip to content

v4.0.0 — On-device mining (opt-in)

Choose a tag to compare

@ogaworld369 ogaworld369 released this 15 Nov 23:57
· 31 commits to main since this release

The biggest update yet: the node app can now mine on the phone itself.

What's new

  • Mining on the device, as an opt-in (off by default). With mining on and a rewards inner hash saved in Settings, the bundled node starts as a validator and the bundled official miner (quantus-miner v4.2.1, rebuilt without its HTTP metrics exporter) runs as a second process, fed jobs by your own node. Rewards go to the wormhole address of your own inner hash. With mining off, the app behaves exactly as v3.0.2 does — same launch arguments, same processes, no new permissions (still five), and the bundled node binary is unchanged.
  • Thermal protection. Mining defaults to 2 CPU workers (1 / 2 / 4 / auto selectable). At the platform's "moderate" heat level the worker count is halved; at "severe" or above the miner stops for the rest of the session and the status says why. The cap and the stop are held across the app's own restarts within a session. The phone is never pushed to its limit.
  • A support footer at the bottom of the Home screen shows the developer's QTC donation address; tapping it copies it. Donations are voluntary — the app never sends anything to it.
  • Session uptime now freezes when the node stops, instead of counting on.

Before you mine

  • You need a rewards inner hash from the official tooling (the value behind the Address: line of quantus-node key quantus --scheme wormhole). After the first start, the app shows the rewards address the node reports — compare it with the tool's address for your inner hash before you rely on it. The inner hash is a preimage, not a key: it cannot spend rewards, and by protocol design it becomes public in block headers once blocks are produced. It is stored only in app-private settings and is scrubbed from logs, screens and shared diagnostics.
  • While mining, the node opens UDP port 9833 for the miner connection. The connection requires a 256-bit auth token and a pinned TLS certificate fingerprint, both held only in app-private storage; the rewards destination is fixed by the node's launch arguments and cannot be changed over this endpoint. The port is reachable from other devices on the same network while mining — see SECURITY.md for the full note.
  • Set expectations honestly: at the network's current difficulty, a phone's expected wait for a block is very long. Mine to take part, not for income.

Verified before release

  • External audit rounds covered the mining implementation and the finished tree; every verified finding was fixed, and a closing review of the fixes found nothing that required rebuilding the APK.
  • On a real device (Pixel 9a / GrapheneOS): an in-place update over v3.0.2; mining switched on; the miner receiving jobs from the bundled node (42 jobs in the first session); the reported rewards address matching the maintainer's wallet address for the same inner hash; the miner's metrics exporter inactive; the shared diagnostic text carrying the inner hash only as "saved".
  • Not observed on a device: a solution actually found and accepted — the expected wait is far longer than any test session, so that path rests on the test harness's parsing of the official miner's real log lines and on the unmodified interface between the official miner and node binaries.
  • JVM suites: 430 mining checks, 330 base checks, 393 transfer checks — all passing.

Requirements

  • Android 12 or later, arm64 device. Verified on Pixel 9a running GrapheneOS. The app is tested on GrapheneOS, so devices running the same OS should work without problems. Other devices are expected to work too; OEM battery savers may stop the resident service — reports via Issues are welcome.

Download

  • quantus-node-v4.0.0.apk — 63,442,275 bytes
  • SHA-256: ca90bbae260d5c9c2e45e20c9507f452f12350557e0dc4c61d0a51c4563dcffd
  • Signed with the project's release key (certificate SHA-256 65bb1a5fef27d70be1dd12fc12ce3484b4c848fceca92f8898cd96cb2784f6ff), the same key as every release since v0.1.0. v4.0.0 installs over v3.0.2 keeping settings and synced data.
  • Update in place: if you already run the app, install this APK over the existing app — do not uninstall first. Uninstalling deletes the node database, your settings and your activity-recording identity.

Feedback

Bug reports and device reports are welcome in Issues. Full details of this release: CHANGELOG.md.