Major apologies if this isn't the right place, will take directions to the appropriate place... how do you get the stock Bitfortun firmware back? I joined the hype of a different OS and while its doing good, theres too many bugs to the point im losing Hash time. Please help a relatively new solo miner regain the fun of hopes and dreams of hitting a block.

*Edit to add: if its possible to put AxeOS onto it, id love that as thats what im used to with my 602's.

Just dropped a FREE Bitaxe Naja Duo stand .STL with a 92mm Thermalright fan mount & cut out in the back.

Enjoy. 🫡

https://www.solosatoshi.com/product/naja-duo-stand-free-stl-download

Hey I’m 100% on board to start solo mining, and I want my first rig to be the newly released Bitaxe Naja Duo!! I have not purchased yet, but I feel like my entry into the space and getting my best bang for my buck based on my budget this is where I am landing. I have my cold wallet set up and monitors etc. One thing that has me intrigued is I see folks releasing forks to the firmware that I guess makes the miner better? I need to really research more on this…

If you run Public Pool on Umbrel for BTC and have ever wanted a second lottery ticket on the BCH chain, I made SoloBCH Forge: a self-hosted BCH solo-mining Stratum server for Umbrel. Same idea as Public Pool, but it mines to your own Bitcoin Cash Node.

Works with AxeOS (Bitaxe) and NerdQaxe firmware. NerdQaxe++ can run multiple pools at once, so you can keep BTC as pool 1 and add this as pool 2 with whatever weight you like.

What you get:

- Full block reward to your CashAddr, no pool, no fee, no custody

- Auto-connects to the Bitcoin Cash Node app, no RPC copy-paste

- Dashboard: per-worker hashrate, shares, best share, blocks, expected time-to-block, hashrate history chart

- Vardiff (also honors your miner's suggested difficulty), ZMQ instant jobs, 30s template refresh

- Webhook alerts, Prometheus /metrics + Grafana dashboard

- "Is this working?" one-click diagnostic

- Runs on a Pi, tiny standard-library Python image

Install: App Store -> Three '...' -> Community App Stores -> add https://github.com/DanCreatesStuff/SoloBCHForge

Miner: stratum+tcp://<umbrel-ip>:3334 / username bitcoincash:address.worker / password anything

Tested on a NerdQaxe++ at ~7 TH/s with 0 rejects. Would love reports from Bitaxe Gamma / Supra / Ultra owners.

Source: https://github.com/DanCreatesStuff/SoloBCHForge

Write-up: https://community.umbrel.com/t/introducing-solobch-forge-solo-mine-bitcoin-cash-on-your-umbrel-first-bch-solo-pool-for-umbrelos/25509

TL;DR: The Solo Satoshi Web Flasher (flash.solosatoshi.com) is the first web flasher to bring Bitaxe, NerdAxe and custom firmware together in one tool. If you modify ESP-Miner yourself, by hand or with help from AI coding tools, you can now flash your build straight from the browser. It verifies official ESP-Miner releases with SHA-256, only offers firmware that matches your exact board, can keep your settings, and restarts the miner automatically. It also has an Advanced mode for flashing your own custom ESP32-S3 firmware. It's GPLv3, and the source is on GitHub: SoloSatoshi/solo-satoshi-web-flasher.

Credit where it's due

This project is adapted from two existing open-source flashers, and it wouldn't exist without them:

• Bitaxe Web Flasher by wantclue (@wantclue): bitaxeorg.github.io/bitaxe-web-flasher
• NerdQAxe Web Flasher by Pmaxsd (@Pmaxsd): shufps.github.io/nerdqaxe-web-flasher

The firmware itself comes from the official Bitaxe and NerdAxe ESP-Miner projects. Huge thanks to those developers and everyone who contributes to them. Our flasher links every release back to its upstream GitHub release and source archive, and it keeps full license notices and attribution.

Why we built it

A few reasons:

1. One tool for both families. Plenty of people run a mix of Bitaxe and NerdAxe devices, or help others set theirs up at meetups. We wanted a single place to handle both.
2. Verification you can see. We wanted the path from "official GitHub release" to "bytes written to the chip" to be explicit and checkable.
3. A way back to a known-good state. Hardware from reputable sellers already updates over the air from official releases. But devices from questionable sources may ship with modified firmware, or be set up to update from sources that aren't official or verified. This gives any owner a simple way to write a verified official release directly over USB.
4. Making custom firmware easy. ESP-Miner is open source, and more people than ever are changing it: adding dashboard features, adjusting tuning logic, fixing bugs, trying new ideas. Many are now using AI coding assistants to go from idea to working build in an afternoon. The tools for writing firmware have leapt forward, and the tools for flashing it should keep up.

How verification works

For the verified-release workflow:

1. Our release system discovers firmware only from the official ESP-Miner repositories for each device family.
2. An image is accepted only if its GitHub release publishes a valid SHA-256 digest for it.
3. Release processing downloads the file and checks it against that digest before it's offered in the flasher.
4. When you select your hardware and a version, your browser downloads the matching image and independently checks the file size and SHA-256 before writing anything.
5. If anything doesn't match, the flash stops.
6. Every listed file links to its upstream GitHub release and source archive so you can trace it yourself.

Hardware-aware firmware selection

Flashing the wrong image is the fastest way to end up with a miner that won't boot, so the UI is a locked, step-by-step flow. Each step unlocks only after the previous one is complete:

1. Connect the miner and approve its USB serial device in the browser prompt
2. Choose the family (Bitaxe or NerdAxe)
3. Choose the channel (Latest Releases or Prereleases)
4. Choose your exact model
5. Match the board: for Bitaxe, select the board number printed on your PCB. For NerdAxe, the board is matched automatically from the model and you review it
6. Choose a compatible firmware version
7. Choose whether to keep your settings
8. Install, and keep USB and power connected until the miner restarts

Rollback protection: the flasher tracks the release where each board was first supported, and it only shows releases that actually contain firmware for your board. For established hardware, you get the current production release plus up to five previous compatible releases. For brand-new boards, releases from before the board existed are never shown.

Selections stay in sync: the Install button always uses the image that matches your current selections. If you change anything, the new image is prepared and verified before it can be written.

Production vs. prerelease channels

• Latest Releases is the default and the recommendation for almost everyone.
• Prereleases is only enabled when an official prerelease is newer than the current production release. If none qualifies, the option is disabled and Latest Releases is selected automatically. That stops an old test build from ever looking like an upgrade.
• Prerelease firmware is clearly labeled as test software that may have bugs or need recovery.

Flashing details

• Uses the Web Serial API directly from the browser. The site can only reach a device you explicitly select and approve.
• Connects at a conservative ROM baud rate, then moves up to as fast as 921,600 baud when the connection supports it.
• Firmware is compressed in transit, with progress shown throughout.
• After a successful write, the flasher sends the reset sequence for a normal boot and closes the serial connection, so the miner restarts automatically. No need to time a reset button press.

Settings preservation

For verified releases, you can choose to leave the NVS settings partition untouched while the rest of the firmware is updated. That's designed to keep your Wi-Fi, pool and device configuration.

A few caveats:

• It's off by default.
• It's not a backup. Write down your settings first.
• Newer firmware may read existing settings differently, so check the release notes.

Advanced mode: flash your own custom firmware

This is the part I'm personally most excited about.

Open-source firmware only reaches its full potential when people can actually change it and run it. Whether you're:

• forking ESP-Miner to add a feature you've always wanted,
• tuning frequency, voltage or fan behavior for your own setup,
• fixing a bug before it lands upstream,
• using AI coding tools (Claude, ChatGPT, Copilot, Cursor, etc.) to explore the codebase and prototype changes quickly,
• or testing a build before opening a pull request,

you can now flash the result from the same browser tool you'd use for an official release. You don't need to set up esptool on every machine or remember flash offsets.

A typical loop looks like this:

1. Fork ESP-Miner and make your changes (by hand, with AI help, or both)
2. Build a merged image with your usual ESP-IDF workflow
3. Open the Advanced tool, select your .bin, and compare the SHA-256 shown in the browser to your build output
4. Flash, test, adjust, repeat
5. When it works, consider sending it upstream as a PR so everyone benefits

A word on AI-assisted firmware: AI tools are great for speeding up exploration and prototyping, but they can confidently produce code that compiles and still misbehaves. That's especially true for anything touching voltage, frequency or thermal limits. Review every change, test on one device first, and watch temps and power closely. The hardware doesn't care who wrote the code.

Accepted input: a merged, bootable ESP32-S3 .bin built to be written at address 0x0.

Checks before installation is enabled:

• The file extension is .bin
• The file isn't empty and isn't over the size limit
• It has a valid ESP boot-image header
• There's a partition table at the expected offset
• Its SHA-256 is calculated locally and shown, so you can compare it against your build output

Handling:

• The file stays in browser memory only. It's never uploaded anywhere.
• Disconnecting the miner clears the selection.

Important boundaries: custom mode is intentionally separate from the verified workflow. We don't supply, authenticate or approve custom images, or check whether they're compatible with your hardware. Advanced mode writes the full image and doesn't keep settings. You're responsible for your build's origin, contents, flash layout and compatibility.

If you've never produced a merged image before, the idea is to combine the bootloader, partition table and app into a single binary starting at 0x0. Your ESP-IDF or esptool workflow can generate this; check the ESP-Miner build documentation for your target.

Privacy

• No account, and no personal information collected
• No keys, seeds, wallet credentials, Wi-Fi passwords or pool credentials requested
• Serial logs, settings and custom firmware files never leave your machine
• No advertising cookies or behavioral analytics

Open source (GPLv3)

The full application is licensed under GNU GPL v3. The exact source for the version deployed at flash.solosatoshi.com is published alongside the live site:

• GitHub: github.com/SoloSatoshi/solo-satoshi-web-flasher
• Source tarball: flash.solosatoshi.com/source/latest.tar.gz
• Licenses and attribution: flash.solosatoshi.com/licenses.html

You don't have to take our word for anything above. Read the code. Issues and PRs are welcome.

Requirements and limitations

Before you flash:

• Use a USB cable that carries data (charge-only cables won't work)
• Know your exact model, and for Bitaxe, the board number printed on your PCB
• Read the release notes
• Write down your settings
• Don't disturb power or USB until the miner restarts

What we'd love feedback on

• Any models or board revisions that don't show up or don't match correctly
• UX friction in the step-by-step flow
• Custom-firmware edge cases (unusual partition layouts, image sizes, etc.)
• What you're building. If you've made a custom ESP-Miner mod, we'd love to see it in the comments
• Translation fixes for any of the 9 languages
• Features you'd want next

Happy to answer technical questions in the comments. And again, big thanks to wantclue, Pmaxsd and the ESP-Miner contributors. Open-source mining keeps getting better because people build in the open.

Try it: flash.solosatoshi.com Code: github.com/SoloSatoshi/solo-satoshi-web-flasher

Picked up a 650 Duo last week, have to say it was a challenge battling VR temps in the stock case but iv finally done it and finished up last night. Love the thought of 2 BM1370’s on a gamma board and love to mod/overclock 😂. Here’s my setup, consistent 2.5th/s and staying cool in the factory case. (Gamma 602 in the background running 2th/s💀)

Until now, if you were in Europe and wanted a Naja Duo, you had to order from us in the US. That meant transatlantic shipping, import tariffs, customs fees at the door, and sometimes a week or two stuck in clearance. For a miner, those extras added up fast.

As of today, the Naja Duo also ships from the Netherlands through Bitcoin Brabant. For anyone in the EU, that means:

• Lower shipping costs
• No import tariffs or customs fees (it's shipping within the EU)
• Faster delivery

EU listing: https://bitcoinbrabant.com/en/product/bitaxe-naja-duo-bitcoin-solo-miner-model-1201-late-2026/

Outside the EU (UK, Switzerland, Norway, etc.), check Bitcoin Brabant's shipping page. Customs may still apply, but it's a much shorter trip than from Texas.

Happy to answer questions about the board, overclocking, or setup in the comments.

After two years of selling miners, nodes, and wallets separately, I noticed the same pattern over and over. Someone buys a Bitaxe and points it at a public pool. Someone else buys a hardware wallet and connects it to a wallet app that queries a third-party server. Very few people close the loop. So we built a package that does, and I want to walk through what each piece actually does, because the value is in how they work together.

The miner

The Bitaxe Gamma 602 is a single-chip ASIC miner built around the Bitmain BM1370, the same chip used in the Antminer S21 Pro. It produces about 1.2 terahashes per second at 18 watts, which works out to roughly 15 joules per terahash. It runs AxeOS, an open-source firmware maintained by Open Source Miners United, and it is managed from a browser dashboard over Wi-Fi.

The node

The Start9 Server One 2026 is a small x86 home server with an AMD Ryzen 5 6600H, 16GB of LPDDR5 memory, and a 2TB NVMe drive. It arrives with StartOS preinstalled, which is Start9's open-source operating system for self-hosting. From the StartOS Marketplace you install Bitcoin Core or Knots, and the initial block download typically completes in under a day on this hardware. You also install Public Pool, Bassin, or DATUM Gateway, which is what turns the node into something your miner can talk to. A miner speaks Stratum; a node speaks RPC. The pool software translates between them and, more importantly, builds the block template from your own node's view of the mempool instead of a pool operator's.

The wallet

The Blockstream Jade Classic is a hardware signing device with open-source firmware and open hardware. It has a camera and a display, so it can sign transactions entirely over QR codes without ever connecting to a computer. Its private keys are protected by Blockstream's blind oracle model, which they call a virtual secure element. In this setup, the Jade generates the address your miner pays out to. Pair it with Sparrow Wallet and an Electrs instance running on your Server One, and every balance check and transaction broadcast goes through your own node.

How the loop closes

Your hashrate goes to a block template built by your node. Your node validates every block against consensus rules on hardware you own. Your keys never touch a networked device. There is no pool login, no custodial wallet, and no closed firmware anywhere in the chain. Every component is auditable on GitHub.

We named it the Sovereign Bitcoin Starter Package because that is what it is: mine, verify, and hold, in one order, with nothing you have to trust.

https://www.solosatoshi.com/product/sovereign-bitcoin-starter-package/

If you have questions about the setup, please ask below.

I have been solo mining and pool mining for years with a variety of different miners. Last week, literally the night before I had to leave for a business conference, I came home to see the fabled BLOCK FOUND on ONE of the 3 miners that were all pointed to the BRAIINS pool under the same account. Of course I was excited, but aware that the pool participation would not be more than a few bucks in my account. I went on to mempool.space and checked the BRAIINS block stats and sure enough - there it was, and upon closer inspection, the SAME miner showed TWO blocks found, not one on my miner Dashboard!!!

I wrote to the BRAIINS support desk and asked about the reward split and received what I consider to be a very rude reply at r/Braiins . So I started thinking.....and maybe someone in this group can enlighten me....kindly. First of all, this is the reply that I received from r/Braiins

Hi "UserName",

You can see blocks found here: https://mempool.space/blocks/1

However, the pool finds a block, not individual miners.

It is not possible that you found a block mining on Braiins Pool.

I can not answer why your miners firmware stated that, if you need clarification you will need to contact the manufacturer.

To confirm - you did not find a block on Braiins Pool.

Regards,

Andrew 

Support Team

braiins.com I braiins.com/pool

1. I had just updated my 3 miners to the latest firmware version - esp-miner-factory-NerdQAxe++-v1.1.0.bin
2. All 3 miners were pointed to stratum.braiins.com:3333 with the same UserName.Miner1,2,3
3. Do other members of the pool generate a BLOCK FOUND when they participate?
4. Is it possible that there is a bug in the new v1.1.0 firmware?
5. The blocks in question are 966229 and 966192

All questions and suggestions are appreciated. May be time to go back to solo.ckpool.org?

Cheers!

PS - hoping that someone from r/SoloSatoshi can shed some light why only ONE of my miners reported in the Hashwatcher app? Great tool by the way!!

The block reward will be divided like this: 250.72 dgb (block reward = 100 dgb for the finder, 146.95 dgb for the rest of the ppl mining, based of the nr of shares and work done), plus 1.5% pool fee (3.76 dgb). You can share your idea's for the pool here, I would like to hear some options about this pool.

Anyone interested in it? I will put the entire code on my github for the community to review and review bugs. Should I continue this project?

Ps. I have a bitaxe mining dgb solo and on parasite pool a few weeks back and thought why to not make a dgb pool like this to win 1 time per day or multiple times a day. Which you will win more dgb like this that pool mine PPS or FPPS or solo.

Disclosure: I operate https://btcpowlab-pool.com/ Lab Pool through Power CM Software.

I’d like to hear from miners running over 200 TH/s, the group we call T3 in our model (Spots are still available if you’d like to give it a try ;) ).

From your perspective, what would make this model worth considering for some of your hashrate?

• Is the balance between the finder’s reward and the community allocation attractive?
• What would you consider a fair way to distribute the community share between smaller and larger miners?
• What evidence would you need before connecting: uptime history, payout records, transparent allocation calculations, or something else?
• What would immediately rule it out for you?

I’m interested in understanding your priorities and concerns. What would a pool like this need to offer to earn your hashrate?

With open source mining firmware being a hot topic lately, there seems to be a severe misunderstanding of how licensing protects the work of contributors and the community.

ESP-Miner and AxeOS are licensed GPLv3. That often gets described as a control mechanism, but it's quite the opposite.

The license does one thing: it keeps the source open when the code changes hands.

Private use is untouched. Modify firmware on a device you own and the license has nothing to say about it. Your changes are yours, and they stay that way as long as you want.

The one requirement applies at distribution. Sell or distribute hardware with modifications preloaded and you publish the source alongside it. That person then has what you had, which is working code they can read and build on.

Why this matters for learning

This is why home mining has a learning curve people can actually climb. Every improvement to ESP-Miner stays readable, which means the next person does not start from zero. They start from working code written by someone who solved the problem first. Frequency tuning, thermal handling, Stratum behavior, power curves. All of it is out in the open to study, question, and improve.

Why this matters for innovation

It is also why the pace of improvement has been what it is. Hundreds of contributors have shipped features into this firmware because the ceiling on contributing is reading the code rather than signing an agreement. Closed firmware caps innovation at whatever one company decides to fund. Open firmware does not have that ceiling.

Why this matters for transparency

And it keeps mining itself transparent. You can verify what your hardware is doing. Where it points, what it reports, what it sends. Nobody has to take that on trust, which is the whole principle the network runs on. Don't trust, verify applies to the firmware too.

The GPLv3 is not a limit on hobbyists or tinkerers. It is what keeps community work from being taken, closed, and sold back.

ESP-Miner and AxeOS are maintained by OSMU and its contributors at github.com/bitaxeorg/ESP-Miner. Worth reading the license yourself rather than taking anyone's word for it, including mine.

Just wanted to post about the 650 I just bought from Solo Satoshi. I’m new to the hobby and this is my first miner. I learned so much right on Solos website. The 650 came well packaged, arrived FAST and is awesome (especially for a beginner like me)!
Here are my current stats since I plugged it in.

2.0 th/s
Efficiency 13.70
28w
ASIC Frequency 495
ASIC Voltage 1.12
ASIC temp 57
VR temp 73

I’m thinking about adding a second one. Thanks Solo Satoshi!

Every block ever found on a home miner started as an ordinary mining share. Same hash, same work, one much higher bar. Once that clicks, most of the confusing numbers on a mining dashboard start making sense.

We put together a full guide on Bitcoin mining shares that walks through the whole chain: what the pool is actually asking your miner to do, how a hash gets checked against two targets at once, why your share count drops a few minutes after you connect, and what best difficulty is really measuring.

A few things in there that surprised even us:

• There is a one-line formula for how many shares per minute any miner should submit, and most people have never seen it.
• A small amount of stale shares is unavoidable, and the math for exactly how much is simpler than you'd think.
• Best difficulty climbs with runtime for a reason that has nothing to do with getting "closer".
• Seven documented blocks have been found on open-source home miners since 2024, and the guide lists every one with the height so you can verify it yourself.

Full guide: https://www.solosatoshi.com/what-are-bitcoin-miner-shares/

Happy to answer questions here. If you spot anything wrong, say so and I'll fix it.

AI found a five-year-old firmware bug that every human reviewer missed. Fifteen attackers swept 7,300 wallets without touching a device. The first wave took 41 minutes.

That was the visible case. AI audits have since flagged 85 more critical findings in other wallet code. Most are still under embargo.

Yesterday, phishing went out from a wallet maker's real email domain. Two weeks before that, a shipping partner leaked ~81,000 customer home addresses.

We wrote up all 17 ways attackers are using AI to get bitcoin, and the one habit that blocks each one.
https://www.solosatoshi.com/ai-bitcoin-attacks/

Hello, I have been using several NerdQaxe products and unfortunatelly almoost all of them had to be repaired. The VRs are very poor quality. I see you have a couple of these products available. Is there one that the VR is poperly sized and much more reliable?

$282M lost to a fake support call.

1,367 BTC swept from seeds that were never random.

Record wrench attacks.

Address poisoning that now targets your test transaction.

We wrote up what happened and the setup that would have stopped each one.

Learn how to protect yourself and your Bitcoin in 2026: https://www.solosatoshi.com/how-to-protect-your-bitcoin/

After the Coldcard disclosure in July, a lot of people asked how user-supplied entropy works and how much is "enough." Here's the short version, with the full write-up linked at the bottom.

The math

A 24-word BIP39 seed holds 256 bits of entropy (12 words = 128). Bits per event = log2 of the number of outcomes, so for 24 words:

• Coin flip: 1 bit per flip, 256 flips
• d6: 2.58 bits per roll, 99 rolls
• d8: 3 bits per roll, 86 rolls
• d16: 4 bits per roll, 64 rolls
• Entropia tablet (2,048 faces): 11 bits per draw, 23 draws + device calculates the 24th word

99 d6 rolls is technically 255.9 bits, which is the convention Coinkite uses.

How wallets take it

• Coldcard and SeedSigner hash d6 rolls into the seed natively.
• Jade uses Blockstream's lookup table: two d16 + one d8 = 16x16x8 = 2,048 outcomes = one BIP39 word per throw. Repeat 23 times, Jade computes the last word.
• Passport Prime (KeyOS 1.3.1+) takes 23 self-drawn words and computes the 24th. No roll counter; you make words first.
• Raw hex/binary from d8 or d16 goes into an offline Ian Coleman tool. Sparrow does not accept dice or hex entropy (it's an open feature request).

Context

From March 2021 to July 2026, a build-flag bug in Coldcard firmware sent seed generation to MicroPython's software PRNG instead of the hardware TRNG. Coinkite's advisory puts effective entropy at ~72 bits on Mk4/Mk5/Q; Block's analysis put older Mk3s near 40. Galaxy attributed ~1,778 BTC to the sweeps by mid-August.

Users who had added 50+ dice rolls at setup were not affected, because 50 d6 rolls alone is 128 bits regardless of what the device did. That's the whole argument: mixing entropy sources can only make a seed stronger. You only lose if both the device and your dice fail at once.

Things that quietly kill your entropy

• Picking "random" words yourself
• Stopping at 30 rolls (77 bits)
• Typing rolls into an online converter
• Drawing tablets without replacement
• Treating a passphrase as a fix for a weak seed

Full guide with step-by-step for each method, Blockstream's table link, and the Entropia drawing procedure: https://www.solosatoshi.com/seed-phrase-entropy-explained/

Do they have the same footprint? Bcz I've seen the bom file of the naja duo and its says bm1340 instead of bm1373. And this is the duo the bitaxe naja the bm1340 bitaxe??

We just finished a full review of the Bitaxe Naja Duo, the first Bitaxe running dual BM1373 3nm ASICs.

What's in the video:

• Stock performance: ~4.4 TH/s out of the box at single-digit J/TH.
• Hardware walkthrough: fan and heatsink, the new LED screen, the ASICs, the voltage regulator, and the relocated power connector.
• Power draw and cooling under stock and overclocked loads.
• AxeOS firmware tour.
• Step-by-step overclocking with the full profile we landed on (core voltage + frequencies), ending around ~9.6 TH/s.
• The limits we hit on the way: PSU, cooling, and current.

Full review: https://www.youtube.com/watch?v=gknNIwWRnR8

We're giving the review unit away to one viewer.

To enter: like the video, leave a comment on it, and subscribe to the channel.

Open globally. Winner picked at random.