Connect Miner

🔌Connect — pick the port that matches your gear.

The port sets your minimum share difficulty, and it is a floor: nothing goes below it. Every connection starts at 4,000 (or that floor, if it is higher), and the pool's vardiff then follows your share rate in both directions — up when shares come in fast, back down when they slow, never past the floor. Your miner can ask for a lower difficulty itself too (mining.suggest_difficulty), again no lower than the floor — NerdMiner-class firmware asks automatically. Pick the tier whose minimum is at or below your hardware, never above it.

Where the Bitcoin pools answer from

You do not need to choose anything. stratum.sololuck.io is the address for every miner, everywhere — it is what the wizard hands you, what every guide prints, and the only address your rig needs. This card is here so you can see the whole of the infrastructure, not so you have to operate it.

SoloLuck's Bitcoin mining runs in one pool, in Jakarta, on its own Bitcoin node: it builds its own block templates and pays a block it solves straight to the miner who solved it. Singapore is not a pool — it is a forwarder, and a miner who connects there is carried into the Jakarta pool over a private encrypted link. us.stratum.sololuck.io reaches the Jakarta pool too: a second pool ran in Phoenix, USA from 2026-09-07 and was retired on 2026-10-03, and miners pointed there carried on without changing anything.

One name, one signature. The pool writes the coinbase signature /sololuck.io/ into every block template it builds, so a block solved here is credited to SoloLuck by the block explorers that read that tag.

• Jakarta · Southeast Asia
  sea.stratum.sololuck.io — a SoloLuck Bitcoin pool, and the one every connect string points at
  Carries: :3335 Nano, :3333 Lite, :4334 Pro, :3334 TLS.
• Singapore · Asia
  sg.stratum.sololuck.io — forwards into the Jakarta pool over a private encrypted link
  Carries: :3335 Nano, :3333 Lite, :4334 Pro, :3334 TLS.

Jakarta answers to two names. stratum.sololuck.io is the canonical one: the address on every connect string we publish, and it is not going anywhere. sea.stratum.sololuck.io names that same Jakarta machine directly, under the same naming scheme as sg; us reaches this machine too. It carries every tier, the encrypted one (:3334) included, and the certificate carries both hostnames, so an encrypted connection verifies under either name. Since 2026-09-06 a second certificate covers the Singapore name as well, so :3334 verifies at Singapore too — every door here serves encrypted mining. Every door carries the same four tiers.

What none of this changes: your odds. Latency is not odds — every hash has exactly the same chance of solving a block whichever door it came in through, and whichever pool it reached. A nearer door is a shorter first hop, which usually means a steadier connection and fewer dropouts on a slow or fidgety line. That is the whole of it.

Check it for yourself. We publish no ping figure for any of these doors, and where a figure does appear elsewhere on this site it is dated and names the vantage it was measured from — a route can quietly get slower with nothing changing on our side, and an undated number would go stale without warning. Every door above accepts a plain TCP connection on the ports in its row, so time one from the machine your miner actually runs on — that measures your connection rather than ours. Time a connection rather than a ping: some of these hosts sit behind filtered ICMP and will not answer one.

Which door is nearest you?

The list above is deliberately free of ping figures, because a number we print here rots the moment a route changes — and one of the doors below did exactly that. It was commissioned on a short hop into Jakarta and is several times slower today; it answered every check throughout, so nothing raised a hand. A rule written down once about who should use which door goes stale the same way, and just as quietly. A reading taken in your own browser cannot. So measure it yourself: this times each entry point from your own browser, right now, over an ordinary web request, and names the nearest. It is a distance hint rather than a Stratum benchmark, and what it changes is the length of your first hop — every door reaches a SoloLuck Bitcoin pool, and every hash has the same chance of solving a block whichever door it came in through and whichever pool it reached.

Measure again

Nothing is sent to us: the timings are taken and read entirely in your browser and never leave it. A door that answers miners but not web requests cannot be timed this way at all and is listed with no number rather than a guess, and a probe that fails is shown as no answer rather than as a fast one. Run it on the network your miner actually sits on — a laptop on a different line will give you a different answer.

Renting hashrate for a solo attempt (Braiins Hashpower)

SoloLuck passes the Braiins Hashpower pool check (opens in a new tab): every port answers mining.subscribe with an extranonce2_size of 8 (they require 7 or more), and a username that is not a Bitcoin address is rejected at mining.authorize instead of being silently accepted. When you create a spot bid or a contract there, enter:

• Mining pool URL: stratum+tcp://stratum.sololuck.io:4334 — the Pro tier. Its starting difficulty of 1,048,576 suits a delivery of 1 PH/s (their minimum bid) and above, so the connection runs at a sane share rate from the first second; vardiff raises it further as needed.
• Worker identity: your own Bitcoin address, optionally with a worker suffix, for example bc1q….braiins. A block found by the rented hashrate pays that address in full, exactly like a block from your own hardware.

Their “Try Your Luck” solo package is fixed to Braiins Solo, so use a custom pool URL on a spot bid or a contract instead. Renting does not change the odds per hash: the odds calculator shows what a given speed and budget actually buys.