SoloLuck Miner
What it is
SoloLuck Miner is a small Windows app with a Start and a Stop button. It runs cpuminer-opt, an open-source CPU miner, on your PC's processor and points it at SoloLuck, a solo Bitcoin mining pool with a 0% pool fee.
It pays nothing unless your PC finds a block. Nothing is held for you, so there is nothing to withdraw: a block your PC finds pays your own Bitcoin address, in the block itself.
- No account and no email: your Bitcoin address is your username.
- On first start it downloads cpuminer-opt v26.1, the one release this build pins, and checks its SHA-256 before running it.
- It never uses more than 90% of your CPU.
- The source is public: GitHub, or the source zip of this exact build.
Download for Windows
⬇ Download SoloLuckMiner-v1.11.5.exe GitHub release ↗
Version 1.11.5. Before you run it, check that the file you downloaded is the one published here. In PowerShell, in the folder you saved it to:
Get-FileHash .\SoloLuckMiner-v1.11.5.exe -Algorithm SHA256
It must print this SHA-256 (PowerShell shows it in capital letters): d529fa273c781f6934bae5f5d9cf751b51aa4b58d90227d16fd7d18be56893ef. Every download's checksum: SHA256SUMS.txt.
It is signed with GPG: SoloLuckMiner-v1.11.5.exe.asc is the signature, made with SoloLuck's release key (fingerprint 278A 7867 47A2 483C CB13 78DE 6DC0 1CCB 8D86 65FB). With gpg installed:
gpg --import SoloLuck-release-signing.asc gpg --verify SoloLuckMiner-v1.11.5.exe.asc SoloLuckMiner-v1.11.5.exe
It must say “Good signature”.
Linux and macOS
No app here: a short script that finds or builds cpuminer-opt and starts it. Download it, check it, read it, then run it with your own address.
Linux (Debian, Ubuntu and most others):
curl -fLO https://sololuck.io/linux-miner.sh sha256sum linux-miner.sh # expect: ff9575cce08e73ef014260239c6184984a761cf57593ad8c106f3e7cba0fe386 less linux-miner.sh bash linux-miner.sh bc1qyouraddress
macOS:
curl -fLO https://sololuck.io/mac-miner.sh shasum -a 256 mac-miner.sh # expect: 330386edc3763d5ed45d0ff456c2ef509463ca170ba968a1614651d3bcfd56c5 less mac-miner.sh bash mac-miner.sh bc1qyouraddress
Your odds on a PC
At the Bitcoin network difficulty right now, 132,757,073,449,487. The hashrates are examples, not measurements: a PC's real figure depends on its processor and the load you set, and the app shows it once it runs.
| Example hashrate | Average time to a block | Chance in a year |
|---|---|---|
| 10 MH/s | 1,800,000,000 years | 1 in 1,800,000,000 |
| 100 MH/s | 180,000,000 years | 1 in 180,000,000 |
| 1 GH/s | 18,000,000 years | 1 in 18,000,000 |
It pays nothing unless your PC finds a block. Expected earnings are effectively zero; it's a lottery ticket. SoloLuck has not found a Bitcoin block. Every hash is a new draw: nothing builds up, so a PC that has mined for a year has the same chance tomorrow as one that starts today.
Try your own hashrate on the odds calculator.
What it changes in Windows Defender
Many antivirus products flag CPU-mining engines, cpuminer-opt included, as coin miners, and Defender may remove the engine as soon as it lands. So before the engine is written to disk, the app asks for administrator rights (one Windows UAC prompt) and runs these PowerShell commands. They are read from the published source of this build:
Add-MpPreference -ExclusionPath '<engine folder>' Add-MpPreference -ExclusionProcess '<engine folder>\cpuminer-*.exe' MpCmdRun.exe -Restore -Path '<engine folder>'
- The first line tells Defender to skip that folder. The second skips cpuminer programs started from it. The third restores anything Defender already quarantined from that folder.
<engine folder>is theSoloLuckMiner-enginefolder next to the app. If the app cannot write there, it uses%LOCALAPPDATA%\SoloLuckMiner-engine, then%TEMP%\SoloLuckMiner-engine.- Real-time protection stays on for everything else. If you say no to the prompt, nothing is changed, and Defender may then remove the engine.
- Both rules stay until you remove them. Deleting the app does not remove them.
- The app's shield indicator looks only for the folder rule, and its text says only this folder is excluded. It never shows whether the process rule is there, and it cannot remove either rule.
To remove both, open PowerShell as administrator and run:
Remove-MpPreference -ExclusionPath '<engine folder>' Remove-MpPreference -ExclusionProcess '<engine folder>\cpuminer-*.exe'
To see the exact paths first: Get-MpPreference | Select-Object ExclusionPath, ExclusionProcess. Both rules are also listed in Windows Security, under Virus & threat protection → Manage settings → Exclusions.