Is SoloLuck better than solo.ckpool.org?

Not in the way that decides your payout. The odds of solving a block are identical on both — same true-solo model, same 2% on-win fee, same on-chain payout. SoloLuck is better only on the things a pool can actually change for a SEA miner: a ~6 ms Jakarta node instead of ckpool's nearest AU/US server, a TLS port, ten languages and a richer dashboard. ckpool is better on track record. Pick by what you value.

Why would I leave ckpool if my luck is the same either way?

Only for the differences a pool can control: latency, encryption, language and polish. If you're in Southeast Asia, a node ~6 ms away submits your shares faster than one across an ocean, so fewer go stale. If none of that moves you, there's no reason to switch — ckpool is a fine pool and the odds won't improve by moving.

Does SoloLuck run the same software as ckpool?

Yes. SoloLuck runs ckpool in solo mode (ckpool -B) — the same open-source GPLv3 software Con Kolivas wrote and runs at solo.ckpool.org. We didn't reinvent the engine; we put it on a node close to Asia, added TLS, ten languages and a fuller dashboard.

How many blocks has SoloLuck found compared to ckpool?

None yet. ckpool has a long public record of solved blocks built over years; SoloLuck has zero, and most of its current hashrate is the operator's own test rigs. We say so plainly. It matters for trusting the plumbing, but it does not change your odds on the next block — that's set by your hashrate against the network, identically on every solo pool.

Does ckpool offer a TLS (encrypted) connection?

No — ckpool is plain stratum only. SoloLuck offers an optional TLS port at :3334 on stratum.sololuck.io, which is worth using over untrusted networks like public Wi-Fi. The rest of the tiered ports (:3335 Nano, :3333 Lite, :8081 Standard, :4334 Pro) are standard stratum.

SoloLuck

ckpool Alternative for Asian Solo Miners

← back to pool

ckpool vs SoloLuck, the honest version

If you've solo mined for any length of time, you've used solo.ckpool.org — Con Kolivas' pool, running the very ckpool -B software the whole solo world is built on, including ours. It is the incumbent for a reason, and we're not going to pretend otherwise.

So here's the only honest pitch: the odds are identical. ckpool and SoloLuck both mine true solo, both take 2% only on a block you actually solve, both pay straight to your address on-chain. A pool cannot change your luck — it can only change the fee, the payout style and the latency. The case for switching is narrow and specific: you're in Asia, you'd like a node next door, a TLS port and a dashboard in your own language — and you're willing to mine on a pool that hasn't proven itself with a block yet. If that's not you, ckpool is a perfectly good home.

What solo.ckpool.org gets right

Credit where it's due. ckpool is the standard everyone else is measured against, and most of that reputation is earned:

A real track record. Years of continuous operation and a long public list of solved blocks — the one thing a brand-new pool simply cannot fake.
The reference software. ckpool — written by the operator himself — is the solo mining stack, released open-source under GPLv3. SoloLuck runs the same ckpool -B; we didn't reinvent the engine, we relocated it.
Multiple nodes. Servers in Australia and the US, so much of the world has something within reach.
0% the rest of the time, 2% on a win. Same flat, on-block fee model we use. No hidden deductions.
Battle-tested and boring. It just works, it has for many years, and there's a calm comfort in that.

None of the points below are an argument that ckpool is bad. They're an argument about where you live.

Where SoloLuck is different — the SEA case

SoloLuck exists for one reason: a single node in Jakarta, built for Southeast Asia first instead of last.

Latency, measured. Our node sits roughly 6 ms from much of Indonesia and SEA, versus ~250 ms to a US pool. ckpool's region select helps — but its nearest node for most of SEA is still Australia, further than a host in your own region. Closer means fewer stale shares and less wasted work. See /compare for the round-trip numbers from your own browser.
TLS, if you want it. Port :3334 encrypts the stratum link. ckpool is plain stratum only — fine on a trusted network, less so over hotel or café Wi-Fi.
Ten languages. The whole site — setup, stats, fee, rules — in en/id/ms/ja/th/ko/zh/vi/tl/hi. ckpool is English-only and famously spartan.
A richer dashboard. Live per-address stats, an honest odds calculator, a verify page, and an Ask bot for setup questions — instead of ckpool's deliberately minimal table.
One host, tiered ports. Everything lives on stratum.sololuck.io; you pick the port for your gear rather than juggling region-specific URLs.

Side by side

Trait	solo.ckpool.org	SoloLuck
Mining model	True solo (`ckpool -B`)	True solo (same `ckpool -B`)
Fee	2%, only on a solved block	2%, only on a solved block
Custody	Non-custodial, paid on-chain	Non-custodial, paid on-chain
Nodes	AU / US, manual select	One Jakarta node, ~6 ms to SEA
TLS	No	Yes (`:3334`)
Languages	English only	10 languages
Dashboard	Spartan, functional	Stats, calculator, Ask bot
Software	ckpool, GPLv3 (the original)	Same ckpool, relocated
Track record	Long public block history	None yet — be aware

Notice the top half is a tie. The model, the fee and the custody are the same because it's the same software — the only honest differences are distance, polish and history.

The one thing ckpool has that we don't: a track record

Full disclosure, because the brand depends on it: no block has been solved on SoloLuck yet, and most of the hashrate pointed at us so far is the operator's own test rigs. ckpool has a long public record of solved blocks and many years of uptime. We have a fast node and a promise. That gap is real and we'll keep saying so until a block closes it.

Here's why it matters less than it sounds, though. Solo mining is a lottery, and a pool's past blocks don't improve your odds on the next one — your luck is set entirely by your hashrate against the network, identically on every solo pool. A track record tells you the pool reliably builds valid templates and pays out correctly when someone wins; it does not mean you're more likely to win there. For the lottery framing in full, see solo vs pooled mining.

What a track record does buy is trust that the plumbing works — so verify ours instead of taking our word for it. Everything we claim is checkable on /verify: the live block template, the chain tip, the fact that you mine to your own address.

Should you switch? How to point your miner

Switch if you're in SEA and want a node next door, a TLS option and a dashboard you can read — and you're comfortable being early. Stay on ckpool if its track record is what lets you sleep, or if you're closer to its AU/US nodes than to Jakarta. Both are honest answers. There's no wrong choice here, only the wrong reason.

Moving over takes one line — same as any ckpool setup. Point your miner at stratum.sololuck.io, use your bc1 address as the username, and any password. Pick the port for your gear:

:3335 Nano — difficulty 1, for NerdMiner / tiny ESP32 / sub-100 GH devices
:3333 Lite — Bitaxe class
:8081 Standard
:4334 Pro — S19 and other high-hashrate gear
:3334 TLS — encrypted stratum

Copy a ready-made config from /setup, run the numbers for your hashrate on the odds calculator, and compare the latency yourself on /compare. There's a community on Telegram at @SoloLuckPool if you get stuck.

Ready to take a ticket?

Paste your address and copy the config from /setup, watch the pool on /status, and check every claim on /verify. Mine to your own address — that is what makes it truly solo.

Get the setup config →

Not ready to point a miner yet? Run your gear through the odds calculator, or join Telegram for block & record alerts — no rig required.

More guides

Browse all guides →