XTM-Miner

Independent Android CPU miner for Tari (XTM), in active development. This repository is not yet a validated miner or APK: physical-device behavior and live accepted shares remain unverified.

Selected mining route

The first implementation targets Tari's standalone Tari RandomX (RxT / XTM-RX) route through a pool that explicitly accepts XMRig Stratum submissions. This is distinct from Monero RandomX merge mining (RxM). The selected Kryptex XTM-RX setup documents algorithm rx/0, endpoint xtm-rx.kryptex.network:7038 over TCP SSL, and login TARI_WALLET/WORKER. Pool fees, payout thresholds and endpoints may change; confirm current terms on the operator's pages before use. The route does not use a Monero wallet or local Tari merge-mining proxy. See docs/COMPATIBILITY.md.

ARM64 Termux source milestone

The current deliverable builds upstream XMRig v6.26.0 (b2ca72480c58d197e18c885d9fc1a0c8d517e60a) from the checksum-pinned source archive in vendor/. The project applies a narrow patch to require Stratum TLS certificate-chain and hostname verification. The native Termux build requires an ARM64 Android device with Termux; it does not download executable source during the build.

After Gate 1 in PHONE-TESTING.md is reviewed, install Termux packages and build from the project directory:

pkg update
pkg install cmake ninja clang make openssl libuv ca-certificates python patch coreutils tar unzip
./scripts/build-termux.sh
./scripts/test-termux.sh

The build defaults to one compile job to reduce memory pressure. Set BUILD_JOBS=2 only if the phone has adequate available memory. The test script checks the source checksum, dependencies, engine version/help, and launcher behavior with a mock. ./scripts/test-termux.sh --tls-local additionally runs local synthetic-certificate checks and requires Termux's optional openssl-tool command-line package; ordinary smoke checks do not require it. ./scripts/test-native-launcher.sh then exercises the real native launcher against an unreachable loopback-only endpoint with a fake address, testing explicit start, duplicate locking, bounded TERM stop, and child/lock cleanup without contacting a public pool. The phone guide separately tests manual foreground Ctrl-C. None of these tests proves hashing. Follow the phone guide gate by gate. Do not skip ahead to pool testing.

The launcher requires both a public Tari receiving address and an explicit --start. It defaults to one mining thread, RandomX light mode, verified TLS, no huge pages, and XMRig's upstream 1% developer donation. An atomic lock at $PREFIX/var/lib/xtm-miner/miner.lock refuses simultaneous XTM-Miner sessions across separate project copies in the same Termux installation. The launcher uses a private temporary config and forwards stop signals to the child miner. Light mode requires at least 512 MiB of system-reported MemAvailable; opt-in fast mode requires 3 GiB. These are conservative preflight heuristics, not Android per-process memory limits or device-safety guarantees. The wrapper adds no project fee and makes no profitability claim.

Validation status

• Tari RxT/XTM-RX route, pool instructions, XMRig revision, and TLS patch rationale are documented in docs/COMPATIBILITY.md.
• The pinned patched engine previously built on x86_64 Linux; local synthetic TLS tests accepted a trusted matching hostname and rejected an untrusted CA and a hostname mismatch. This is host testing only.
• The updated launcher mock test passed in the Sandbox for explicit-start gating, config contents and permissions, fail-closed CA handling, cleanup, duplicate-session refusal, SIGINT/TERM forwarding, and no orphan mock process.
• User-provided output confirms a successful XMRig 6.26.0 ARM64 Termux build on a Pixel 9a running Android 17/API 37. Corrected ordinary and optional local-TLS smoke tests passed there: trusted matching local TLS was accepted while wrong-host and untrusted certificates were rejected. The real launcher also passed a no-pool loopback test for explicit start, duplicate prevention, TERM stop, native-child reaping, and lock cleanup. Both a real-launcher Ctrl-C attempt and a no-miner signal probe restarted the Google Play Termux session; the probe confirmed SIGINT reached its foreground script and the post-restart check found no miner process or lock. The root cause is unknown, so this build uses a separately invoked, pidfd-bound TERM stop helper instead of Ctrl-C. Google Play Termux reports Android linker64 through /proc/PID/exe, so the helper permits that case only with an exact executable mapping of this project binary. The updated helper physically stopped real loopback XMRig, released the lock, returned the first session to its shell, and the independent process-list check found no miner-like process. Public-pool, actual hashing, and accepted-share tests remain pending.
• No production pool connection, authenticated worker, actual RandomX pool job, or accepted share has been tested.
• No Android cross-build or emulator test was available in the Sandbox. The user's phone is not attached as an execution environment, and no SDK/NDK, adb, or emulator is available here; details are in docs/ANDROID-TERMUX-TOOLCHAIN.md.
• No standalone APK/JNI integration, thermal/battery behavior, Android lifecycle handling, or physical Stop test exists yet.

A build or pool login alone is not accepted-share evidence. See docs/TEST-REPORT.md and DECISIONS.md for exact evidence and next steps.