Changelog

2026-10-03 — SoloLuck's second Bitcoin pool, in Phoenix, USA, is retired. us.stratum.sololuck.io now reaches the Jakarta pool, so a miner pointed there keeps mining without changing anything, and the Connect page and the Ping Race no longer offer Phoenix. SoloLuck's Bitcoin mining runs in one pool again, in Jakarta, with the Singapore door forwarding into it.
2026-09-17 — Windows miner v1.11.5, with the same fix in the Linux and macOS miner scripts: Bitcoin Cash now works on a PC. The Bitcoin Cash pool has one port for every size of machine and starts each connection at share difficulty 1,024. At a PC’s speed that is hours per share, and the pool only lowers a difficulty once it has seen shares — so a PC could mine for hours without a single share reaching the pool, and its logbook stayed empty. The app and both scripts now ask the pool for its lowest difficulty when they connect, so a PC’s shares show up within minutes. Also fixed in the Windows app: the Accepted count went up by one every five minutes, because it counted the mining engine’s periodic summary as a share, so it could report accepted shares when none had been sent. It now counts only the pool’s own verdicts, and the hashrate readout shows the hashes the engine actually counted instead of switching to an estimate from shares every five minutes. Your odds of finding a block are unchanged: they depend on your hashrate, not on share difficulty. Existing installs pick the update up the next time the app starts.
2026-09-11 — Correction: several DigiByte lines said each block paid “a single coinbase output” to “the address that solved it”, and one tile was labelled “Paid to miners”. A coinbase has one spendable output plus a zero-value segwit commitment, and all six DigiByte blocks so far were mined by machines the pool operator runs — they show how the software pays a block, not that an outside miner has been paid. /blocks, /proof, /dgb and llms.txt now say so. SoloLuck has not found a Bitcoin block.
2026-09-11 — The Singapore entry point is back. sg.stratum.sololuck.io leads to the Singapore machine again, which carries a miner into the Jakarta pool over a private encrypted link, and it is listed on /connect and in the Ping Race once more. What prompted its retirement earlier today is still true: that machine's own route into Jakarta is slow at the moment, so for most miners coming in through Singapore is a longer path than connecting to Jakarta directly. For solo mining that costs a few stale shares at most, never odds — a found block is still sent to the network from Jakarta — so it stays a choice. Measure your own round trip on the Ping page and choose with the number in front of you.
2026-09-11 — CORRECTION, added 2026-09-11: reversed the same day — the Singapore entry point is back; see the entry above. As published earlier on 2026-09-11: The Singapore entry point is retired. It was a relay: a miner connecting to sg.stratum.sololuck.io was carried into the Jakarta pool, and that detour turned out to be slower than connecting to Jakarta directly. The name now points straight at the Jakarta pool, so anyone still using it keeps mining with nothing to change — just a shorter path. SoloLuck's Bitcoin mining still runs in two pools, Jakarta and Phoenix, neither of which forwards to the other; the Ping Race now times those two, and every door still carries the same four tiers.
2026-09-10 — Windows miner v1.11.4. If the pool you are mining to stops answering, the app now moves you to the other one instead of retrying a dead address forever. It waits a full 90 seconds first, so a brief blip never moves anyone, and it checks that the other pool is actually answering before it goes — moving to a second dead pool would help nobody. It tells you what happened and why, in those words. Bitcoin only: Bitcoin Cash has one pool, so there is nothing to move to. Until now the app picked the nearer pool when it started and never looked again, which meant a pool going down mid-session left you reconnecting to it indefinitely while quietly earning nothing.
2026-09-10 — Windows miner v1.11.3. SoloLuck runs two Bitcoin pools — the Asia pool and the US pool — and until now the app only knew the first, so anyone mining from the Americas or Europe crossed the Pacific to submit every share. This build measures both when it starts: it opens a connection to each, times the handshake three times, and asks each one to subscribe so it can tell a live pool from a port that merely accepts connections. It then mines to whichever answered quicker and prints both numbers, so you can see why it chose. There is nothing to configure and nothing to lose if the check fails — a name that will not resolve, a pool that will not answer, or a check that has not finished when you press Start all fall back to the endpoint every earlier version used. Your statistics page is unaffected either way: /users/ reads both pools, so the one you land on does not change where your hashrate shows up. Bitcoin Cash is untouched — it has one pool, so there is nothing to choose. Run SoloLuckMiner.exe --pools to see the measurement on its own; it writes the result to a text file beside the app.
2026-09-06 — SoloLuck's Bitcoin mining now runs in more than one pool — today one in Jakarta and one in Phoenix, USA — each with its own Bitcoin node building its own block templates. Two pools split nothing: in solo mining nobody shares work, so each pool is an independent search and a solved block pays whoever found it the entire reward. Your odds are what they always were — your hashrate against the whole Bitcoin network, at either one. Both machines write the same coinbase signature, so a block from either is credited to SoloLuck on-chain and the pool directories still list it once. You do not have to choose anything: stratum.sololuck.io is the address on every guide and it is not going anywhere — and where a page can time your connection, it now hands you the nearer of the two instead.
2026-09-06 — Bitcoin Cash solo mining is open. The same true-solo terms as Bitcoin: 0% fee, the whole block reward paid straight to the address you mine with, nothing held back and no account to open. The same SHA-256 hardware works unchanged — no new firmware and no new chip, just a Bitcoin Cash address and a different port. Bitcoin Cash's network is far smaller than Bitcoin's, so the same machine has far shorter odds of finding a block there; the arithmetic is on the Bitcoin Cash page with both numbers shown.
2026-09-06 — DigiByte solo mining is open. The page shipped earlier today with no pool behind it — the node was still downloading the chain, and it said so in those words rather than showing zeros that could be mistaken for a measurement — and the pool came up the same day. Within hours of opening it had solved two blocks, 24,162,973 and 24,162,854, each paying the whole reward in a single spendable coinbase output to the address that solved it — the only other output is the zero-value segwit commitment every block carries. Open those heights on any DigiByte explorer and read the coinbase for yourself. SoloLuck mines the SHA256d lane, one of DigiByte's five algorithms, so the same SHA-256 hardware works unchanged — and roughly one block in five is one your machine can compete for. The doors are digibyte.sololuck.io on 3341, 3340 and 4340.
2026-09-06 — Windows miner v1.11.1. One app with a coin selector instead of a separate download per chain: pick Bitcoin or Bitcoin Cash, paste that chain's own address, and the app fills in the right host and port for you — the wrong-chain mistake it used to be possible to make by hand is now hard to make at all. DigiByte is built into the same app but is switched OFF in this release and draws no button; it is enabled in a later build rather than shipped as a door that might not open. Downloads stay versioned and the SHA-256 to check is on the Verify page, which now takes the filename from the same place as the hash so the two cannot disagree — they had.
2026-09-06 — The Standard tier (:8081) has been retired, and every entry point now offers the same four doors: Nano (:3335), Lite (:3333), Pro (:4334) and the encrypted tier (:3334). :8081 was never a mining port by design — it is an HTTP-alternate port the pool used because it happened to be open — and one miner was on it. Connections to :8081 are forwarded to Lite automatically, so no configuration had to change and nobody was disconnected.
2026-09-06 — Fixed before anyone could see it: the first block SoloLuck finds would have been listed several times over. ckpool writes up to four log lines when a block is solved, only one of which runs once per block, and the site counted the whole family — so a single block would have been reported as six on the dashboard, the status page and the public API. Blocks are now identified by height and hash rather than by log text. SoloLuck had not found a Bitcoin block at that point, so nothing that was ever displayed was wrong; the first one would have been.
2026-09-06 — The optional pool comparison on the home page used a probe that could not tell a refused connection from a fast one, so a pool that blocked the check could be reported as quick — and SoloLuck could be shown fastest because a rival failed rather than because we were quicker. Both sides are now measured the same way, a failure reads as a failure, and nothing is called fastest unless another pool actually answered.
2026-09-06 — The setup page now names the chain when it refuses an address. A Bitcoin Cash address pasted into the Bitcoin wizard used to be rejected with a list of Bitcoin formats and no mention of Bitcoin Cash. It also says plainly that a 1… or 3… address is written identically on both chains and that nothing anywhere can tell them apart — the same key controls it on both, so a block would still be yours to spend, but the hardware would have spent its time in a different search at different odds.
2026-09-06 — Correction on every port description: the pool's difficulty adjustment follows your share rate up and down, and the pages said it only ever went up. A miner whose hashrate drops — a rig switched off, or one throttling in the heat — was told their difficulty would stay high and their shares would dry up. It comes back down to meet them, never below the floor of the port they used.
2026-09-06 — Accessibility on the setup and connect pages: every copy button now says what it copies rather than just “copy”, the address field has a proper label, validation messages are announced by screen readers, and the ports table stacks on a phone instead of scrolling sideways.
2026-09-06 — Positioning: SoloLuck is a solo pool open to miners anywhere, and the site no longer presents itself as a Southeast Asian one. Copy that framed the pool regionally has been rewritten on the server-rendered pages — the dated guides keep the wording they were published with, and Jakarta is genuinely in Southeast Asia — and the homepage latency line no longer names a city — whether SoloLuck is your shortest hop depends on where you sit, so the page tells you to measure it rather than telling you the answer. Jakarta is still stated plainly wherever it is a fact: the pool node runs there, the operator is there, that is the single vantage the uptime figure is measured from, and it is the measurement point for the latency tables.
2026-09-06 — CORRECTION, added 2026-09-10: this entry is superseded in part and is kept here as first published rather than rewritten. Since 2026-09-07 SoloLuck's Bitcoin mining runs in two pools — one in Jakarta and one in Phoenix, USA — each with its own Bitcoin node building its own block templates, so the sentences below saying there is exactly one pool no longer hold. Two is the count of the Bitcoin pools; Bitcoin Cash and DigiByte have their own. Singapore is unchanged: still a forwarder into the Jakarta pool over a private encrypted link, and not a pool. The Standard tier (:8081) named below was retired on 2026-09-06 and must never be given to a miner; every door now carries the same four tiers — Nano (:3335), Lite (:3333), Pro (:4334) and TLS (:3334). As published on 2026-09-06: Three named entry points, documented. The pool answers on three named doors — Jakarta (sea.stratum.sololuck.io), Singapore (sg.stratum.sololuck.io) and Phoenix (us.stratum.sololuck.io) — and /connect now lists each one with the tiers it carries. There is still exactly one SoloLuck pool and it runs in Jakarta: Singapore and Phoenix are forwarders that carry a miner into that same pool over a private encrypted link, so it is the same work, the same block templates and the same reward paid straight to your own address. Neither is a second pool and no mining happens at either one. [Superseded 2026-09-07: Phoenix became a second SoloLuck Bitcoin pool that day, with its own Bitcoin node building its own block templates. Singapore is still a forwarder and still not a pool.] The certificate was extended so the Jakarta machine verifies under both stratum.sololuck.io and sea.stratum.sololuck.io and that door carries every tier, TLS (:3334) and Standard (:8081) included; the two forwarders carry Nano (:3335), Lite (:3333), Pro (:4334) and — since a second certificate covering the stratum names was issued later the same evening — the encrypted tier (:3334) as well, so every door serves encrypted mining and a TLS connection to a forwarder verifies that forwarder's own hostname. Standard (:8081) stays on the pool's own two names, because ckpool binds that port on the pool machine's own public address. [Superseded: the Standard tier was retired on 2026-09-06 — see the separate entry for that date — so every mention of :8081 in this entry is historical. It must never be given to a miner; the four tiers now are Nano (:3335), Lite (:3333), Pro (:4334) and TLS (:3334).] You still do not have to choose anything — stratum.sololuck.io is the address every guide prints and it is not going anywhere.
2026-09-06 — Ping Race now times SoloLuck's own doors as well as the other pools, from your own browser, and tells three states apart: a real reading in milliseconds, a probe that was tried and did not answer, and a door a browser has no way to reach at all. All three SoloLuck doors now report a real reading. The other two states are not decoration: until this evening the Singapore and Phoenix boxes accepted mining connections only, so a browser had nothing to time and the page said so rather than guessing; both now answer a probe as well. A door that is tried and fails still shows as failed rather than as a number, which is the point — a broken endpoint that reported a fast time would be recommended as the best one.
2026-09-06 — Certificate renewal moved to DNS-based validation. Renewal no longer depends on a challenge served over port 80, so it cannot fail because of what the web port is or is not doing.
2026-09-06 — Fixed on /status: the Standard tier (:8081) was reported offline while it was serving miners. The tier health check connected over loopback only and ckpool binds that port on the public address only, so the check failed on a port that was working. A tier now counts as up if either route accepts, which is what a miner actually experiences. Mining on :8081 was never affected — only the status display was wrong.
2026-08-29 — Uppercase addresses now map to one account — if you enter your bech32 address in capitals (BC1Q…), the pool treats it as the same account as the lowercase form, so your shares and hashrate no longer split across two.
2026-08-29 — The Setup page now checks your Bitcoin payout address with real checksums as you type (base58check and bech32/bech32m) and accepts an all-uppercase bech32 address, so a mistyped address is caught before you mine.
2026-08-29 — Reliability: a block the pool finds is now saved to a local file and submitted to every configured Bitcoin node — the Jakarta pool node and the operator's fallback node — so a node hiccup at the moment of a win cannot lose it.
2026-08-29 — Per-address hashrate charts no longer show a false spike from a single lucky share, so your history reads truer.
2026-08-29 — Faster page loads — the website now serves over HTTP/2.
2026-08-20 — Pool's mining engine upgraded to ckpool v1.2.0 — upstream's last minor release before Stratum V2 support. The upstream changes that actually reach this pool are hardening against malformed responses from the Bitcoin node, mining notifications sharded across threads for faster delivery, and dynamic coinbase sizing. Most of the rest of v1.2.0 is a new IPC path to the node, which this pool does not use — we stay on the ZMQ/RPC path, so those fixes do not apply here. SoloLuck's local patches — the per-port difficulty tiers, per-miner reject accounting, and the 0% fee payout configuration — were rebased onto it and preserved. The 0% fee and non-custodial payout are unchanged: block rewards still pay straight to the miner's own address. Also raised the pool's maximum simultaneous client limit from 250 to 1000.
2026-07-22 — Miner alerts on Telegram — the @SoloLuckIOMining_bot /watch command now also sends worker-down alerts (20 minutes of silence, plus a ping the moment the worker returns) and personal best-share milestones, on top of the existing block-solved notification. Free for every address mining on the pool.
2026-07-20 — Singapore entry point launched — sg.stratum.sololuck.io. A second connection point in Singapore that forwards every miner to the same Jakarta pool over a private encrypted link: same work, same rewards, nothing new to trust. Often a shorter first hop from Malaysia, Singapore and the Philippines; from Indonesia stay on stratum.sololuck.io (Jakarta is closer). Ports: Nano :3335, Lite :3333, Pro :4334 — the TLS tier (:3334) and the Standard tier (:8081) stay on the Jakarta hostname.
2026-07-13 — Fallback-node ckpool refreshed to the latest upstream build. Both nodes — the Jakarta pool node and the operator's fallback node — now check for Bitcoin Core and ckpool updates automatically every night: downloads are signature-verified before anything is installed, a health check must pass after the swap, and any failure rolls back to the previous version on its own.
2026-07-13 — Bitcoin Core upgraded 31.0 → 31.1 on the pool node — official binaries from bitcoincore.org, SHA-256 and GPG signatures verified before the swap, about ten seconds of node downtime with the stratum endpoints staying up. The operator's fallback node was brought to the same version.
2026-07-10 — Windows CPU miner v1.10.1: runs without turning off antivirus. You do NOT need to disable Windows real-time protection — on first run, BEFORE the engine is written to disk, the app adds a Windows Defender exclusion for just its own engine folder (one admin prompt) so the fast engine is never quarantined; real-time protection stays fully on for everything else. If antivirus had already dropped you to the slow SSE2 build, it now re-fetches the fast engine into the shielded folder automatically.
2026-07-10 — Windows CPU miner v1.8.0: CPU load is now hard-capped at 90% (the last few threads add very little hashrate for a lot of extra heat, and full load can make the PC unresponsive) — the old 100% option is gone and old settings migrate to the cap. New one-click ‘Shield it’ adds a Windows Defender exclusion for the mining-engine folder: if antivirus quarantines the fast AVX-512/AVX2 engine the app silently falls back to the slow baseline build (an ~8-10× hashrate loss), so shielding keeps you on the fast engine. Per-CPU engine auto-select is unchanged.
2026-07-10 — Windows CPU miner v1.7.0: the ‘Use 100% of the CPU’ full-load option is now reliable — ticking it always mines at full power (an earlier build could reload a saved full-load setting as 80% even with the box checked). Full load is now presented as a legitimate choice — best hashrate, and fine for a stress-test/burn-in — rather than only a warning. Added a ‘Check for updates’ link in the footer, next to the version, so you can check for a new release on demand.
2026-07-10 — Windows CPU miner v1.6.0: fixed a bug where ticking ‘Allow 100% CPU’ could leave the miner running at 80%; ticking it now uses full power. Updates are now installed automatically — the app downloads and SHA-256-verifies a new version in the background and applies it the moment you are not mining (mining is never interrupted).
2026-07-10 — Windows CPU miner v1.5.0: the app now auto-detects and shows your CPU (model, cores/threads and the exact cpuminer instruction path it will use — e.g. AVX-512+SHA on modern AMD, AVX2+SHA on 12th-gen Intel), a live per-core load meter so you can see which cores are mining, a green ‘recommended’ marker on the CPU-load slider, and a built-in auto-updater that checks for new versions and installs them only after verifying the download’s SHA-256 against the site.
2026-07-10 — Windows CPU miner v1.4.0: the app now verifies your Bitcoin payout address with real checksums as you type (base58check and bech32/bech32m — a typo is caught before mining ever starts, because on a solo pool a mistyped address means an unclaimable block). Pool endpoint fixed to sololuck.io:3335; CPU load is a slider starting gentle at 25% of your cores (100% is opt-in with an honest slowdown warning); every engine file is verified against a pinned SHA-256 manifest before anything runs; honest connection status; plain-word crash explanations with an automatic baseline retry on older CPUs. Downloads are now versioned, with old URLs redirecting, and the app links here from a 'What's new' footer. Older versions are no longer offered here; the current version is on /setup.
2026-07-02 — English-only interface: the language selector was removed and old ?lang= URLs now 301-redirect to their English pages. Navigation dropdowns rebuilt: one menu open at a time, keyboard and screen-reader accessible.
2026-07-02 — Accuracy audit: coinbase-maturity FAQ everywhere, precise coinbase-output wording, labelled operator fleet with an operator/community split, operator-run-monitor wording with one start date, live checksum manifest (/SHA256SUMS.txt), security.txt, full terms and privacy policies, safer Mac install flow, RFC 3339 UTC API timestamps. Also: light/dark theme toggle, comparison-page fee accuracy.
2026-07-01 — Moved to a true 0% pool fee — finders keepers (previously 2%).
2026-06-22 — Encrypted TLS stratum endpoint (port 3334); live template proof; connect-kit with QR.
2026-06-20 — Ten-language site; live pool-hashrate chart; solo-odds calculator.
2026-06-19 — Three difficulty tiers; ckpool upgraded to v1.1.1.
2026-06-18 — Public launch — true per-miner solo (-B) with a public stats page.

Public-facing changes only; dates are approximate.