SoloFury ⚡ Non-custodial Solo Pool | BTC BCH BC2 BCH2 XEC DGB | 800+ blocks

[SoloFury]

Live multi-chain block explorer for solo miners — BTC · BCH · BC2 · BCH2 · XEC (free + embeddable)

Disclosure: I run SoloFury, a non-custodial solo SHA-256 pool. I built this explorer as a free public tool and wanted to share it with the solo-mining community here.

What it is
A single block explorer covering all five SHA-256 chains we support, with the data solo miners actually care about — live from our own full nodes:

• Latest blocks per chain — height, time, coinbase address, reward, tx count, size
• Mempool-style strip with the pool tag that mined each recent block
• SoloFury wins — every block our solo miners have found, verified on-chain (clickable to the address)
• Pool distribution and block-interval charts
• Expected-next estimate (pool hashrate vs network) and pool-luck tracking
• Retarget / halving context — useful for BC2 and BCH2 where this is hard to find elsewhere

Why it might be useful
Most explorers are single-chain (and the smaller SHA-256 alts barely have one). This puts BTC, BCH, BC2, BCH2 and XEC side by side, and adds the solo-specific stuff — who mined what, odds context, retarget drift — that generic explorers skip.

Languages
Available in 10 languages (EN/IT/DE/ES/RU/ZH/FR/JA/KO/PT-BR).

Embeddable
You can drop it on your own site/forum/shop with one line of code — three layouts (full / compact / strip+wins), pick the coin, iframe or JS widget. Generator here: solofury.com/embed-explorer/

Links
Explorer: solofury.com/explorer/
BC2 view: solofury.com/explorer/?coin=bc2
BCH2 view: solofury.com/explorer/?coin=bch2

Feedback welcome — happy to add fields or chains people want. It's a tool for the community first.

[SoloFury]

Thanks for the advice. I'm still trying new things. Check out the site.
Good luck with your mining!

[SoloFury]

👻 New free tool: Ghost Miner — a zero-watt solo mining simulator with REAL odds

Just shipped a companion tool for solo miners: Ghost Miner.

You summon a virtual rig on BTC, BCH, BC2, BCH2 or XEC and it hunts real blocks at the live network difficulty — same math as a real solo setup, zero electricity.

Two modes:

• Time Warp — fast-forward through "ghost-years". Blocks pass at the chain's true cadence; you lose almost all of them (just like reality), halvings cut the reward, until your ghost finally wins one.
• Live Haunt — register a ghost and it tracks real blocks in real time. Every draw is provably fair: HMAC(seed, coin:height:block_hash:ghost_id), with the daily seed hash committed before the blocks and revealed after — so you can recompute and verify every result yourself.

Also: a "Hall of the Haunted" leaderboard, an embeddable widget, and 10 languages.

👉 https://solofury.com/ghost/

BCH2/BC2 have the most winnable odds if you want to actually see a ghost land a block. Feedback welcome — especially on the provably-fair verification flow.

[Nexus9090]

Hi Rolando,

Just wanted to share some feedback with you.

I've switched to using Duckduckgo's browser and found that it will not connect to your servers and reports with the error below:-



I can still access using other browsers, so it looks like a problem with DuckDuckGo's browser or something else?

[SoloFury]

TLS / encrypted stratum now live on SoloFury — all 5 coins, all 9 regions
Quick update for anyone who's asked about encrypted connections: SoloFury now supports TLS stratum (stratum+tls://) across every coin (BTC, BCH, BC2, BCH2, XEC) and all 9 regions.
Setup is simple — the TLS port is just the plain port with a "1" in front:
BTC   6060 -> 16060
BCH   7070 -> 17070
BC2   8080 -> 18080
BCH2  8585 -> 18585
XEC   9090 -> 19090
Same hostname as before, only the port and protocol change. Example for a US-East miner:

stratum+tls://us-bch.solofury.com:17070
We use a publicly-trusted Let's Encrypt certificate, so on Bitaxe/AxeOS (2.13+) there's nothing to paste — just enable the TLS toggle in pool settings and you're encrypted end-to-end. Your worker name and share traffic no longer travel in the clear.
There's also a TLS toggle on the setup wizard ( solofury.com/start/ ) that generates the exact config for your coin and region.
Still non-custodial solo, still 1% fee. Feedback welcome as always.

[SoloFury]

Hi Rolando,

Just wanted to share some feedback with you.

I've switched to using Duckduckgo's browser and found that it will not connect to your servers and reports with the error below:-



I can still access using other browsers, so it looks like a problem with DuckDuckGo's browser or something else?

Hi, thanks a lot for reporting this
The key detail is the error itself: ERR_QUIC_PROTOCOL_ERROR. QUIC is the transport behind HTTP/3, which our CDN (Cloudflare) serves over UDP on port 443. What's happening is that the DuckDuckGo browser opens an HTTP/3 connection, it fails for some reason, and the browser doesn't fall back cleanly to regular TCP — so you get a dead page. Other browsers either complete the QUIC handshake fine or fall back to HTTP/2 over TCP automatically, which is why they work for you.

So it's not the pool servers being down — it's specifically how that browser handles HTTP/3. A couple of things on your side that usually fix it:

1. In the DuckDuckGo browser, try disabling HTTP/3 / QUIC if it exposes the setting (some builds do under experimental/network flags).
2. It can also be a local firewall or router silently dropping UDP on port 443 (QUIC uses UDP, normal HTTPS uses TCP). If you're behind a corporate/strict firewall, that would explain why only the QUIC path breaks.
3. As a quick test: connecting through a VPN, or from a different network, will usually tell us instantly whether it's the browser or your network path.

On my end: mining itself is completely unaffected — your miners connect to the stratum endpoints directly (e.g. us-bch.solofury.com), which don't go through Cloudflare's HTTP/3 at all, so your hashrate and payouts are never touched by this. This only affects viewing the website dashboard in that specific browser.

If it turns out a lot of people hit this, I can look at adjusting the HTTP/3 settings on the CDN side — but I'd rather not disable a performance feature for everyone over one browser's quirk unless it's widespread. Let me know if the steps above sort it out, or if anyone else is seeing the same thing.

Thanks again for the heads-up.

[SoloFury]

⚙️ SoloFury nodes are now running Bitcoin Core 31.1.
Synced everywhere. Same non-custodial setup, same coinbase-direct payouts.
🚧 Stratum V2 is close. Lab validation done — production rollout in progress.

[SoloFury]

Every day someone posts the same three problems: a Bitaxe that boots but sits at 0 GH/s, a NerdQaxe rebooting every two minutes, a machine that claims to be hashing while the pool sees nothing.

I got tired of writing the same answers, so I wrote them all down properly.

https://solofury.com/blog/home-miner-troubleshooting-bible/

Free, no signup, no email wall. Available in 10 languages.

What's in it

• Six failure domains that explain nearly every dead unit: power, ASIC init, thermal, network, stratum, firmware
• A 60-second triage — five questions that tell you which domain you're in before you touch anything
• How to read the serial log at 115200 baud, with an annotated healthy boot so you know which milestone failed
• A master symptom table, 31 rows, symptom to likely cause to first action
• A dictionary of red error lines written verbatim as the firmware prints them, so Ctrl+F on your exact string lands on the answer
• Model-specific quirks for Ultra, Gamma 601/602, GT, Hex, Touch, NerdQaxe++, clones, and the BM1373 generation
• A PRO bench section: three DC measurements that partition any power fault, plus what a repair bench can and can't fix

Three things that surprise people

1. USB-C powers the ESP32, not the ASIC. A board running on USB-C alone boots, serves the dashboard, and hashes at exactly 0 GH/s drawing about 2W. It imitates a dead regulator precisely. This costs the community hours every week.

2. A latched TPS546 fault survives software restarts. The fault state lives in the regulator's own status register until input voltage is physically removed. Restarting from the web UI, calling the restart API, pressing the ESP32 reset button — none of them clear it. There's a whole class of GitHub issues about BM1370 boards stuck at 0 GH/s where the restart endpoint fixes nothing and a power cycle fixes everything.

3. Hardware error rate is the honest number, dashboard hashrate is a claim. A chip at 5% errors can display a proud hashrate while effective output quietly drops below what a lower clock would deliver. Tune toward accepted shares per hour, never the dashboard figure.

Also covered

AxeOS ships a power-on self-test most owners don't know exists — it names the broken subsystem in about 30 seconds. And there's a REST API on port 80 that pulls the device logs over the network, so the serial cable is only needed for boot-time failures and crash loops. There's a fleet health script in there too.

On sourcing

Compiled from the ESP-Miner issue tracker and release notes, the ESP-IDF fatal errors documentation, community repair bench material, and the failure patterns that keep coming back in the Bitaxe / NerdAxe / NerdQaxe communities. Every primary source is linked at the end — 14 official links, no mirrors.

Corrections welcome

I run a solo pool, so I'll be upfront: the guide links to our connection page in one place. Everything else is vendor-neutral and points at the open source projects.

If you hit a failure mode that isn't covered, or you think something in there is wrong, post it here. It's maintained as a living document and I'd rather fix it than defend it.

[SoloFury]

Update: Stratum V2 is now live on SoloFury.
 
Running in production since 24 August 2026 across all nine regions. BTC only for now — the V2 stack talks to the node through Bitcoin Core's IPC mining interface, and no other SHA-256 implementation exposes an equivalent yet. BCH, BC2, BCH2 and XEC stay on V1 with full version-rolling.
 
Connecting:

Code:

Scheme    stratum2+tcp://
Ports     3333 (standard) · 3343 (high-diff, S21/S23 class)
Username  your BTC address, optionally .workername
Password  x
 
Authority public key (same on all 9 regions):
9cLif4sCxvAz7FBP7GPvYG8Mv586ZhdgNbn3f4PsrM56gboSZEp

V1 and V2 share the same ports — the pool detects which protocol your miner speaks and answers accordingly, so a mixed fleet points at one address with nothing to reconfigure.
 
Firmware with native V2: Braiins OS+ 26.07+ (key goes in the URL path, not a separate field — a URL without it fails silently), AxeOS 2.14+ and NerdQAxe 1.0.37+. Stock Bitmain, stock WhatsMiner, VNish and LuxOS are V1-only, S21 and S23 included.
 
Worth knowing: a V2 config that silently falls back to V1 produces no error — miner connects, shares accepted, everything looks fine. Check your firmware's pool status, or query the API:

Code:

curl -s "https://solofury.com/api-btc/client/YOUR_ADDRESS" | jq '.workers[] | {name, protocol}'

With an extended channel and coinbase decoding on, your miner also displays the block outputs before hashing them — so you can verify the 99% is addressed to your wallet rather than take my word for it.
 
To be clear about what this isn't: no job declaration. The pool still builds the templates. If transaction selection is what you want, DEMAND and Braiins Pool do that. For solo mining the V2 wins here are encryption, latency and the coinbase verification above.
 
Setup reference: solofury.com/guides/stratum-v2-connect
 
Questions welcome.

[SoloFury]

SoloFury update — the miner page, rebuilt around you and your hardware

Over the last week we rebuilt the entire miner page on SoloFury. Not a restyle: every section was redone with one idea in mind — a solo miner should be able to open one page, for one address, and know within seconds whether their setup is doing what it should. No account, no signup, nothing to configure. Paste an address, everything below is yours.

Here is what changed, section by section, with the technical details for those who want them.


Real screenshot from today. Only the address was replaced.


1. Worker table: grouping, tiles, outlier detection

Anyone running more than a handful of devices knows the problem: twenty rows that all look alike. The table now has three grouping modes:

• Family — automatic. The table strips the trailing number from each worker name (S21Plus01, S21Plus02 → group "S21Plus"), or uses an explicit prefix if you name your workers rack1_s19-01. Nothing to configure, and because the grouping lives in the name, it follows you on every device.
• Region — by the stratum region each worker connects through.
• Custom — drag one worker onto another, name the group. Multi-select with checkboxes on mobile. Saved per wallet address and coin in your browser.

Each group header shows summed hashrate, online count, best difficulty and most recent share, and collapses with a click. On top of that:

• Outlier detection — inside a homogeneous family, any worker below 72% of the family median gets an orange "attention" tag with the percentage gap. That is how you spot the one S21 that is quietly running at 70% before it shows up in your daily totals.
• Tiles view — a heatmap: one tile per worker, coloured against its family median (green above, orange below, red offline). For 20+ devices you see the state of the whole fleet in one look. Click a tile → the table opens on that worker.
• Filters — All / Online / Attention / Offline with counts, and a search box that accepts regex.

The worker detail panel (the + button) is untouched — every patch was verified byte-for-byte against it.

Naming guide, in 10 languages: How to name mining workers


2. The chart



Still Chart.js — we benchmarked the alternatives and at our data volume (288 points per 24h) there is no reason to change engine; the difference is in what sits on top of it:

• Stats strip — now, average, peak, low, % vs your average, and minutes spent under −15% of it, for the selected range.
• Attention bands — every window where you dropped below −15% of your own average is shaded. Against yourself, not against the network.
• Previous period — yesterday overlaid on today as a grey dashed line (up to 7d ranges).
• Rich tooltip — time, hashrate with delta vs average, accepted shares, difficulty in one hover. Zoom with the wheel, pan by dragging, double-click to reset. LTTB downsampling keeps 90-day ranges smooth.
• Rejected shares — the toggle appears only if your address actually has rejected/stale/invalid shares in the range. If you mine clean, it stays out of your way.
• Share PNG — one click exports the chart with your stats, coin, period and address as a branded image.

Range and toggles are remembered per address. The pool page chart got all of the same, with pool data.


3. Cards that are entry points, not just numbers

The top cards now use the same colours and thresholds as the table and the chart, and each one takes you somewhere:

• YOUR HASHRATE shows the 24h stats strip in miniature, attention bands and your block pins on the sparkline. Click → the chart with the average line drawn.
• ASIC ONLINE — online / attention / offline with a tri-colour bar and chips for your three largest hardware families. Click the card → the table filtered on attention. Click a chip → only that family open.
• BEST SHARE — the all-time record plus the 24h best with the worker that found it. Click → table sorted by best difficulty, worker highlighted.
• BLOCK IN PROGRESS — with your current round effort. Click → the luck section.

The threshold for "online" was also aligned between cards and table (10 minutes), so the two never disagree.


4. Luck, calculated properly

This is the part we spent the most care on, because it is the number solo miners look at every day.

Round effort = work done ÷ work expected. Work done is the sum of the difficulty of your accepted shares since your last block, aggregated across all our regions; work expected is the current network difficulty. This is the definition 2Miners, Kryptex and Miningcore use. It rises until you find a block, then resets to zero. If difficulty changes mid-round, it moves with it.

Two things we added on the backend:

• Effort is recorded at every block. When your address finds a block, the final effort of that round is written to disk before the reset. From now on, every block on your page shows the luck of the round that produced it — real shares, not an estimate.
• Effort never resets without a block. The per-address baseline is persisted to disk, so an aggregator restart does not touch anyone's bar. And if a mining node restarts and its cumulative counter drops, the baseline is recalibrated to preserve the effort in progress. We tested this explicitly: restart the aggregator, same number before and after.

On the page: your current round on an honest 0→300% scale (the old bar was capped at 100%, so 137% looked exactly like 100%), the time since your last block against the expected time at your 24h hashrate, a probability curve with the 50/50 point and "you are here", and a histogram of your real rounds — median, best, worst, blocks found vs expected.


5. Blocks, fully explained

Every block your address has found is now enriched from our own nodes, not from a label:

• Block hash, confirmations, time, difficulty, transaction count, size.
• The coinbase, decoded: subsidy plus the transaction fees that block carried, then the two outputs — yours, and the 1% pool fee. This is the non-custodial model made visible: the same numbers a block explorer shows, because they come from the coinbase itself. Anyone can verify them.
• USD value on the day it was found (historical price, cached permanently) and USD today.
• Luck of that round, your hashrate at the time, best share of the round, time since the previous block vs expected.
• Status from the chain: maturing (with confirmations counting up and time to spendable), matured, or orphaned.

Layout: a lifetime strip (blocks, mined, value today vs when found, average luck, days since last vs expected), months with only the current one open, a two-line row per block, and a four-column panel on click: Block · Reward · Round · Verification. Search by height, deep link to any block, CSV/JSON export for your records, a share card for the day you hit.

On the pool page the same data is a calendar: days with blocks light up, brighter with more; click a day to see who found what, from which region; a year heatmap shows the pool's rhythm at a glance. Since April: 97 blocks, $71,000+ paid directly to miners' addresses — none of it ever passed through us.


Under the hood, briefly

Astro static frontend, 10 languages, ~1,000 pages. Block enrichment runs as a cron on our aggregator: it queries the local node of each coin (getblock, coinbase outputs), CoinGecko for historical prices, and our own hashrate history for round statistics, and writes static JSON served by nginx — no new API surface, nothing dynamic to break. Everything mentioned above is live on all five SHA-256 coins (BTC, BCH, XEC, BC2, BCH2) across nine regions on five continents.


What's next

• Public pages for every block found (/block/coin/height) — a verifiable, shareable proof page.
• The stratum region that delivered each block, shown on the block.
• Full translation of the new sections' labels (the section titles are already in 10 languages).

Try it

solofury.com/miner/ — pick a coin, paste your address. If you are not mining with us yet, the Solo Start page generates the configuration for Bitaxe, NerdAxe, Antminer and Whatsminer in one step.

Feedback, bug reports and feature requests are welcome here in the thread. This whole update came out of one miner's frustration with twenty identical rows — the next one can come out of yours.

Non-custodial. No signup. 1% fee, paid as a second coinbase output.

[Nexus9090]

Its good, I have a few miners pointed to BTC, BCH and BC2 now.

Your web interface is clean and easy to use, excellent job!

 

[SoloFury]

Thanks, that's great to hear —
The interface took a lot of long evenings, so it's good to know it lands.

If you want to catch the updates as they ship, we post everything on X: https://x.com/SoloFuryPool

[SoloFury]

Update: Block Info — a block explorer for six SHA-256 chains, live from our own nodes

Over the last week we replaced the old explorer page with something we wanted for ourselves: one place to look up any block on BTC, BCH, BC2, BCH2, XEC and DGB, read straight from SoloFury's nodes and updated every minute.

https://solofury.com/block-info/btc/

What it does

• Search by block height, block hash or pool name, on any of the six chains.
• Every coinbase, broken down by role: miner output, pool fee, OP_RETURN, and on eCash the consensus outputs (miner fund and staking) shown separately, so you can see exactly who received what in each block.
• Pool attribution with a confidence level: blocks are attributed from coinbase tags and published rules, and the page says how sure the attribution is. Blocks with no recognisable tag are labelled "Unattributed" instead of guessed.
• Our own fee, verified on-chain: on every SoloFury block the 1% pool-fee output is checked against the coinbase, and the block page shows the result.
• The ember line: the mempool being forged on the left, the latest blocks cooling on the right, with size, transaction count and age.
• Block intervals and pool distribution over the last 200 blocks, pool pages with blocks over time, and a side-by-side pool comparison.

How the numbers are made
The methodology page explains data sources, indexing, how reward, subsidy and fees are split, coinbase output roles, the attribution rules, the fee audit and the limits: solofury.com/block-info/methodology. The same data is available through a public API, documented on the same page.

Also new on the site

• Who runs SoloFury and how payouts work: solofury.com/about · legal notice: solofury.com/legal
• For farm operators and hosting providers: what solo variance really looks like on BTC and BCH, with dry-spell probabilities and cash-flow sizing: solo mining for hosted fleets

Feedback is very welcome, especially on attribution: if a pool's blocks are mislabelled or unattributed, post the height here and I'll check the rule.

— Rolando

[Nexus9090]

Nice feature