SoloFury ⚡ Multi-Coin SHA-256 Solo Mining Pool | BCH BTC BC2 BCH2 XEC | 1% Fee

[Nexus9090]

I like the changes you've made to the site, I can see its still a work in progress but its coming along quite nicely.

I currently have my last remaining Bitaxe pointed at your BC2 pool. However the BC2 price is not presently shown; where it was on the previous incarnation of the site.





One other thing that's changed that might not be ideal, is that the linking to a particular miner has changed so bookmarks no longer work without re-entering the miner address and then re-saving the bookmarks.

Lastly the ping I'm seeing to you EU Frankfurt server isn't anything like what your site reports (16mS).

I'm located in England and I'm currently seeing 140mS to your BC2 primary pool (stratum+tcp://eu-bc2.solofury.com:8080)

I appreciate there's a lot of mechanics at play with network hops etc, however this is significantly more than it was when I first tried your pool I was averaging 25-35mS previously. Has something changed at your pool end?


I note you've found another BCH block, congratulations! to you and the miner who won it. 

Mine on!

[SoloFury]

Thanks for the info, I'll check everything.
I'm very happy you're reporting problems. It's not easy to find all the changes on your own; there are so many at once.
Structuring the new interface wasn't easy.
Yes, the new block was found just as I was loading the new interface. I'll check the problems.

Happy mining and good luck!

[Nexus9090]

Thanks for the info, I'll check everything.
I'm very happy you're reporting problems. It's not easy to find all the changes on your own; there are so many at once.
Structuring the new interface wasn't easy.
Yes, the new block was found just as I was loading the new interface. I'll check the problems.

Happy mining and good luck!

Thanks,

Its hard work proof reading your own work. I'm sure you'll figure it out.

It'd be nice to win a block or two 

[SoloFury]

Here I am, I made some changes. BC2 Price: Just fixed it an hour ago. It was a weird CoinGecko bug: their API was returning {"error":"offline"}; it should now work properly.
Broken bookmarks — FIXED: Great report. The old SPA used URL fragments (#bc2/qq...) for miner pages; the new Astro build uses query params (/miner/?coin=bc2&addr=qq...). I just deployed a redirect handler for legacy bookmarks in the site header — old hash-based URLs are now automatically redirected to the new format. Your existing bookmark should work as is, without doing anything. The new canonical format (if you want to re-save) is: https://solofury.com/miner/?coin=bc2&addr=TUO_ADDIRIZZO_BC2
Frankfurt latency (140ms from the UK): Just ran diagnostics on the primary server. The Frankfurt relay is working normally. UK → Frankfurt via decent fiber should be 10-25ms (London-Frankfurt is one of the lowest-latency intercontinental links in Europe). 140ms means something is adding ~100ms to the path between you and solofury. Most likely causes, in order:
ISP routing via the US. Some UK ISPs (especially BT Wholesale and Virgin Media during peak hours) route Vultr traffic via the US East Coast peering instead of the direct EU peering. This would add exactly the ~100ms you see.
VPN / Cloudflare WARP / privacy proxy active — easily +50-100ms.
Your ISP's peering issue with Vultr Frankfurt.
If you can:
tracert eu-bc2.solofury.com
(or traceroute / mtr on Linux). The hop where the latency jumps from ~10ms to ~100ms is the real deal. If it's hops 3-5 (within your ISP), it's their internal routing. If it's hops 6-8 (transit provider), it's a peering issue. It's worth reporting to your ISP in both cases.
It's also worth comparing: ping eu-bch.solofury.com (port 7070, same Frankfurt server) — if that's also 140ms, it's the network path. If BCH is 25ms and BC2 is 140ms, there's something weird going on at the HAProxy level on a specific port (very unlikely, but I'd like to know).

[Nexus9090]

Here I am, I made some changes. BC2 Price: Just fixed it an hour ago. It was a weird CoinGecko bug: their API was returning {"error":"offline"}; it should now work properly.
Broken bookmarks — FIXED: Great report. The old SPA used URL fragments (#bc2/qq...) for miner pages; the new Astro build uses query params (/miner/?coin=bc2&addr=qq...). I just deployed a redirect handler for legacy bookmarks in the site header — old hash-based URLs are now automatically redirected to the new format. Your existing bookmark should work as is, without doing anything. The new canonical format (if you want to re-save) is: https://solofury.com/miner/?coin=bc2&addr=TUO_ADDIRIZZO_BC2
Frankfurt latency (140ms from the UK): Just ran diagnostics on the primary server. The Frankfurt relay is working normally. UK → Frankfurt via decent fiber should be 10-25ms (London-Frankfurt is one of the lowest-latency intercontinental links in Europe). 140ms means something is adding ~100ms to the path between you and solofury. Most likely causes, in order:
ISP routing via the US. Some UK ISPs (especially BT Wholesale and Virgin Media during peak hours) route Vultr traffic via the US East Coast peering instead of the direct EU peering. This would add exactly the ~100ms you see.
VPN / Cloudflare WARP / privacy proxy active — easily +50-100ms.
Your ISP's peering issue with Vultr Frankfurt.
If you can:
tracert eu-bc2.solofury.com
(or traceroute / mtr on Linux). The hop where the latency jumps from ~10ms to ~100ms is the real deal. If it's hops 3-5 (within your ISP), it's their internal routing. If it's hops 6-8 (transit provider), it's a peering issue. It's worth reporting to your ISP in both cases.
It's also worth comparing: ping eu-bch.solofury.com (port 7070, same Frankfurt server) — if that's also 140ms, it's the network path. If BCH is 25ms and BC2 is 140ms, there's something weird going on at the HAProxy level on a specific port (very unlikely, but I'd like to know).

Tracert response:-

Code:

Tracing route to eu-bc2.solofury.com [136.244.90.16]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms    <1 ms     1 ms  192.168.1.254
  3     2 ms     1 ms     2 ms  172.16.15.95
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        6 ms     *     core6-hu0-7-0-35.faraday.ukcore.bt.net [62.6.201.247]
  7    10 ms     7 ms     7 ms  166-49-209-194.gia.bt.net [166.49.209.194]
  8    20 ms    20 ms    20 ms  t2c4-et-4-0-2.de-fra.gia.bt.net [166.49.208.35]
  9    21 ms     *       20 ms  decix.fkt.vultr.com [80.81.196.21]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    21 ms    21 ms    21 ms  136.244.90.16.vultrusercontent.com [136.244.90.16]

Looks like a routing issue with my ISP.

I'll reset my router and gateway and see if that resolves the delay.

I dont think its an issue your end. But thanks for looking into it.

[Delaforetnoire]

I'm very happy you're reporting problems. It's not easy to find all the changes on your own; there are so many at once.

You staying active and handling everything so well already means a lot. Stay active here, keep solving the problems, keep moving forward. Wishing you all the best.

[Nexus9090]

Hi Rolando

Would it be possible for you to add back in the USD calculated value on the block reward that was on the original version of your site.



Also, in the mining luck/block odds section the block value is not shown





Many Thanks

Mine on!

[SoloFury]

Looks like a routing issue with my ISP.

I'll reset my router and gateway and see if that resolves the delay.

I dont think its an issue your end. But thanks for looking into it.

There are no problems :-) I hope you solve it.

[SoloFury]

I'm very happy you're reporting problems. It's not easy to find all the changes on your own; there are so many at once.

You staying active and handling everything so well already means a lot. Stay active here, keep solving the problems, keep moving forward. Wishing you all the best.

Thank you so much. I've been mining for a long time, it's always been a passion of mine. I have some nerdqaxe nerdoctaxe, and about 6 months ago I got some s21s. I've always solo mined in various pools, switching from one pool to another. I always felt like something was missing, so I started solofury. This made me even more passionate. But it's not a job for me. It's just passion, I dedicate a lot of time to it, and I'd like to try to help. Thanks for the kind words, though. I'm very happy.

Hi Rolando

Would it be possible for you to add back in the USD calculated value on the block reward that was on the original version of your site.

https://i.ibb.co/bj7qgVG0/solofury-bc2-price-2.jpg

Also, in the mining luck/block odds section the block value is not shown

https://i.ibb.co/MxDykvWj/solofury-bc2-price-3.jpg



Many Thanks

Mine on!

I should have fixed both problems, you can check.
I've put a few articles inside the blog, there's one that talks about bc2, take a look: https://www.solofury.com/blog/

[Nexus9090]

Hi Rolando

Would it be possible for you to add back in the USD calculated value on the block reward that was on the original version of your site.



Also, in the mining luck/block odds section the block value is not shown





Many Thanks

Mine on!

I should have fixed both problems, you can check.
I've put a few articles inside the blog, there's one that talks about bc2, take a look: https://www.solofury.com/blog/

Thanks for fixing the problems.

The blog article on BC2 was interesting, I was wondering when the re-target was due.

Thanks!

[SoloFury]

I'm glad you read it. Good luck mining!

[SoloFury]

Hey guys 👋

I just finished something I'm pretty proud of and wanted to share it here first.

You know how setting up a miner on a new pool is always a bit of a pain — digging through docs, copy-pasting stratum URLs, figuring out which server is closest to you? I wanted to fix that for SoloFury.

So I built Solo Start → solofury.com/start/

It's a 4-step configurator that:
• Detects your location automatically and picks the nearest server (US/EU/Asia)
• Shows a 3D interactive globe where you click your city and see the connection arc animate in real time
• Spits out your full stratum config — Pool 1, 2, 3 failover, worker, password — all ready to copy or download
• Works for all 5 coins: BTC, BCH, BC2, BCH2, XEC
• No account, no KYC, no email, nothing. Just open the page and go.

I built it for Bitaxe miners, NerdAxe users, and anyone who just wants to point their ASIC at a solo pool without the headache.

Would love to hear what you think — especially if something doesn't work with your setup. Happy to add more hardware models to the list too if yours is missing.

Cheers 🤙
Rolando — SoloFury

[SoloFury]

Hey everyone! 👋

Quick update from SoloFury — I just shipped two small but pretty handy features for the /miner/ dashboard. Nothing crazy, just things I personally wished for as a solo miner, so I built them.

The two new buttons in the top-right of the identity card:

📜 .LOG button — one-click diagnostic report

Click and you get a 14-section plain-text .log file with everything happening on your wallet right now:

• Executive summary — status, top issues to investigate first
• Per-worker health analysis — drift detection vs 1h/24h averages, severity levels (OK / WARN / CRITICAL) with suggested actions for each problem
• Difficulty optimization — tells you per worker whether to raise/lower the diff to hit ~1 share / 10s
• Share quality breakdown — rejected / invalid / stale / duplicate rates
• 24h statistics + ASCII hashrate timeline
• All blocks ever found by your wallet (height, date, which worker submitted the winning share)
• Network context with statistical TTF (Time To Find next block)
• Pool context for cross-checking

Here's a snippet of what it looks like (real output from my own farm, 4× S21+ on BCH):

Code:

══ 3. WORKER HEALTH ANALYSIS ══

  ⚠  1 of 7 workers need attention:

  ┌─ S21Plus04  [CRITICAL]  ───────────────────────
  │ Hardware:    Antminer S21+
  │ Hashrate:    2.54 TH/s   now
  │              27.3 TH/s   (1h avg)
  │              165 TH/s    (24h avg)  ← reference
  │ Uptime:      20d 9h
  │ Last share:  22m ago
  │ Issues:
  │   ⚠ OFFLINE — no shares for 22m
  │   ⚠ HASHRATE -98% vs 24h avg (severe degradation)
  │ Suggested actions:
  │   • Worker offline > 10min. Check power & network
  │   • Verify ASIC web UI is reachable
  │   • Check stratum URL & port still match pool config
  └───────────────────────────────────────────────────────

https://solofury.com/guides/miner-log/

It actually caught one of my own ASICs that had a hashboard issue I hadn't noticed yet. 🙃

📤 SHARE button — auto-generated PNG card

Generates a 1200×630 PNG with your current hashrate, ASIC count, blocks found, total mined and BCH/BTC/XEC price. Good for tweeting your latest block, dropping on Reddit, or just showing off in Discord.

good luck with mining!

[Nexus9090]

Thanks for adding the log feature, that's quite nice.

I've noticed a formatting problem when viewing the miner stats page on a tablet or phone.

The miner address bar doesn't format nicely and all becomes squashed up:-




Not really a big issue but it does spoil the look and feel a bit.


Anyway

Good luck and Mine On!!!

[SoloFury]

Hi, yes, you're right, it's being optimized for mobile viewing. But first I need to finish the interface with the various functions. This is because adding more things would break the mobile layout. I'll optimize this chapter soon, too.
Thanks so much for letting me know.

[SoloFury]

🌍 Click to see the 9-region globe (PNG, 1024×545)


Some news from the SoloFury side.

A few months ago I was running this pool on 3 servers — Atlanta as main, Frankfurt and Singapore as relays. Worked fine for most people but anyone mining from Brazil, South Africa, Israel, the UK, or East Asia was sitting on 200ms+ stratum latency. Not great for solo where every share counts.

So over the last week or so I deployed 6 more relays: São Paulo, Johannesburg, Tel Aviv, Seattle, London, Tokyo. 9 regions total now, covering pretty much every continent.

While I was at it, I rewrote the /start configurator. The 3D globe now:

• Picks your nearest server the moment the page loads (no permission popup — uses your IP)
• Shows a live animated link between you and the closest region
• Lets you click any city to preview how the routing would change from there
• Compares the top 3 regions for ping/distance side-by-side

All 45 stratum endpoints (9 regions × 5 coins) are live. BCH, BTC, BC2, BCH2, XEC — all the usual ports, just with regional hostnames now too (e.g. uk-bch.solofury.com:7070 for the new London relay, jp-btc.solofury.com:6060 for Tokyo, and so on).

Would love feedback from anyone in the new regions — drop a reply if your stratum latency improved (or didn't!).

— Rolando

P.S. — the whole idea behind SoloFury is to let you actually see everything that's happening, like it's your own personal pool. That's why we've got the miner log, and more transparency features are on the way. Not the classic 'point your miner at the URL and hope for the best' kind of pool.

[Nexus9090]

🌍 Click to see the 9-region globe (PNG, 1024×545)


Some news from the SoloFury side.

A few months ago I was running this pool on 3 servers — Atlanta as main, Frankfurt and Singapore as relays. Worked fine for most people but anyone mining from Brazil, South Africa, Israel, the UK, or East Asia was sitting on 200ms+ stratum latency. Not great for solo where every share counts.

So over the last week or so I deployed 6 more relays: São Paulo, Johannesburg, Tel Aviv, Seattle, London, Tokyo. 9 regions total now, covering pretty much every continent.

While I was at it, I rewrote the /start configurator. The 3D globe now:

• Picks your nearest server the moment the page loads (no permission popup — uses your IP)
• Shows a live animated link between you and the closest region
• Lets you click any city to preview how the routing would change from there
• Compares the top 3 regions for ping/distance side-by-side

All 45 stratum endpoints (9 regions × 5 coins) are live. BCH, BTC, BC2, BCH2, XEC — all the usual ports, just with regional hostnames now too (e.g. uk-bch.solofury.com:7070 for the new London relay, jp-btc.solofury.com:6060 for Tokyo, and so on).

Would love feedback from anyone in the new regions — drop a reply if your stratum latency improved (or didn't!).

— Rolando

P.S. — the whole idea behind SoloFury is to let you actually see everything that's happening, like it's your own personal pool. That's why we've got the miner log, and more transparency features are on the way. Not the classic 'point your miner at the URL and hope for the best' kind of pool.

Hi Rolando

I spoke with the tech support at my ISP to try and see if there was anything that could be done to reduce latency. After a long discussion and being transferred to several different representatives I eventually ended up talking with one of their technicians that actually seemed to know what he was talking about and was a BTC enthusiast himself.

He's suggested that because your BC2 service runs on ports 8080/8081 that theses were typically alternate HTTP ports and as a result are heavily screened & filtered service ports and that may be the reason for the additional transport delays.

He suggested you might want to use a non-standard port to run the service on then it won't be subject to the additional screening overheads.

I don't know if that's something you can do, I appreciate it probably requires some work to make it happen.

Anyway, The change over to uk-bc2 has reduced the ping time to 75-90mS, but not completely solved the problem.

Thanks!

[SoloFury]

Hey, talking to an ISP is often difficult. You can try this. For bc2, I use port 8080 as the primary port (but some ISPs use this as an HTTP alternate port). Each coin has three ports, so if there's a problem with one port, it immediately switches to the other. (It's set so that in the event of a disconnect, it automatically switches to the other using internal routing.) However, if your ping is a bit slow, that's okay.

You can try connecting here: uk-bc2.solofury.com:8081 (BC2 uses port 8080-8081-8082). This port is not an HTTP alternate port.

You can try it and let me know how it goes.

[Nexus9090]

Hey, talking to an ISP is often difficult. You can try this. For bc2, I use port 8080 as the primary port (but some ISPs use this as an HTTP alternate port). Each coin has three ports, so if there's a problem with one port, it immediately switches to the other. (It's set so that in the event of a disconnect, it automatically switches to the other using internal routing.) However, if your ping is a bit slow, that's okay.

You can try connecting here: uk-bc2.solofury.com:8081 (BC2 uses port 8080-8081-8082). This port is not an HTTP alternate port.

You can try it and let me know how it goes.

Hi

Well, I've tried it and its made no difference. So it looks like its just plain old routing delays.

At the end of the day its no worse than ckpool was when it was "east-coast" hosted only. However, for eusolo.ckpool I get <20mS typically so there's something odd going on with routing to your service.

Never mind, at least its working even if it is a little slow on the ping.

Thanks for looking into it.