Repository navigation
Releases
v4.2.5
Mining performance release
The bundled miner now computes the proof-of-work hash with a batched engine that processes four nonces at a time in a transposed layout, reusing one hashing setup across the batch. Measured with a bench built from the shipped source on a Pixel 9a: 436,642 hashes/s per thread, against 357,195 for the previous engine (about 1.22x). The engine is plain Rust with no unsafe code, is differentially tested against the previous engine and the reference implementation, and returns exactly the same results. The bundled node binary is unchanged, there are no feature or permission changes, and mining stays opt-in and off by default.
Full changelog: CHANGELOG.md
Install
Download the APK below and install it over your current version — settings and records are kept.
- APK: 63,582,911 bytes
- SHA-256:
ca7d206d16836245407d99517968377bfbf0dc834d9353c92ef5af107cd0daa9
v4.2.4 — Security fixes: verified node RPC endpoint, handover hardening
What's new
- The security fix release for the external audit of v4.2.3. That audit found no critical or high issues (one medium, eleven low, twelve informational); every item is fixed here, or accepted with the reason recorded in SECURITY.md. An audit of these changes found no critical or high findings either (one medium, three low), and every verified finding was fixed in this release. No feature changes, no new permissions, and the bundled node and miner binaries are unchanged from v4.2.3.
- The app now verifies it is talking to its own node. The node does not fail when its RPC port (9944) is taken — it silently rebinds to a random port — so polling a fixed address could have meant polling another app's listener. The app now adopts the RPC address and peer identity from the node's own startup output and checks the identity on every poll. The activity recording and the identity transfer read through a record of the same facts that stays valid only while that node process lives.
- Log-derived figures count only the node's own lines. Statistics, the miner's start gate and the diagnostics' WARN/ERROR counts act only on lines in the node's own header format; control and bidi control characters are stripped before a line is stored, shown or shared; and shared diagnostics now mask every non-loopback address, not only the device's own.
- Less of the node is visible by default. Your display name is passed to the node only while telemetry is on (peers otherwise see the default name); mDNS no longer advertises the node on the local network; the Prometheus metrics endpoint and offchain workers are off.
- Handover hardening. The confirmation number is now derived from the handover's own secret instead of the transfer code; packages are capped at 16 MiB (about 19,900 checkpoints) and imports stream into place instead of buffering the whole file in memory; the transfer-code entry and dialogs gain the same input and screen protections as the inner-hash editor. Both devices need v4.2.4 for a handover — an older version cannot read the new package (a v4.2.4 device still reads packages from older versions).
Install
Download quantus-node-v4.2.4.apk (63,566,527 bytes) and install it over your current version — settings and records are kept.
SHA-256: 845f5f7375ffb776d3d0959608c6d56a5bcac031d43a440f798aad99a26e3b3d
Note
Published ahead of on-device verification; the on-device checks (above all, the node reaching sync through the adopted endpoint, and a mining start with the new launch arguments) follow. A further external review of this release is scheduled; any findings will be addressed in a later release.
Full details: CHANGELOG.md
v4.2.3 — Rebuilt binaries: loopback miner endpoint, dependency security updates
What's new
- The bundled node and miner binaries are rebuilt — the first binary change since v3.0.2. No app features change; no new permissions; no changes to the node launch arguments, the database or the data formats.
- The miner endpoint now listens on loopback only (127.0.0.1:9833). It previously listened on all interfaces, with the auth token and the TLS certificate pin as the boundary. The only miner this build ever serves is the one bundled in the same app, and the token and pin remain in place as further layers for that local connection. The mining confirmation text now says the port is reachable only from within the device, in all nine languages.
- Dependency security updates in both binaries. Node:
quinn-udp0.5.16 andhickory-net/hickory-proto0.26.2. Miner:rustls0.23.46,rustls-webpki0.103.16,quinn-proto0.11.19,quinn-udp0.5.16,anyhow1.0.104 andcrossbeam-epoch0.9.20. The dependency audit was re-run after the rebuild: the node's shipped closure is down to the two long-standing items that have no fix inside the pinned framework's ranges, and the miner's shipped closure has none. - The bundled CA roots are refreshed, and the third-party license notices are regenerated for the updated dependency sets.
Install
Download quantus-node-v4.2.3.apk (63,550,143 bytes) and install it over your current version — settings and records are kept.
SHA-256: 09fe2b2b59f1ca54015634f5243c67c353f1e5ab58dd2539ef9e634d97724a6d
Note for miners
After updating, turn mining on once and confirm that jobs arrive as before. The miner now reaches the node over loopback only — the same path it always used — so nothing about how you mine changes.
Full details: CHANGELOG.md
v4.2.2
versionCode 68 / v4.2.2 — 2026-11-16
- A polish release: the remaining low findings of the external audit of v4.2.0, its follow-up checks and the gap inventory — all fixed except the notification bidi item (phase-1 L-7) and FC-3, which remain as accepted items. No new features, no new permissions, and no changes to the node launch arguments, the database or the bundled binaries.
- The member card's streak is labelled as what it is. The value is the longest streak, but several languages said "consecutive days"; all nine now say the longest consecutive run.
- The Storage page also shows the device's free space, under the app's total — the same reading the diagnostic summary already took.
- The price and donation sheets are properly modal, and say what their controls do. The donation sheet gains an explicit copy button (tapping the address still copies it too); the sheets' close buttons are named for screen readers; and while a sheet is open, the content behind it is hidden from accessibility services.
- The settings lock covers the price switch in both places — Settings → External information and the price sheet — and the External information page now shows the same "why it is disabled" notice the other locked sections show.
- Value rows no longer crush their labels. The tappable value rows (home mining and price, the settings hub, the mining rewards and workers rows) and the home today row are built on the stacking row layout the read-only rows already used: a long value in a verbose language stacks under its label instead of squeezing it. The today row also gains its chevron and opens the record tab, and slide direction follows the app's language rather than the device's.
- Smaller row and navigation fixes. Arriving at Settings from a tab is a forward slide, not a return; tapping a switch row gives the same haptic answer as tapping the switch itself; the transfer page's "other actions" toggle is a full 48 dp target; the duplicated section headings on the Mining, DePIN, Storage and Transfer pages are gone (the page header already carries the title); and the home block number is built at its fitted pixel size, so the first frame no longer jumps at font scales other than 1.0.
- Price freshness no longer trusts the wall clock. Staleness is judged on the monotonic clock (persisted with each fetch, together with the boot count, so a reboot is recognised and the wall clock takes over as the fallback after it), a stored fetch time in the future counts as stale, and failed fetches retry after 15, then 30, then 60 minutes instead of 5, then 15. The fetch now identifies itself with the app's actual version.
- The daily record is written at most every 15 minutes (and on node stop, as before), instead of about once a minute; a crash can now lose at most 15 minutes of one day's counters. Its retention moves at most a day per save, so a clock reading far in the future can no longer prune the real history in one save, mining time is counted across delayed polls but never across a suspend, peer samples belong to the day they were taken on, and a replaced poller's final write can no longer cost the live session an interval of mining time.
- Mining robustness. A thermal stop is now requested before its log line is written, so an Error escaping the log call cannot leave the miner running (a full disk cannot do it — the log already swallows an IOException); and while a thermal stop is latched for the session, the miner restart button is disabled instead of sitting enabled and doing nothing.
- Verified on the JVM suites before release: core 330, transfer 393, mining 587, vision 214, transfer-flow 22, observer-hold 18 — all passing, 0 failed — and the string table complete at 447 keys × 9 languages, 0 missing.
- Release record. APK: 63,546,047 bytes, SHA-256
0284fadd1444bc9279c1567a3f8022d76bd5773bfdf55eb201db2c08a6c1016e.
v4.2.1
v4.2.1 — fixes from the external audit of v4.2.0
A fix release. The external audit of v4.2.0 found no critical issues; its two high and five medium findings are all fixed here. There are no changes to the node launch arguments, the database, the bundled node and miner binaries, or the permissions (still five), and no data is migrated — v4.2.1 installs over v4.2.0 keeping settings and records.
Fixed
- Storage sizes measure again. The Settings hub split in v4.2.0 left the size measurement gated to the hub screen, so the Storage page could sit on "Measuring…" and kept showing the pre-deletion sizes after a "delete the chain database and resync". The measurement now runs on the Storage page itself.
- The price and donation sheets no longer slide under the bottom navigation. The donation address is fully visible and tapping it copies it, instead of switching tabs; the price sheet's disclosure is fully readable. The how-to-read sheet's panel also clears the navigation.
- A failed start leads straight to the diagnostics. In a failure state (or after a time-limit stop), "Node details" opens with the Diagnostics section expanded.
- The Settings hub's Node row no longer shows a value. It displayed the telemetry switch as "Node On/Off", which read as the node's own state.
- A stale QTC price dims on the home row too, as it already did inside the price sheet.
- The first-run paragraph no longer pushes the Start button down. While the introduction shows, the metric block (all dashes in that state) is hidden.
Verification
- JVM suites: 572 mining checks, 330 base checks, 393 transfer checks — all passing.
- The sheet overlap behind the second fix was confirmed on a real device in v4.2.0.
Download
quantus-node-v4.2.1.apk(63,475,120 bytes)- SHA-256:
c5a07aea4a87d62557edb221b052abffce6d6353e9e4497d9be26752c489ee0e
v4.2.0
What's new in v4.2.0
The home screen is a list now. Under the status card and the start/stop button, everything is a row: today's record (with a progress bar), mining, the QTC price, node details, the activity track and donations. The price card is gone — tapping the QTC row opens a price sheet with the larger figure, the 24-hour change and the source, and the donation address has its own sheet too. Until the node has run for the first time, the status card shows a short paragraph on what the app does.
Price fetching can be switched off, and says what it does. The price sheet and the new External information settings page carry a switch for price fetching (on by default) and a note on what a fetch connects to and what it never sends. The refresh interval is now one hour instead of five minutes.
Settings is a hub of pages. Settings opens as a list — Node, Mining, DePIN records, Storage, Device transfer, External information, Language, About — and every row shows its current value. The sections themselves work as before.
The member tab scrolls, and the card has its declared ratio. The member screen is a scrolling column: the card (now formally 1.42:1, reached by tightening margins only), with a standing note below it that the records live only on this device, are never converted into money and carry no ranking. A long press on the member number copies it.
Motion and touch. Screen changes fade or slide briefly, sheets rise from the bottom, the main button answers a press immediately, toggles and the resync confirmation have haptic feedback, and screen changes are announced to accessibility services. All motion follows the system's animation setting.
Smaller fixes. The notification icon is now a monochrome silhouette of the eye; in Japanese, "best block" reads "latest block"; the network ticker shows the newest event on a single line; the home block number shrinks to fit its line instead of wrapping at large font scales; right-to-left layouts keep Latin-script values in their own direction run.
Install
- APK: quantus-node-v4.2.0.apk (63,475,120 bytes)
- SHA-256: 3a788e7835aeed77970d72074024dacc1331d1963c584d6de0ad777046dfe0bf
- An in-place update over v4.1.0 keeps all data.
v4.1.0 — Storage management and readability fixes
v4.1.0 — Storage management and readability fixes
A maintenance release: see and manage the space the node uses, plus the foundation for a future activity-track view.
What's new
- Storage management in Settings. The Settings screen now shows how much space the chain database, the node as a whole, the logs and the DePIN records use, with a total for the app's data. A "delete the chain database and resync" action — available only while the node is stopped, behind a confirmation that spells out what is deleted and what is kept — removes only the chain database. The node's network key, the mining settings and rewards inner hash, the DePIN identity and records, the track records, the logs and the app settings are all kept. The node does not restart by itself; the next start syncs from the beginning.
- Daily activity sampling (foundation, no UI yet). The app now keeps a lightweight on-device daily record — uptime, blocks observed, peer counts, mining jobs and mining time, and an approximate hash total. Nothing is displayed yet and nothing leaves the device; a later release will draw the activity track from it.
- Readability and polish fixes. Dialog buttons now always use the app's own wording in the selected language instead of falling back to the device locale; the block number in the notification is digit-grouped; the faintest label color is split so that text meant to be read is lighter than pure decoration; the "how to read this screen" sheet can be dismissed with the back key, its close button or a tap outside; a pending chain-database reset is shown in the Storage section; and the home screen's field and card animations pause while the app is in the background or the node is stopped.
- Two robustness fixes carried over from the v4.0.0 audit's follow-up list: the mining worker cap is now read and published under the same lock, and miner thread startup is isolated from Error-level failures the same way the shutdown path already was.
No new permissions (still five), the bundled node and miner binaries are unchanged from v4.0.0, and no data is migrated.
Verified before release
- An external audit covered the storage, sampling and robustness changes; every verified finding was fixed — including a correction to which database directories the resync action deletes, so it now removes the database the node actually writes.
- On a real device (Pixel 9a / GrapheneOS): an in-place update over v4.0.0 with settings and records preserved; the node synced to the chain tip; mining running with jobs received from the bundled node; the Storage section reporting the node data size; the first daily record written; and a shared diagnostic summary with no warnings or errors.
- JVM suites: 572 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.1.0.apk— 63,458,659 bytes- SHA-256:
e267ad6142b7da29c25da4bd28bc6cdfbf9a2360efa8ae99a0ea553da81d6e32 - Signed with the project's release key (certificate SHA-256
65bb1a5fef27d70be1dd12fc12ce3484b4c848fceca92f8898cd96cb2784f6ff), the same key as every release since v0.1.0. v4.1.0 installs over v4.0.0 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.
v4.0.0 — On-device mining (opt-in)
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-minerv4.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 ofquantus-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.
v3.0.2 — Sync stall hotfix
A hotfix release. The bundled node binary is rebuilt (the first binary change since versionCode 10) to fix a stall that could stop a node permanently on some devices. The app code does not change.
What is fixed
- Nodes could stall permanently on some devices. Reported on a Xiaomi device: the node sat at block 16,038 while the network was at ~402k, peers dropped to zero, and the status still showed "synced". The node's log repeated one error on every block: the Wasm runtime could not be created because its memory pool mapping — a single reservation of 258 GiB of virtual address space (
mmap failed to reserve 0x4082000000 bytes) — was refused by the device. With no runtime, every block verification failed, so the node could never advance again. - The fix. The rebuilt binary creates runtime instances on demand instead of reserving the whole memory pool up front. Nothing about block validation itself changes: the same runtime code verifies every block, only the way its instances are allocated differs. The failure was reproduced on the host under a virtual-memory limit (the unpatched binary aborts with the identical error) and the fixed binary was verified the same way — full startup, genesis, and block production under the limit that kills the unpatched build.
- The misleading "synced" display was a consequence, not a separate bug: with all peers gone the node itself no longer reported syncing. With verification working again, an affected node catches up and the status follows.
The app code, the node launch arguments, the database and the permissions (still five) are unchanged from v3.0.1. The full change list is in CHANGELOG.md.
Download
- quantus-node-v3.0.2.apk — 55,995,644 bytes
- SHA-256:
36791bd99b597b679190fb39b169cb89b81c70857bf630fd5e96859864eff85e - Verify the checksum after downloading, before installing. The APK is signed with the project's release key (certificate SHA-256
65bb1a5fef27d70be1dd12fc12ce3484b4c848fceca92f8898cd96cb2784f6ff) — the same key as every public release since v0.1.0, so it installs over v3.0.1 keeping settings and synced data.
Requirements
- Android 12 or later, arm64 device
- About 3 GB of free storage as a guide (measured 1.30 GB in total after a full sync on the reference device)
- Wi-Fi is strongly recommended for the first sync (about 2 hours on the reference device; a lot of data)
Verified / expected devices
- Verified: Pixel 9a running GrapheneOS — in-place update over v3.0.1, node at the chain tip (#407,635) and importing new blocks, 12 peers, no warnings or errors in the log.
- Expected to work: other Android 12+ arm64 devices, including the Xiaomi model this fix targets; a confirmation on that device is pending with the reporter. Aggressive OEM battery savers (Samsung, Xiaomi, …) may stop the resident service — if the node keeps stopping, exempt the app from battery optimization. Device reports via GitHub Issues are welcome; the verified list grows from them.
Known limitations
- DePIN aggregation is not live yet: recording and proof bundles work entirely on-device, and there is no public aggregation or dashboard listing of records in this release. The record is yours to keep and show.
- The Connection tab visualizes peer count and your own checkpoints; per-peer detail is not available from the node, so the field shows relationships in aggregate, not individual peers.
- Automatic start after a device reboot is not implemented; open the app and tap Start after a reboot.
- Translations (9 languages) have not yet had a native-speaker review.
- A stalled sync on a poor connection may still need a manual Stop → Start if the automatic restart (at most 3 times in 24 hours) does not clear it.
Feedback, device reports, and bug reports are welcome as GitHub Issues. Security issues: see SECURITY.md instead of a public issue.
v3.0.1 — Audit fixes
v3.0.1 — Audit fixes
A maintenance release. It fixes the verified findings of a fourth round of external audit of the v3.0 tree, together with an internal review of the same code. No features change.
What is fixed
- Recording stop reliability. Turning recording off immediately after turning it on could leave recording running while the display showed it off. A pending off is now re-delivered until the recording process confirms it.
- Status figures after an identity change. The status could show the previous identity's checkpoint count and latest time. The remembered figures are now kept per identity.
- Journal capacity edge. A journal filled to exactly the checkpoint maximum could no longer be exported as a proof bundle. The append limit now matches the export and verification limit.
- Proof bundle export. After the home identity had been sent out and erased, exporting a bundle could create a fresh home seed as a side effect. Export now refuses instead of minting one.
- Erased seed residue. Temporary vault files could retain a copy of an erased identity seed; orphaned temporary files are now swept after writes.
- Transfer edge cases. Cancelling a completed attempt could mis-record the restore state and stall recording until the next transfer action; cancelling an attempt with no staging record could crash; and closing a one-shot sender by another path could leave its confirmation key in the vault. All three are fixed.
- Import robustness. The free-space floor is now checked before a transfer plan is adopted, the verified checkpoint count of an imported archive is saved when staging completes, and the import progress display no longer caps at a stale constant below the real journal capacity.
- Failure classification. A decryption failure caused by the Android Keystore was reported as a corrupted transfer code; it is now classified as a keystore problem, with the matching guidance.
- Recording self-stop. An unexpected reply from the local node could make recording stop itself; such replies are now handled as ordinary RPC failures. The DePIN RPC client also no longer follows redirects.
- Price display. A failed background start could leave the QTC price marked as fetching indefinitely; the flag is now released.
- Housekeeping. Launch-record cleanup could delete the supervisor's own window file; orphaned claim markers and stale temporary status files are now swept, and a failing recovery step no longer blocks crash-debris cleanup.
One display item that needs new UI strings in all nine languages is not in this release and is left for a later one.
The node launch arguments, the database and the bundled node binary are unchanged (still the versionCode 10 build). No permission is added (still five). The full change list is in CHANGELOG.md.
Download
- quantus-node-v3.0.1.apk — 55,995,644 bytes
- SHA-256:
3542f338c53ec85e102ff11872a892cf7a8745ef4282b7d284f6ae3838b82715 - Verify the checksum after downloading, before installing. The APK is signed with the project's release key (certificate SHA-256
65bb1a5fef27d70be1dd12fc12ce3484b4c848fceca92f8898cd96cb2784f6ff) — the same key as every public release since v0.1.0, so it installs over v3.0 keeping settings and synced data.
Requirements
- Android 12 or later, arm64 device
- About 3 GB of free storage as a guide (measured 1.30 GB in total after a full sync on the reference device)
- Wi-Fi is strongly recommended for the first sync (about 2 hours on the reference device; a lot of data)
Verified / expected devices
- Verified: Pixel 9a running GrapheneOS (the same code is in place on this device: in-place update, sync completed, recording active, and the exported proof bundle verified end to end at 389 checkpoints).
- Expected to work: other Android 12+ arm64 devices. Not yet verified on them; aggressive OEM battery savers (Samsung, Xiaomi, …) may stop the resident service — if the node keeps stopping, exempt the app from battery optimization. Device reports via GitHub Issues are welcome; the verified list grows from them.
Known limitations
- DePIN aggregation is not live yet: recording and proof bundles work entirely on-device, and there is no public aggregation or dashboard listing of records in this release. The record is yours to keep and show.
- The Connection tab visualizes peer count and your own checkpoints; per-peer detail is not available from the node, so the field shows relationships in aggregate, not individual peers.
- Automatic start after a device reboot is not implemented; open the app and tap Start after a reboot.
- Translations (9 languages) have not yet had a native-speaker review.
- A stalled sync on a poor connection may still need a manual Stop → Start if the automatic restart (at most 3 times in 24 hours) does not clear it.
Feedback, device reports, and bug reports are welcome as GitHub Issues. Security issues: see SECURITY.md instead of a public issue.