Verify

Don't trust. Verify.

SoloLuck is true-solo and non-custodial. Here is how you can check every claim yourself — without taking our word for it.

1 · You hold the keys

You mine with your own Bitcoin address as the username. If you solve a block, the reward is paid by the Bitcoin network straight to that address in the block's coinbase. We never take custody — there is nothing to withdraw and nothing for us to freeze or lose.

2 · 0% fee — nothing is taken

There is no fee — 0%. Solve a block and the entire reward is paid to your address in the coinbase; SoloLuck takes nothing. When a block is found, the spendable payout output is visible on any block explorer; the coinbase may also carry a zero-value witness-commitment output required by the protocol, but SoloLuck receives no spendable fee output — the math is public.

3 · The numbers are real

Every figure on this site comes straight from the pool's own stats. The raw machine-readable feed is at /api/public — the same data the site renders, unedited.

4 · Open source

SoloLuck runs on ckpool, the open-source (GPLv3) solo-mining server — its source is public, so anyone can read exactly how true-solo payout works. The patches SoloLuck adds to it are published too, under the same licence: https://github.com/sololuckio/ckpool-sololuck — apply them to a clean ckpool v1.2.0 checkout and the README tells you the tree hash you should get. The website is still not published, and published source does not prove the binary we run was built from it. The downloadable Windows miner is open source. We would rather say all of that plainly than overclaim.

Several Bitcoin pools, one name

SoloLuck's Bitcoin mining runs in one pool, in Jakarta (stratum.sololuck.io, the address every guide prints; sea.stratum.sololuck.io and, since 2026-10-03, us.stratum.sololuck.io reach the same machine). It has its own Bitcoin node and builds its own block templates. Singapore (sg.stratum.sololuck.io) 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.

Everything above is true at every one of them, and you check it the same way at each. You mine with your own address at any of them; a block solved at any of them is paid by the Bitcoin network straight to that address; neither machine ever holds your coins. Both write the identical coinbase signature /sololuck.io/ into every template they build, so an explorer credits a block from either to SoloLuck — several Bitcoin pools, one on-chain identity, and one entry in the pool directories. Point a miner at any door and its shares turn up on the same per-address stats page and in the same /api/public feed.

Several pools divide nothing. Solo mining shares no work between miners: you search alone, and a block you solve pays you the whole reward. The Bitcoin pools are independent searches that were never cooperating, so nothing about your odds moves — they are your hashrate against the whole Bitcoin network, at any of them, exactly as before. What differs between them is the length of your first hop, and nothing else.

Miner firmware quicklink support

SoloLuck ships in the pool quicklink list of stock Bitaxe firmware — AxeOS v2.15.0 (released 2026-08-21) and later — alongside Public Pool, OCEAN and Braiins, and in the NerdQAxe+ 1.1.0 release candidates (not yet in that project's LTS line). A quicklink opens your SoloLuck worker statistics from the device interface; it only appears once SoloLuck is already configured, so it is a convenience and a public record, not a way people discover the pool.

This is not an endorsement, certification, or guarantee by the firmware maintainers. It is a public integration record that miners can verify themselves.

Public records

Also listed in mining software

  • Hive OS pool templates — merged 2026-09-17, for Bitcoin and DigiByte; this repository is the list of pools Hive OS offers when you build a Flight Sheet
  • SparkMiner (open-source ESP32 solo miner) — merged 2026-09-19; SoloLuck's minimum-difficulty port 3335 is in its README's recommended pools table, and the maintainer checked the port and our description against this site before merging

Why this matters

  • The record is public and reviewable.
  • It helps miners jump from their firmware UI to SoloLuck worker statistics.
  • It reduces confusion when checking whether a miner is connected correctly.
  • It provides another public compatibility trail for SoloLuck.

This does not change SoloLuck's mining odds, fee model, payout rules, block-finding probability, or risk profile.

5 · No tracking

No accounts, no KYC, no trackers, no advertising or third-party cookies, no third-party assets — this page loads nothing from anyone but us. Interface preferences live in your browser's local storage; the analytics opt-out uses one first-party cookie (details on /privacy).

6 · What we can't prove yet

Honesty cuts both ways. As of 2026-10-04 02:05 UTC: SoloLuck has found 0 Bitcoin blocks — solo mining is high-variance and our hashrate is small, so treat a block as a rare, high-variance event, not an expectation. We are a new, small pool — though most of the hashrate here now comes from community miners rather than the operator's own rigs. Uptime on /status is measured from a single home vantage in Indonesia, not a global probe network. We'd rather say this plainly than dress it up.

Updated 2026-09-26. This card used to say that our Bitcoin Cash pool accepted a username that is not a Bitcoin Cash address — a Bitcoin address, a DigiByte address or a nickname — and that a block solved under it would pay SoloLuck, not you. That is fixed: since 2026-09-26 the pool refuses such a login and the error says why, the way our DigiByte pool always has. It refuses the old 1…/3… form of an address too, because that form is written the same on Bitcoin and Bitcoin Cash. You can check it yourself: connect a miner with a wrong username and the login fails.

⭐ It is no longer only a demonstration. SoloLuck has solved 32 blocks on DigiByte mainnet — 24,318,178, 24,316,221, 24,315,923, 24,314,386, 24,314,274, 24,313,585 — and each paid the full block reward in one spendable coinbase output with no fee output, tagged /sololuck.io/. The first six were found by machines the pool operator runs, so they show what the software does with a reward, not that an outside miner has been paid. A different chain at a far lower difficulty than Bitcoin, and the copy will not pretend otherwise — but it is the same pool software and the same payout construction, now on-chain instead of on regtest. Check it, don't take it from us: open those heights on any DigiByte explorer and read the coinbase, or see /blocks for each one checked by hand.

  • 24,318,178000000000000000426d985dd9fb31a79f6ffda6ad7237e21a675d9986307070d
  • 24,316,221000000000000000840a978bb5a954d0f0b8794b9bbcd55a9e0182de5dad1151b
  • 24,315,92300000000000000008f0fb13efbe6aa29d2d90b3cd1cbec5bd38fc6ccfaaa1e4d
  • 24,314,3860000000000000007053913722a76a8172ae1224f274336b2f3a3bdddbf661a44
  • 24,314,274000000000000000018ccde2a0335c4ba73e7ae2b2c47406853bcde10f711cab6
  • 24,313,585000000000000000546b11b9d973c90e18f6079c8c2d82f9bcd29b6dd123f7f0c

7 · Official channels — avoid impersonators

SoloLuck's only official surfaces: this site sololuck.io, the Telegram channel @SoloLuckPool, the community bot @SoloLuckIOMining_bot, and the Windows miner from sololuck.io/setup (current file SoloLuckMiner-v1.11.5.exe) (SHA-256 d529fa273c781f6934bae5f5d9cf751b51aa4b58d90227d16fd7d18be56893ef — verify with sha256sum SoloLuckMiner-v1.11.5.exe before running). We are not affiliated with sololuck.com (a mining-odds calculator) or sololuck.xyz. We will never DM you first. The pool has a single operator and one official bot (@SoloLuckIOMining_bot); both only ever reply to a message you start, and neither will ever message you out of the blue. There is no 'support team' and no other admins or moderators — anyone who DMs you first claiming to be SoloLuck support, an admin, or a moderator, even using our name or logo, is an impersonator. We will never ask for your seed or private keys, and never ask you to deposit anything — and there is no fee — 0%, so the whole coinbase is yours in a block you solve.

The weekly torch — a draw the pool cannot rig

Every Sunday one active community miner is honoured as the week’s torch-bearer — and the pool does not choose. Bitcoin does. The draw takes the newest block hash at pick time, hashes it once with SHA-256 to turn it into an evenly spread number, and lands that on a weight wheel built from every non-operator address active that week, weighted toward the smallest rigs (weight = 1/√hashrate) — the torch exists to honour the hobbyists this pool is for. The full draw record — block hash, every address, every weight — is published at /api/torch the moment it happens; redo the arithmetic and you get the same name.

Current bearer: bc1q4hr2q7…t728 · chosen by block #969,785.