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!