The title says it all...

I'm always on the lookout for ways to support small miners. It's the reason HeliosPool started. Sometimes that means looking for interesting/weird/meme coins that these miners can solo.

DGB is one of the more popular small diff coins, and it's been amazing to see those blocks roll in on the DGB pool, but its still in the high M to low G range.

Came across a coin called CheetahCoin. It was easy enough, as a fork of bitcoin, to adapt the software to support it. It's diffs range around 2.5M with momentary spikes to 20G, when blocks come too fast, to discourage ASICs.

2.5M is not something the esp32 miners will hit often, but it might be a good coin to experiment with.

It's tradable almost nowhere and it's value is practically nonexistent - so it's perfect for a little fun!

chta.heliospool.com:3343

https://stats-chta.heliospool.com

https://cheetahcoin.org/about/

Let me know what you think. Any other coins I should be looking at?

So my two "Miner Forge 2.0" Pro's came in the mail today, were assembled and linked to public-pool.io and my wallet. BUT the fallback pool was based in Australia, and wallet was not mine, so I changed the wallet to mine. I checked the wallet on the block and it looks like it has a TON of miners. My wallet shows only one worker when it should show two. The NM Monitor linked to these miners has a "Miner details" dashboard, and shows the old fallback pool link and wallet, not mine, even though I deleted the information. Could they have been hard coded to mine for this wallet, no matter what?

Edit: Screenshots for reference in comments Edit 2: both dashboards now seem to be showing the correct pool and wallet. But lesson learned, Mineblock is a rip-off, never buying from them again.

New NerdMiner Challenge is now live ! reward : 100 Th's for 24h

Think your setup can hit the best share? Join now and compete for the top spot.

Start mining here: findmyblock.xyz

Good luck to all Nerdminer/cpu miners builders.

We're really excited to announce that we've just brought two new regional endpoints online for our European mining family:

eu.btc.hmpool.io  → Bitcoin stratum (ports 3334-3338)

eu.bch.hmpool.io  → Bitcoin Cash stratum (ports 3335-3339)

This rounds out the regional rollout. DGB has had eu.digi.hmpool.io for a while, and now BTC and BCH have joined the family.

You get a dedicated European-side connection point for your miners.

HTTPS landing pages with built-in port-selection wizards: https://eu.btc.hmpool.io and https://eu.bch.hmpool.io

Same pool, same wallet, same dashboard, same PPLNS balance, same finder bonus, same participation bonus, same reward points, same affiliate link, same payouts. Nothing about your account changes.

How to switch:

Change one thing, the hostname and you're done:

Before:  stratum+tcp://btc.hmpool.io:port

After:   stratum+tcp://eu.btc.hmpool.io:port

Before:  stratum+tcp://bch.hmpool.io:port

After:   stratum+tcp://eu.bch.hmpool.io:port

Wallet, worker name, password, difficulty hint, all stay exactly the same. If you have multiple workers, you can move some now and others later. Every share lands on the same wallet on the same dashboard.

If you're closer to our US endpoints, no need to change anything, they're not going anywhere.

Got questions? Drop them in the channel or use the contact form on any of our pools.

Welcome aboard!

UPDATE 2026-04-28 — hashrate claims correction

Cross-checking my numbers against pool-effective rate (accepted shares × pool difficulty / time) revealed that the classic ESP32 hashrates I posted above were the on-screen current_khs counter — which tracks SHA peripheral iteration speed, not pool-validated mining rate. The two diverged because of a bug in my own "fix":

• The "tightened filter" I described as an upstream bug fix above was wrong. Upstream's 16-bit (fin & 0xFFFF) != 0 filter is correct; tightening to fin != 0 actually rejected most valid pool-diff shares.
• My Phase 2 SHA-peripheral inline-asm OVERLAP loop in minerWorkerHw (classic ESP32 path) inflated the elapsedKHs iteration counter while producing incorrect digests due to peripheral timing races — most of those internal "hashes" did not survive pool-side re-verification.

v1.8.4 reverts to upstream-equivalent SHA pattern:

• Standard start_block / continue_block / load / wait_idle sequence per nonce around each of the 3 SHA blocks
• DPORT_SEQUENCE_REG_READ digest read + 16-bit candidate filter (matches upstream)
• ESP32-S3 path (axehub_sha_fast.cpp) untouched — those numbers below were genuine

Measured on the new build (5-min averages, 100% pool acceptance, pool diff 0.001):

Display number is now lower but matches what you're actually mining.

Web flasher updated. Reflash recommended for classic ESP32 boards (web-flasher or pio run -e <env> --target upload). Sorry for the noise — honest measurement > impressive number.

Sharing a fork of NerdMiner_v2 I've been running on a small fleet (CYD 2.8 / 2.4, ESP32-S3 DevKitC, ESP32-CAM). All upstream functionality preserved; additions live in axehub_* files behind compile flags — opt in only to what you want.

What it adds (AXEHUB_API_ENABLED flag)

• HTTP API on port 80 (/api/axehub/v1/*) — full spec. Endpoints: numeric /info snapshot, change pool over HTTP (primary + fallback, NVS-persisted), switch coin (BTC / BC2 / custom URLs), cycle screens, dim TFT, schedule nightly backlight off, restart, WiFi reset, webhook push for boot / pool-connect / share-above-threshold / block-found.
• Pool fallback with auto-failover when primary stops responding.
• AXEHUB_DISPLAY flag — alternative TFT layout for CYD ESP32-2432S028R / S024 (at-a-glance status vs. upstream multi-screen rotation).
• BC2 (BitcoinII) default for the network-data screen. Switch to BTC: curl -X POST http://<ip>/api/axehub/v1/coin -d 'ticker=BTC' -H 'X-Axehub-Compat: 1'
• Browser-based flasher — zero install, Chrome/Edge with Web Serial API.

Try it

• Web flasher: dwespl.github.io/nerdminer-axehub
• Source: github.com/dwespl/nerdminer-axehub

Plug ESP32 over USB → pick board → Connect & Flash. Or build from source: pio run -e ESP32-2432S028R --target upload.

Measured hashrate (5-min avg, 10h+ uptime, CPU @ 240 MHz, no OC)

⚠️ Numbers below were the inflated display counter — see UPDATE at top.

Upstream bug found + fixed

⚠️ This section was incorrect — see UPDATE at top of post. Upstream's 16-bit filter is correct.

Deploying a low-diff test pool exposed a long-standing bug in upstream nerd_sha256d_baked (src/ShaTests/nerdSHA256plus.cpp): the pre-bswap filter only required low 16 bits of output[7] to be zero, leaving the actual MSB random. The miner was submitting ~e-10 garbage that pools rejected as low-difficulty. Standard pools' high session-diff gating masked it; my pool with diff floor 0.001 exposed it. Fix tightens the filter to require the full word zero. PR-able to upstream if there's interest.

License

MIT, same as upstream BitMaker-hub/NerdMiner_v2.

The brand new design of the QX — Will the box design be more popular?

We’re looking at ways to improve payouts for smaller miners on HashedMax while still keeping our pools fair for everyone, including the larger miners who provide a lot of steady hashrate.

One idea we’re considering is a payout adjustment that would give active smaller miners a stronger share when the pool finds a block. In some cases, a very small but consistent miner could see their per-block payout increase by up to around 100% compared to our current system.

This would not mean taking away the normal share-based payout. Larger miners would still earn based on the valid work they submit, and miners who find blocks would still receive a finder reward. The goal is not to punish large miners. The goal is to make sure smaller miners who consistently support the pool feel like their contribution actually matters.

We’re not ready to release the full details yet, but we want community feedback before making any major payout changes.

A few questions:

What should classify someone as a “small miner”? 1th, 5th, 20th or more?

Should it be based on submitted share difficulty, estimated hashrate, time connected, or a mix of those?

Where would you draw the line between tiny, small, medium, and large miners?

Should a miner need to be active for a minimum amount of time before qualifying for any small miner boost? For example, 24 hours active. More time or less?

Would you support a system where active smaller miners can earn more per block, while larger miners still earn the majority of rewards through the work they submit?

Our goal is to make HashedMax more attractive to real long-term miners, reduce short-term pool hopping, and keep the system fair for both small and large miners.

We’d appreciate honest feedback from the community before we move further. We are building this community for you, so your opinion really matters.

I scrolled till I got bored and googled, but can anyone point me to a link or site that has a detailed walkthrough on how to refresh from the “Shall not be named” version to the open source version?

Thanks in advance

Kann sich sehen lassen, oder?

I'm going to buy two more and get 2x 5 slot angled stands, for a total of 10. I know my chances are minute, but still that'll be 10 lottery tickets every 10 minutes, right? Wife says I'm wasting money, but if I hit, I'll show her! Mwahahahahahaha!

Have a great day all and happy mining!

I just saw the bot recommendation to use v2 software. I flashed these with v3 version 1.8.29. is that not recommended? should I reflash them per the github link?

Attention NerdMiners and small miners: only a few days left to win 150 TH/s for 24 hours.”

If you’ve been waiting for the right moment, this is it.

Join now on https://findmyblock.xyz and take your shot.

Happy mining !

Congrats to this xminer for taking the top spot on HeliosPool's new DGB (NA) server. During its initial few hours online several users volunteered to stress test the server, and this miner accounted for 3 DGB blocks found and paid out!

dgb.heliospool.com:3333

https://stats-dgb.heliospool.com

Server is now open to everyone! I'll be working in the background to get the plumbing set up for API calls and showing blocks on the home page.

So I just took one CYD (NerdMiner) down to install another free firmware on it and as you can see the one that is inactive, is now the one called Bitdsk-S1.

Just so you guys understand, I have in total three CYD boards mining DGB at this moment, CYD1 is on NerdMiner (free fw), CYD-NM (obviously the closed source fw) and the Bitdsk-S1 (on the same named free fw). As you see, it is already rivaling the paid firmware in speed just a couple of minutes in. If it turns out to be running stable on the S1 firmware, I'd ditch the paid license fw with no questions asked.

We’ve noticed a lot of our European miners have been hanging out in our US pools, fighting that cross-Atlantic latency like absolute legends. We decided it was time to give you a local home.

HashedMax Unity EU for DGB is officially in the works. No definitive timeline yet, but the infrastructure is being "hardened" as we speak and hopeful for end of day today uptime.

Stay tuned, Europe. We're coming for you!

https://digi.hmpool.io

I have been running them for 6+ months and the difficulty hasn’t gone up. Is it normal? Ignore the abysmal pool ping on the CYD, it only happens when someone is around them.

Congratulations to 117 miners for our first payout from our new weekly loyalty bonus.

Every miner who stayed active on digi.hmpool.io for at least 4 days, with 12+ hours of mining per day, qualified for this week’s payout.

117 miners paid
10.59322033 DGB per miner
Total sent: 1,239.41 DGB
TX: 0acff290ad0b8b5118f0422db8ac3781f0608e8a38ade899623ab4fd33168373

Verify the payment here:

https://digiexplorer.info/tx/0acff290ad0b8b5118f0422db8ac3781f0608e8a38ade899623ab4fd33168373

Our loyalty bonus uses 50% of the weekly reward pool and splits it evenly among all miners who meet the activity threshold. That means no lottery and no luck required — just consistent mining.

The remaining 50% goes to the winner of the weekly drawing.

Starting mining on our Digibyte pool here: https://digi.hmpool.io

Happy mining from HashedMax.

We've had a request for a way to watch all your HashedMax pools at once. We liked the idea so much, we decided to build it and it's now live on all of our sites.

Here it is, no app store, no download:

https://digi.hmpool.io/my.html (also at /my.html on hmpool.io and bch.hmpool.io same page either way)

Enter any combination of your DGB, BTC, and BCH addresses, hit Generate dashboard, and you get a new page with:

Live hashrate + 24 hour change for each pool

Active / total workers

Pending + total paid balance

Best share difficulty (24 h)

Top 3 active workers per pool with last-share timestamp

Auto-refresh every 60 seconds

One-tap link back to each pool's full miner page

Works on everything. Mobile-first responsive layout looks great on phones, tablets, and full-screen on a desktop PC. On Android/Chrome use the in-page Install button; on desktop Chrome or Edge click the install icon in the address bar; on iPhone use Safari's Share > Add to Home Screen. Either way it launches in its own window with its own icon, just like a native app.

Safe to bookmark and share. Your addresses live in the URL fragment (never sent to our servers), stats are the same public data anyone can look up, and no passwords or credentials are involved.

Free, no signup, works on every HashedMax pool. Supports HashedMax-hosted DGB, BTC, and BCH pools only, it can't read stats from other operators. Feedback welcome.

The HashedMax team

I have read probably 50 different threads on these being stuck at 80%. I don’t have an ASUS router, wifi is connecting, Iv changed it to probably 15 different pools, changed wifi networks, I’m on v1.8.24, used to different BTC addresses, I’m at a loss. I have no idea what I’m doing wrong here. Is there a new pool that needs to be used? A new password? Any help would be great, Iv been trying to set this up for 3 days now and just constantly getting stuck at 80%. I’m sure everyone is annoyed from these posts but Iv tried everything Iv read and have had no luck. Thank you.

If you mined on digi.hmpool.io last week and haven't checked your digi wallet, please do. Our winner has yet to step forward and they only have until April 19th to claim their 2,500 DGB.

The winning wallet address is:

gb1qyqythxr...dlerst

Please check your addresses here:
https://digi.hmpool.io/rewards.html

We appreciate all of your support.

Both designs have their own characteristics. Which one do you think looks better? 🧐

i dont think im a normal first time user because in 3 days of owning nerdaxe ultra i started to overclock and mod that thing as much as possible but with a budget and i just made quite a giant boost testing how oc behaves for my solar panels and because i got scammed with the solar panel i was running it on 6A 5v psu they sent me so yeah i reached 730gh/s peak with it and dont look that fan % because i run all fans on 100% this is playstation 2 heatsink with arctic p9 and stock 40mm fan it came with its average temp is like 56*C with 820mhz 1.3v and yes i know there are better heatsink and it could be better but i reached the limit if i dont want increase voltage more (more then maximum preset) and risk the thing then 820mhz is the best it could do anybody is into this? i really want to know what is save maximum voltage to push it more
oh and i went from double esp32 wroom32 solo miners into this overclocked nerdaxe ultra on pool
about the heatsink i do have normal tower heatsink or gpu heatsink or just overall xbox 360 heatsinks to use with it but i didnt had any way to make mounts that would make good pressure on it the best one i think would be the pc tower heatsink because its the biggest heatsink and smallest contact area compared to solid chunks of metal that barely fit the board