There is something satisfying about putting old hardware back to work.
A lot of people have old Android phones laying around with cracked screens, weak batteries, or no real purpose anymore. They may not be powerhouses, but they can still be turned into little worker units. In my case, I wanted a way to get CPU miners running on old cell phones and then manage them from a Windows machine without having to baby each phone one by one.
That is where this setup comes in.
I put together a GitHub repo here:
https://github.com/PaulMoon410/win_mine
That repository is a PowerShell-based starter kit for running miners from Windows through PuTTY plink over SSH. The repo includes a shared config file, a miner template, start/check/kill scripts, and multi-device monitoring scripts. The README specifically lists miner\_common.ps1, bot\_TEMPLATE.ps1, cell\_start.ps1, cell\_check.ps1, cell\_kill.ps1, monitor\_all.ps1, and start\_all.ps1 as the core files in the workflow.
Instead of tapping around on each phone every time I want to start or monitor a miner, I can use one Windows machine as the command center.
My repo is built around that idea:
The repo README calls it a reusable starter kit for running miners from Windows via PowerShell + PuTTY plink, and the included notes say the scripts use SSH on port 8022.
Before using the Windows launcher side, you need a few basics in place on the phones.
For Android, Termux is one of the easiest ways to create a Linux-like command-line environment on the device. You will generally want:
On each Android phone, inside Termux, a typical setup looks like this:
pkg update \&\& pkg upgrade -y
pkg install openssh git clang make -y
passwd
sshd
That gets the phone closer to being reachable over SSH and gives you the basic tools needed to pull code and build software in Termux. The exact miner build can vary depending on whether you are using cpuminer-opt, cpuminer-multi, or another CPU miner source tree.
My repo already assumes certain working directories for the phones configured in miner\_common.ps1.
Right now, the sample config in the repo shows three miner entries:
157 using u0\[email protected] with working directory \~/cpuminer-multi188 using u0\[email protected] with working directory \~/cpuminer-opt189 using u0\[email protected] with working directory \~/cpuminer-optSo the practical part is simple:
In miner\_common.ps1, the default executable is set as:
$Script:MinerExecutable = "./cpuminer"
The same file also sets the sample pool, wallet placeholder, and password argument placeholder.
The first file to edit is:
miner\_common.ps1
That same script currently contains examples like:
PlinkPath = "C:\\Program Files\\PuTTY\\plink.exe"MinerPassword = "CHANGE\_ME"MinerWallet = "CHANGE\_ME\_WALLET"stratum+tcp://yescrypt.na.mine.zpool.ca:6233157, 188, and 189So after downloading the repo, the first job is replacing all the placeholder values with your actual setup.
Old cell phones are not going to compete with real mining hardware. They are small CPU workers. They are more useful for experimentation, learning, testing pools, running low-power background mining, or making use of hardware that would otherwise just collect dust.
The bigger value here, at least to me, is the system itself:
That is the kind of project I enjoy, because it feels like squeezing life out of equipment people already wrote off.
🤖 PeakeBot — Autonomous Trading System (RC-AWARE)
Independent multi-token trading bot featuring:
RC-aware execution, adaptive delay logic, and self-regulating trade cycles.
📊 Trading bot details:
👉 https://geocities.ws/p/e/peakecoin/trading-bot/peakebot_v0_01.html
💻 Open-source repositories:
👉 https://github.com/paulmoon410
For their continued support, guidance, and help expanding the PeakeCoin ecosystem.
