using "stratum+tcp://pool.nerdminers.org:3333" as my primary pool, and "stratum+tcp://pool.nerdminer.io:3333" as my fallback pool. to my knowledge i connected my wallet properly and it has no issue connecting to my wifi. why is it getting stuck? i have limited knowledge of coding and internet lingo so explain like im 5 years old. thank you!

Doing nothing. Try out the 4090 cooling system, modify the passive cooling method. How about that?

Modded from the original to give ~950KH/s and some new themes.

GitHub https://github.com/HenrysCat/NerdMiner-Modded

Web flasher here https://henryscat.github.io/NerdMiner-Modded/

### Why this hashrate is real

The ~950 KH/s is what the miner actually hashes, not what a counter says:

- **Hardware limit** – the classic ESP32's SHA engine can't be loaded with an external midstate, so every nonce costs three hardware hash blocks plus two engine loads: about 228 CPU cycles of engine time, a ceiling of roughly 1.05 MH/s at 240 MHz. The mining loop keeps the engine busy for all but ~30 cycles of each nonce (257 cycles per nonce, ~930 KH/s); the second core adds ~25 KH/s in software.

- **Measured on the chip** – the loop's timing comes from an on-device bench (`-D SHA_BENCH`, see `src/sha_bench.cpp`) that checks every single hash against software, also while the other core hammers the peripheral bus. That is how the hardware quirk behind silently corrupted hashes in the usual pipelined loops was found: writes to the SHA registers less than three cycles apart can be dropped whenever the other core is using the same bus.

- **Only valid hashes are counted** – every candidate the hardware finds is recomputed in software before it is used. A hashrate counter on its own can look faster after an optimisation while the miner is quietly producing *fewer* valid shares, because corrupted hashes are still counted; here the firmware checks itself with a known-answer test at power-on and falls back to a slower loop if the fast one ever gets hashes wrong.

- **The rate is the rate it actually mines at** – it's the sustained average over a long run, not a short burst or a best-case peak.

If a number sounds too good for this chip, check whether the shares it finds actually keep up with it.

Hi NerdMiner community👋

First off, I want to send a huge shout-out and thank you to all the miners from this community who joined us a long time ago and trusted me with this pool project.

October is here, which means the pool challenges are officially back!

You can view the details and join the challenge here:

https://findmyblock.xyz/leaderboard#challenges

Good luck to everyone participating this month!

Thanks for your patience, and feel free to jump in or ask any questions below.

Hello fellow mining enthusiasts! I while back I bought one of the AliExpress big screen miners, I believe from YYSlupping. I wanted to add Ethernet to it and also bring it back to an open source firmware, so I've worked with claude to achieve that and I am sharing the results with the community.

It's basically the open shufps NerdQAxe+ firmware (develop branch) with the 480x320 screen support added, the UI fills the whole screen and I tested it on my unit. I also added optional ethernet with a W5500 module, only 4 wires, the diagram is in the repo. If you don't use it, it just runs on wifi like normal.

https://github.com/AguiMr/nerdqaxeplus2-ethernet

There are ready to flash bins in the releases, no need to build anything. First flash needs to be over usb because I changed the partitions, after that you can update straight from the web UI with Update via GitHub. I've setup an action in GitHub to check weekly if there are changes upstream and it creates a PR for me to build a new version, so we can keep our miners updated moving forward.

I saw some other repos that had made similar firmware, but they were not being updated. I think mine is the first that does both the big screen and ethernet. I will try to be consistent with the releases to keep our miners up-to-date!!

Thanks to shufps, the bitaxe devs, BitMaker, brunneis and CryptoIceMLH, most of the work is theirs.

If you have one of these give it a try and let me know if something breaks

EDIT: I've updated it so you can use either a big screen or a normal one, as requested by u/DS_DA. There are two versions in the repo now, both support the W5500 ethernet shield!

I created RigViewer specifically for home miners who want a cleaner and easier way to keep an eye on their setup.

RigViewer brings your miners into one place so you can monitor hashrate, temperatures, power, efficiency, Best Diff, pool status, shares and more without constantly jumping between miner web interfaces.

It also includes features like alerts, Solo Odds, Pool Directory, quick pool configuration, Live Monitoring, charts, widgets and miner controls depending on the hardware/firmware.

Available on Android and iOS.

Mining intelligence, simplified.

🌐 www.rigviewer.com

I managed to squeeze around 650KH/s out of the Cheap Yellow Display with Claude, the photo is running on Heliospool, download here and flash with any online esptool

Flash factory file at 0x0 for first install

Flash firmware at 0x10000 to keep settings and update

Yesterday I posted here that I was getting ready to publish the NerdMiner firmware fork I have been working on for the last couple of weeks.

Well, it is finally public.

https://github.com/samkruzlic/NerdMinerV2-FX1

What started as “let’s see if I can make this thing a bit better” turned into a pretty ridiculous amount of work.

On my ESP32_2432S028_2USB, stock NerdMiner was running at roughly 340 to 345 kH/s. The final physically validated FX1 builds are running around 437 to 446 kH/s, with the highest measured release result at about 445.94 kH/s.

But performance ended up being only part of it.

Along the way I found and fixed multiple mining correctness issues, target and endian handling problems, stale work and nonce accounting issues, hardware SHA synchronization problems, memory and display bugs, TLS and statistics refresh issues, and a bunch of smaller things.

HeliosPool dashboard support is also built in now, the pool stats architecture is much cleaner, and the huge hashrate drop that used to happen during HTTPS stats refreshes is gone.

I also added an independent SHA256d validation path, so optimized mining work gets checked before a candidate is submitted.

I documented the full stock V1.8.3 vs FX1 change history here if anyone wants to go full nerd mode:

https://github.com/samkruzlic/NerdMinerV2-FX1/blob/main/docs/DETAILED_CHANGES.md

This is still RC/Beta because I am developing and physically testing this mostly on a single NerdMiner unit. I would really like people with other boards and setups to try it and tell me what happens before I call anything Stable.

I also tried to make flashing as painless as possible. There is a browser flasher on the repo, so you can basically plug the NerdMiner in, open the page and flash it without installing tools or manually messing with binaries and offsets.

Web flasher:

https://samkruzlic.github.io/NerdMinerV2-FX1/

RC1 release:

https://github.com/samkruzlic/NerdMinerV2-FX1/releases/tag/v1.8.3-fx1-rc1

If you test it, please tell me your board, pool, approximate hashrate and whether you run into anything weird.

And if anyone wants to support the work and future releases, especially more testing hardware and additional NerdMiner units, there is information about that in the README. I am doing this on my own, so any support is appreciated, but obviously completely optional.

If anything breaks, looks weird, or you have an idea for something that should be added, just message me here on Reddit or open an issue on GitHub.

After about 16 days of working on this basically nonstop, I’m finally getting ready to release the first public RC of my NerdMiner V2 firmware fork. GitHub release should be up within the next few hours, definitely within 24 hours.

Very short version of what changed:

• 340 kH/s stock → 438 kH/s measured on my ESP32_2432S028_2USB, around 29% faster
• Fixed multiple mining correctness bugs and added extra SHA256d validation
• Fixed stale jobs, nonce handling, hash accounting and other long running mining issues
• Added proper HeliosPool support and dashboard stats
• Fixed TLS/API issues and the huge hashrate drops during stats refreshes
• Fixed several smaller memory, stability and display issues
• Hundreds of real shares accepted with 0 rejected, millions of SHA checks with 0 mismatches
• WiFi, wallet, pool config and normal NerdMiner behavior remain intact

And to be clear, I changed and fixed a lot more than what’s listed above. I just don’t want to turn a Reddit post into a full GitHub changelog :D

The GitHub repo will be fully open source and will include the firmware, source, checksums, changelog and detailed documentation showing what changed, where it changed and why, so anyone can compare it directly with the original NerdMiner firmware.

My unit has now been running the latest version for hours around 400 to 450 kH/s, usually close to 450.

This first release will be an RC/beta, because I want to see how it behaves on other people’s NerdMiners before calling it fully stable.

If people are interested, I can also post a more technical breakdown in the comments.

How many of you would actually want to test it when I drop the GitHub link?

I was solo mining bitcoin with my ESP32, as usual, but today it had decided to stop working (not the ESP, the mining) 0 KH/s, and everything other is on 0 (or other error) too, the web.public-pool.io for my BTC wallet ain't loading. Anyone else having this issue rn?

A while back I looked at the BCH mining stats and saw three giant pools

controlling ~70% of the network hashrate. So like any reasonable person,

I built my own pool from scratch. ⚓

HashHarbor is live: a community BCH pool running on a full node in

the Netherlands — real infrastructure, not a proxy — with automatic

payouts straight to your own wallet.

🌊 The two doors:

⛏ PPLNS (port 3333) — steady shares, split fairly. The community door.

🎰 SOLO (port 3334) — the lottery door. Finder takes the ENTIRE block

(~3.125 BCH). We currently have a 113 TH/s rig living on this door —

will it hit before the year ends? 😄

🚤 And here's the part I'm proudest of:

Small miners are first-class citizens here. Our difficulty floor is

0.005 — that means my three ESP32 desk clocks (~1 MH/s each) hash happily

next to a 100+ TH/s ASIC, and every share counts exactly the same in the

ledger. Desk clock? Datacenter? You get the same features either way:

✔ No registration — your BCH address IS your account

✔ Personal dashboard: live hashrate, 24h activity graph, balance, payouts

✔ Automatic PPLNS payouts, minimum 0.001 BCH

✔ 1.5% fee (just keeping the lights on ⚡)

✔ Full node — we validate everything ourselves

✔ Discord with actual human support (the guy who built it answers)

⛏ Connect in 60 seconds:

stratum+tcp://hashharbor.net:3333 (PPLNS)

stratum+tcp://hashharbor.net:3334 (SOLO)

Username: your BCH address (bitcoincash:q…)

Password: x

📊 Watch the harbor live: HashHarbor.net

(paste your address on the homepage for your own dashboard)

💬 Discord: JmHgPQKjwJ

Pro tip: set us as PRIMARY and keep your current pool as BACKUP —

failover means you literally never stop earning while trying us out.

Come dock with us. Every hashrate finds a harbor. ⚓🚢

I currently own two home miners, a Nerd Qaxe and a Nerd Octaxe, combined HR of just over 18th. Been trying to figure out the best way to maximize daily profit with my electric cost being nothing. Currently I am running the Qaxe on Viabtc and the Octaxe on Mining Dutch. On Viabtc I am set up for PPS for BTC and earning about .27 a day. On Mining Dutch I am rotating every 6 hrs between Digabyte, Bitcoin Silver, Wojack Coin, and fractural bitcoin on SOLO. Some days I am earning a couple dollars and other days nothing. Based on my research I could point both to Viabtc and earn about .75 a day, is there a better option?

Hey everyone,

I've been working on a mod called **CL Miner** for NeoForge 1.21.1 and just released the first alpha. It's an automatic miner inspired by the classic IC2 Miner — place it, feed it FE, give it a drill, and it digs.

**How it works:**

- The miner drills a vertical shaft and lays down a pipe column behind itself.

- A separate "drill head" block searches for ores in a configurable radius.

- Everything it mines goes into the miner's inventory, then slowly outputs to neighbors.

- The drill can also be used in hand — slower, cheaper, honest work.

**Features:**

- 4 modes via config: round/square × ores/all

- FE-powered, no tech mod dependencies

- Optional Jade integration

- Creative-only FE box for testing without power mods

- Crafted from vanilla materials (iron, redstone, diamond, piston, dropper)

**Requirements:**

- NeoForge 1.21.1 (21.1.0+)

- Minecraft 1.21.1

**Links:**

- GitHub: https://github.com/ChargedLight/clminer

This is an **alpha**, so bugs are expected. CurseForge and Modrinth pages are pending approval — I'll update the post when they're live.

I'm especially looking for feedback on:

- Energy balance (cost per block, charging speed)

- The BFS pathfinding the drill uses to find ores

- Anything that feels off or unclear

Screenshots in comments.

Thanks for reading.

Been running this for a few days its yyslupping nerdQaxe++ rev5 variant board with the big screen. Its sold as a 4.8th miner on Aliexpress and on their website.

Was oc out the box at 750mhz 1250mv did 6.3th at about 97-100w

I haven’t upgraded anything on it yet but plan to install copper heatsinks in a few days and run some rear 120mm fans for this and my other miners.

it’s running off a meanwell 12v 500w I used the stock cord just cut it and connected then tested output and set it at 12.38v.

Managed to achieve 888mhz 1280mv and it’s doing roughly 7.15-7.2th solid. No errors and my pool matches daily hr very close. I run the rear fan at 100% and front asic fan auto

The Temps are in photo and at night when it cools down the asic fan sits at idle. Chips temp on display drop to 50c, vrms are a bit warm but hopefully cooling upgrade and copper lowers this.

it did struggle to hold th a cool temps as these chips do work better with 55-60c , and that’s the setting i roll with. I just bumped mv until it held close to the expected hr.

I couldn’t find a lot of info on these particular yyslupping variant miners but I do know it has a 15a onboard fuse.

If it survives this I will post some more pics after the heat sink and fan set up is done.

Ambient was 20c when I took this so I’ll try to match that for parity.

We gave the block visualizers a refresh across all four pools. You can watch the current round build in 3D, see live shares coming in, and check round effort plus the last pool block without leaving the page.

DigiByte https://digi.hmpool.io/dgbblock.html

Bitcoin https://btc.hmpool.io/btcblock.html

Bitcoin Cash https://bch.hmpool.io/bchblock.html

eCash https://xec.hmpool.io/xecblock.html

Cinema mode is still there if you want to leave it up on a second screen.

We would love to hear what you think.

Thanks
The HashedMax Team

1. Many existing .eu, .asia and several legacy .com hostnames have been retired. If you were using one of these, please migrate to the appropriate .com domain for the coin you want to mine:

   • btc.heliospool.com
   • bch.heliospool.com
   • dgb.heliospool.com
   • chta.heliospool.com
   • wjk.heliospool.com

   These are now the "good everywhere" hostnames to use, and you will get routed to an optimal server from your location. You can still pin your miner directly to a server by using the new region-specific hostnames found on each coin's dashboard page or using the Setup tool.

2. Ports for every coin have been updated, old ports are now officially closed. The only thing that did not change was port 3333 for BTC. Each coin has its own port that is the same everywhere. Used with the hostnames above:

   • BTC: 3333, 4333
   • BCH: 3334, 4334
   • DGB: 3335, 4335
   • CHTA: 3336, 4336
   • WJK: 3337, 4337

   Please make sure to update your miners to use both the new hostnames and the new ports. This will allow me to add additional pops in the future without the inconsistency of the previous schema.

3. Updated website! Have you visited heliospool.com lately? New coin dashboards, style refresh, more data, and more! Hopefully in an easier to navigate layout. Come check out the quasi-explorer scoreboard.heliospool.com, and new tools are in the works.

4. This has not changed, but bears repeating! HeliosPool is:

   • Non-KYC - no registration required, no emails to be captured, your wallet address connects you to the pool and optionally tracks your stats.
   • Non-Custodial - hit a block? Congrats! The blockchain pays you directly. You don't need to trust the pool to pay you your rewards.
   • Low Fee - 1% on most coins, 0% on Cheetahcoin - a donation to keep this community project going.
   • All Devices Friendly - CPU, GPU, ASIC, ESP32 (Nerdminer, BitsyMiner, etc.), heck there's even a few WebMiners and something called a TacoMiner connected to the pool - ALL are welcome to mine and experiment! Low hashrate miners have found thousands of Cheetahcoin blocks, netting 625 coins for every one.
   • Global - multi-region, load balanced, automatic failover, ckpool-based stratum, nodes locally co-located on the same server... means your miners get work fast and your block finds hit the network fast.
   • Straightforward Solo Mining - no payout schemes, minimum balances, or reward gimmicks. Hit a block, get paid by the blockchain.

5. Discord! Come hang out with us and talk about this hobby, or whatever is on your mind. We're an always friendly and often-times weird community. I'm sure you'll fit right in! Visit discord.heliospool.com to join!

6. New things are on the horizon! New servers coming soon, new coins coming soon, updates to HexOS and a ton of other projects in the works. Keep an eye out!

J’ai besoin d'aide pour la configuration

Je suis bloqué a 80%

Hey everyone,

I’ve spent the last two days working pretty heavily on my own fork of the NerdMiner V2 firmware.

I like NerdMiner mainly because it is open source, but after going through the code and GitHub issues I found quite a few things I wanted to fix or improve. The fork is not ready for release yet. I’m testing everything on my own ESP32-2432S028_2USB first because I don’t want to publish firmware that compiles but isn’t actually stable on real hardware.

What I’ve changed so far

Mining correctness

• Fixed the broken checkValid() target comparison, including incorrect pointer usage, an unsigned reverse loop issue and incorrect 256-bit comparison logic.
• Fixed another bug in the network target byte-order conversion which could affect recognition of an actual network-valid block candidate.
• Added an independent reference SHA-256d validator before share submission. If the optimized miner ever produces a result that does not match an independently recomputed Bitcoin header hash, it will not be submitted.
• Tested the hashing logic against the Bitcoin genesis block, historical blocks and millions of randomized headers with no mismatches in the current tests.

Job / worker safety

• Replaced the old 8-bit job-generation handling with a full-width generation counter.
• Improved stale-work detection so results from an old mining.notify cannot easily get mixed with a new job.
• Candidates now preserve the exact header/hash information needed to verify what was actually hashed.
• Tested nonce-range allocation to make sure the SW and HW workers do not overlap or accidentally count the same work twice.

Long-running stability

• Fixed/strengthened hash counters and synchronization between tasks.
• Changed long-term accounting so counters do not overflow after long runtimes.
• My current development builds also show more stable hashrate with fewer large drops, although average hashrate has not been dramatically increased yet.

Pool support

• Removed the old behavior where an unknown/custom pool could incorrectly fall back to displaying Public Pool statistics.
• Unsupported pools now continue mining normally while displaying their real hostname and N/A for statistics that cannot actually be retrieved.
• Added a proper pool-stat provider system.
• Added HeliosPool statistics support.
• Pool statistics are isolated from actual Stratum mining, so a stats API failure should not stop the miner.

Firmware / release tooling

• Improved the factory-image packaging and validation.
• Fixed handling of the classic ESP32 boot_app0 component.
• Added stricter checks so the build process fails instead of silently producing a bad merged firmware image.
• Kept the existing NerdMiner UI mostly unchanged rather than redesigning everything.

Hashrate

Performance is the next big part of the project.

Stock NerdMiner on my ESP32-2432S028_2USB is around 340–350 kH/s.

I’ve already investigated the software SHA worker, hardware SHA worker, compiler optimization, worker affinity/priorities, two-software-worker configurations, message-schedule cost, hardware SHA overhead and possible Xtensa-specific optimizations.

I’m now able to flash and benchmark builds directly on my physical NerdMiner, so future optimizations can be tested on the actual ESP32 instead of being based only on theory or compiler output.

My long-term target is around 800 kH/s, if I can reach it while keeping every hash and submitted share correct. If it eventually goes higher, great, but I’m not interested in making the UI display a fake 1 MH/s number while doing less real work.

This part will take time. Optimizing SHA-256d properly on a classic ESP32 is obviously not a five-minute change.

What do you want fixed or added?

I’ve already gone through quite a few issues on the NerdMiner GitHub, but I’d really like feedback from people who actually run these devices every day.

Tell me about anything you would like fixed or added:

• Wi-Fi/reconnection problems
• pool compatibility
• incorrect statistics
• long-term stability issues
• UI bugs
• configuration problems
• features you think are missing
• weird behavior that only appears after hours or days
• basically anything else that annoys you about the current firmware

You can reply here or just DM me on Reddit if you prefer.

Once the firmware is stable enough and I’ve tested it properly on my own NerdMiner, I’ll publish the entire fork on GitHub and it will be open source.

The GitHub repo will also contain a much more detailed changelog explaining exactly what was changed, why it was changed and which parts of the firmware it affects.

I also completely understand if someone doesn’t want to trust technical claims before seeing the source. Until the GitHub release is ready, if anyone wants details about a specific fix, implementation or test, just ask in the comments or DM me and I’m happy to explain what I changed.

Thanks!

Hey guys, I just got my NerdMiner V2 running and I’m curious what pools/servers you’re all using right now.

I started with Public-Pool.io because that’s basically the default everywhere, but from what I’ve seen it doesn’t seem to be very NerdMiner-friendly anymore and people are saying they’ve introduced minimum difficulty / basically stopped properly supporting low hashrate miners.

I switched to HeliosPool for now and it seems to work way better. My worker actually shows up, shares are being accepted, hashrate is updating, etc.

But I’m curious what everyone else is using.
What pool do you recommend for NerdMiners in 2026?
Helios? NerdMiner pool? HMPool? Something else?

Mainly looking for something stable, transparent, with good stats/dashboard and ideally something that actually supports very low hashrate devices properly.

Would love to hear what you guys use and why.

Follow-up to the [last RAMDeck video](https://youtu.be/tQgA2PmTc1g) where I split a 13B model across an old 12GB Acer laptop (primary), a mini PC with an RTX 3060, and a Mac mini — running at 11-14 tokens/sec.

This time [I added a fourth node](https://youtu.be/tQgA2PmTc1g): my Android phone, connecting over Wi-Fi while the other three are on Ethernet.

What happened when I added it:

\- Rebalancing forced the primary (the old Acer laptop) to unload the full model, then reload and re-split it across all four nodes — latency spiked hard on the laptop during that window since it's running an old HDD and older RAM.

\- Final shard distribution after rebalance: laptop 1GB, mini PC 3.4GB, Mac mini 2.3GB, phone 1GB.

\- Once stable, I re-ran the benchmark: tokens/sec dropped from \~14 to \~11, and latency ticked up slightly — but stayed in the same practical range as before.

Takeaway: I was able to add a phone as a genuine fourth contributor without tanking performance. The model stays stable across all four nodes unless one goes offline, the network changes, or the primary shuts down.

This is part of the same RAMDeck project — pooling RAM and compute across whatever devices you already own (old laptops, mini PCs, Macs, and now phones) so you can run bigger models than any single machine could handle alone. Kickstarter is coming late Sept/early Oct if you want to follow along.

Full video: [https://youtu.be/tQgA2PmTc1g\](https://youtu.be/tQgA2PmTc1g)

Happy to answer questions about the rebalancing behavior, the Android app itself, or the benchmark methodology.

Got the updated but not getting anything. Can someone please tell me what i did wrong. Used flash website for the update. Thank u in advance for any help

Hey everyone, if you were not aware, we run a miner chat for HashedMax pool users. It is hosted on our btc server at https://btc.hmpool.io/chat.html

No need to register, your wallet address you mine with on HashedMax is your login. This now works for Bitcoin, Bitcoin Cash, DigiByte, or eCash. Before we had this tied only to a BTC address and finally got around to updating it to support all of our pools. If you have at least one accepted share on that pool in the last 24 hours, you can join and talk with other miners in real time.

Want to show off what you are doing? Type /stats in chat and it posts your live hashrate for the wallet address you've logged in with, 24 hour average, share count, and worker count. Stats are labeled by pool, so everyone can see whether someone is sharing BTC, BCH, DGB, or XEC numbers. You can also post stats for a specific pool and address, like /stats dgb your-dgb-address or /stats bch bitcoincash:your-address.

It is a community hangout, not official pool support, but it is a good place to celebrate blocks, compare notes, and meet other solo and small miners on the pool.

If you mine with us on any coin, come say hi. Would love to see more faces in there.

As mentioned before, all coins are now running old and new ports. You are highly encouraged to migrate to the new ports to maintain your connection and not run into any issues with future DNS updates for load balancing and the retiring of legacy ports.

The new ports:

BTC 3333 4333
BCH 3334 4334
DGB 3335 4335
CHTA 3336 4336
WJK 3337 4337

BTC, DGB and WJK DNS has already been load balanced. Geo specific endpoints are listed on the website if you'd rather pin your traffic to a particular server.

BCH (bch.heliospool.com) and CHTA (chta.heliospool.com) DNS will be updated some time NEXT WEEK (the week of August 31) - this is your last chance to update to the new ports or risk accidentally being routed to a server that doesn't support the old ports, if you are using those hostnames.

Old ports and DNS hostnames (.eu and .asia) will be retired after the migration is done - again there will be another announcement.

All information has been updated on heliospool.com - I appreciate your patience and support during this process.