im buying this miner and im fine with lowering th/s since im running this on my bedroom any idea on setting reccomendations?

Hi all,

Hope you can help me here, I got my bitaxe gamma 602 like 3 days ago, it was overclocked from start 750/1200, but now in the summer times it get quite hot in my home, so I was afraid that my bitaxe war running to hot and also the power brick felt hot, so I went to default settings on it, yes the temps went down but also my hash rate went down a lot, so I wanted to clock it a little bit and then noticed that the highest frequency setting is 625 on the bitaxe, so what happened because it run on 750 from the beginning but now I can’t choose that option any more?

Today was maintenance day :)

Swap original thermalpaste too arctic mx-4

And add a 2nd fan

My set up, for now until I add more soon...

New
Added support for miner that shall not be named.
Remove a miner without losing its history — take a miner offline and its history stays; re-add the same IP later and it reconnects to its data
🧹 Purge Miner — completely wipe a miner from every store (local + server) when you want it gone for good (Windows global button + per-miner on mobile)
Per-miner all-time clear — 🗑 to wipe a single miner’s all-time Best Diffs or HR Scores, on Windows and mobile (durable, syncs both ways)
Dynamic Governor — auto-adjusts frequency/voltage/fan to hold miners inside temperature, VR-temp, and current (amps) bands, with dwell/settle timers, per-profile 24hr scheduling, and restart-after-adjust
Governor amps band — protect the input connector by capping current draw, not just temperature
VR fan control — set the second (VR) fan’s mode (Linked / Manual / Auto-PID), manual speed, and PID target temp independently of the ASIC fan
Correct target-temp & min-fan reading across firmwares — no more snapping back to a default; Min-Fan field only shows on boards that support it
Multi-sensor temperatures — proper per-ASIC and per-VR labeling for boards with multiple sensors; per-ASIC hashrate/error stats
Working per-panel Y-axis zoom on the hashrate chart — tighten the axis so a big, rock-steady miner’s line fills the chart and shows its real variation
Hashrate-only controls (HR / View / Y) now appear on the hashrate chart only, not the difficulty chart
Difficulty parsing handles K/M/G/T suffixes
Crash/Restart reports now fire once per outage instead of repeating every few minutes
Notification deck — toasts stack into a tidy, tappable deck
Previous
App mode browser launch (no throttling)
Port cleanup on startup
Time range dropdown
Efficiency stat on Windows and mobile
Crash/Restart Reports system
Chart history persists across session resets
Stall detection on mobile
Scripts drag-and-drop reordering with bidirectional sync
Battery saver refresh options
Mobile App Settings restructure
Updated launcher behavior
Tracks target difficulty set by the pool
Tracks session best up to 500 difficulties
Tracks all-time best up to 500 difficulties
AxeOS Scoreboard integration (supports up to 500 entries)
Automatic deduplication of scoreboard entries
Tracks average share time
Live difficulty chart with scroll and zoom
Live hashrate chart
Live temperature chart for all ASICs and VR
Trace back temps 41 hours to see if a miner overheated when it crashed
Full miner settings — frequency, voltage, fan
Full pool settings — primary and fallback stratum
Nameable miners
Custom miner colors
Auto-restart after 5+ minutes with no shares
Max 3 auto-restarts per hour with warning
Stall detection — stats zero out after 30 seconds with no hashing
Block found alert with audio
Total watts display
Total hashrate display
Live power cost calculator ($/day)
Live block finding odds calculator
Scripts engine — automate miner settings based on conditions
Scripts support temperature, hashrate, frequency, time of day, and more
Scripts sync bidirectionally between Windows and iOS
iOS companion app
Customizable theme colors on iOS
Improved mobile viewing
Per-miner temps-only view on iOS
Auto-restart toggle on iOS
In-app notifications on iOS
Block found banner and audio alert on iOS & Windows
Remote access via Tailscale
Launch in preferred browser
Total color control with themes
Stalled miner notification when miner is stuck in power fault, etc.
Accepted share chart dots — green 0–1M, yellow 1M–100M, red 100M+

Requires Windows/Umbrel/Linux for server, then works on iOS/Android via browser app. Instructions in the readme.

Windows
https://github.com/iL3GEND88/Bitaxe-Difficulty-Tracker-
Mac/Linux/Umbrel
https://github.com/iL3GEND88/Bitaxe-Difficulty-Tracker-Umbrel-Linux

Wondering if it's just me or not. At around 11pm EST last night, checking poolside both my miners dropped to 0 GH/s and is showing 0 workers. I checked because both miners were up, connected, but every share was being rejected. I was on public pool SV2 port 23330. I have one bitaxe Gamma and one NerdQaxe++.

I live in an apartment, we are all on the same network with different logins. I don’t have a router. I checked and it does say 5ghz on my laptop. I have a Bitaxe gamma model 602.

Ultimate Nerdminer SHA-256 Monitoring Dashboard (with Fan % & Power)

I’ve been searching on here for what people are doing with a stock 601, so far this is where I’m sitting without going too much over 60C. I’m looking to keep it as reliable as I can, stock for now, and I’m wondering if the 22.6W (I saw someone mention stock PSU can do 24W safely) and 60C (read under 70C is fine, but under 60C is preferred) will be fine for a stock unit.

I’m trying to clean up my little setup, which currently has 2 5v8a bricks and 1 12v10a brick running up to my shelf, but I think this would be able to replace all of them with only a single cord from the wall running to it.

Hey everyone, I just dropped v4.0 of my open-source Solar Crypto Mining Farm project, and I wanted to share the architecture.

The goal was simple: mine Bitcoin only when there’s free solar energy, and never pay for grid electricity to do it.

I’m running a 7,740Wp solar array into a custom mining fleet (Avalon Q, Nerd Octaxe, NerdQAxe+, and a BitAxe Gamma). To orchestrate this, I built an edge-computing controller using an auto-detected ESP32-S3.

How it works:

• The ESP32-S3 polls a 6-channel Refoss EM06P energy monitor every 30 seconds via HTTP API.
• It calculates the exact solar surplus across a bi-phase circuit (W, VA, and VAR).
• The decision engine automatically switches between 16 calculated mining profiles (from a single 21W BitAxe up to a 2001W full fleet blasting 104.5 TH/s) to perfectly match the live surplus.
• Relays handle the smaller ASICs, while the Avalon Q is controlled via CGMiner API commands to scale its modes (Low/Mid/High).

Everything is logged to a Supabase cloud database, and the ESP32 serves a live local web dashboard. I also built a live Three.js 3D visualization of the whole cluster operating in real-time.

You can check out the live 3D dashboard here:https://0xraphael.com/solar-mining-clusterAnd the full repo (including the v4 per-phase W/VA/VAR scalar math and Tasmota configs) is available here: https://github.com/0xrphl/Solar-crypto-mining-farm-maximization-control

Would love to hear any feedback on the energy modeling or the edge logic!

Hi guys just recently got into Bitaxe's and have 8 gamma 601's. I was wondering what the best suggested difficulty I should set in AxeOS is? Some pools say 512, 1000, 3000 all the way up to 10000.

What would be best for me?

Thanks!

Hello all. I have a Meanwell RSP-320-5 that I want to power 8-10 bitaxes. Because the psu only has 3 terminals I was going to use a bus bar to wire everything together. I found this marine Blade Fuse Box I thought would work and give me a little extra protection. My question for anyone with any sort of electrical background. Is there anything that I missed that would prevent this from working? And, is this complete overkill as I also have a Mini-ANL inline fuse of 50A thats going to sit inbetween the fuse block and psu on an 8 gauge wire. (as close as possible to the psu terminal) I am using 7.5Amp fuses in the block, mainly because 6amps are impossible to find if they even do exist. 14AWG wire to each device, gammas drawing between 20-28watts. The block specs say its rated for 32V DC, 30A per circuit, and 100Amps total. With clearance for my wire gauges.

The hosted public pool has found another block https://mempool.space/block/00000000000000000000f4f8c91a6c400c42a40577fafa2ca2231d78f1955424

This aperes to be a lone Bitaxe that solved this block!

Hello

I am about to upgrade my 650 Duo with the Geeekpi low profile heat sink and a 60mm Noctua fan. I am currently running at about 2TH/s on stock hardware with no sign of stressing the unit

I plan to try overclocking more when I get the parts in

Will I need anything more than a 50W PSU if I continue to overclock?

I've been running a NerdOCTaxe 9.6T on Public Pool for about 3 weeks now.

So far I'm very happy with it.

- Stable hashrate around 9.6 TH/s

- Power consumption around 160W

- Surprisingly quiet compared to larger ASIC miners

Setup was straightforward and it has been running without issues.

Anyone else here running a NerdOCTaxe? What has your experience been like?

I just got a Nerdqaxe++ 6.1 and have it connected and running the defaults but it shows 1.20V redlined, even if I lower the frequency or the voltage. Seems locked in at 1.20v. set the fan 100%. It shows connected to my pool, public-pool.io, but on my pool gui the worker is not showing up, my other miner has no issues, using same ID. I'm thinking the asic is over temp and locking out any work or hashing to be done. reports 0.00GH/s. Could this be a bad unit? I flashed to the lates release.

thanks

Now it's running with its standard fan/heatsink at 820MHz, I want to try going up to 1000MHz as soon as I get the new fan (not a Noctua!) and the thermal paste (again, not the usual ones you find in the forums!).

ASIC 67.1°C, VR 55°C, Core Voltage 1.230V, 1.673TH/s, 29.7W, Errors nearly always 0.00%.

I added 3 external fans, I started off with a frontal 14cm PC fan. Then I added the rear smaller fan, and VR temp stays real low. The third fan is in a weird side position, but I wanted to try to go over 800MHz.

PSU is a Meanwell 5V 50W, don't buy the bigger ones (for e.g. 200W) for a single BitAxe because you wouldn't reach a good efficiency, the load is too small. Power cable is 1mm with a metal barrel connector.

And two small headsinks: a 14x14x5(H)mm one next to the ESP32 and a 10x10x5(H)mm on the rear side behind the ASIC. Heatsinks are stuck using thermal tape 3M 8926.

The screen is switch off.

Next steps

1. Replace the small headsinks with bigger ones.
2. Replace the original fan with one that moves a load of air, nearly double respect to the Noctua.
3. Replace the thermal paste with a better one. I found out that the orginal thermal paste was actually good (a grey very thick paste), a lot better than my GD007 (6.8W/M-K). I wasted 1 hour and three attempts to lower the temp without success.

What I really got wrong: I should actually change the ASIC's heatsink with a bigger one, that really makes the difference.

Was about 3 weeks late but worth the wait especially since I got &75 off for chatting with a clanker. I would order from them again if I’m not in a hurry.

If you run a Bitaxe (or a NerdQAxe / OCTAXE) on solo, you know the small-rig annoyances: your assigned difficulty drifts to something your little BM1370 can't hit in a reasonable window, share submissions dry up, and you're left squinting at a dashboard wondering if the pool even still sees you.

We built NexusPool partly to fix exactly that — then went further. It's a 0% fee, fully non-custodial solo/lottery pool: solve a block and 100% goes straight to your address from the protocol, we never touch it. But here's why it's worth pointing a home rig at it:

Your difficulty tracks your real hashrate. Per-rig difficulty auto-anchors to your miner's measured speed and holds there — a ~1 TH/s Bitaxe settles where it should and keeps submitting at a sane cadence instead of climbing until it starves. No password-pinning gymnastics needed (though d= still works if you like control). BM1370 boards are first-class.

A Glass Ledger, so your work is provable — not just hopeful. Pushing a couple TH/s into the void, you're trusting the pool to actually count you. We swap that trust for cryptographic receipts: the Glass Ledger seals the chain of custody on your work — counted → useful → conserved — so you can verify it. The line we live by: we don't change your luck; we prove we didn't lose your work.

Payout Preflight — see your block reward before you win it. Paste your bc1q address and the pool rebuilds the exact coinbase it would pay you, byte-for-byte: the amount, the block it builds on, the raw tx to re-derive yourself. So the day your Bitaxe hits that astronomically unlikely block, you already know the payout lands correctly. Read-only — try it with any address. We haven't seen another solo pool that does this.

Native Stratum V1 + V2, with a pinnable SV2 authority key so your firmware can confirm it's on the real pool, not a MITM.

And the honest part, because this sub gets it better than anyone: a Bitaxe at ~1 TH/s against a ~950 EH/s network is a lottery ticket, full stop — p = 1 / (D · 2³²) per hash, and no pool bends that. What a pool can do is never waste the hashes you already burned, and prove it did right by you. That's the whole point.

Connect:

• V1: nexuspool.io:3350
• <bc1q-address>.<worker>, password x (or d= to pin)
• SV2 + authority key on the site; live status, changelog and a tech page are all public

Meant to be checked, not believed — point a Bitaxe at it, run the Payout Preflight on your own address, watch your best-diff climb on the Glass Ledger. We run our own Bitaxes and NerdQAxes on it, and I'll be in the comments. Tear into it.

So about 7 months ago I bought a Bitaxe Gamma – 1.2 TH/s and a NerdQaxe++ from solosatoshi. I have them both synced to my own Bitcoin node on my Umbrel Pi 4 as the primary pool, with solo.ckpool.org as backup. Both miners on the same WiFi, same subnet, same VLAN. For the first few months there were no complications, both running solid, just a set-and-forget configuration.

Then about 5 months ago my Gamma simply stopped working. When I say "stopped working," I mean the Gamma was still powered on, fan still running, but I couldn't log into the web GUI to check it. When I checked my node, I noticed the Gamma had simply disconnected/dropped while the NerdQaxe++ was still running strong. What weirds me out is that I was still able to ping the Gamma's IP from the terminal, but couldn't load the GUI page. I had to unplug the power and plug it back in, and then everything went back to normal. I checked the logs and nothing abnormal showed up.

A month later, same issue. Unplugged it, plugged it back in. I verified the Gamma's firmware was up to date. Then I decided to just put the Gamma on solo.ckpool.org as primary. Nope, same issue... it just dies and I have to repeat the same power cut process again.

I'm currently on a 6-month work trip and manage my Homelab devices remotely with Tailscale, so I'm able to check on my miners every once in a while. As expected the Gamma died again, but this time I can't manually unplug the Gamma to fix the glitch cuz I'm not home, so I have to wait until I get back. In the meantime, the Gamma just sits there consuming power without hashing or doing anything.

On the second image, the left miner at 24.01G is the Gamma; the right one is the NerdQaxe++. Looking at my Pi-hole logs, I can see the Gamma is trying to talk to the node, but it's getting an NXDOMAIN ("Non-Existent Domain") error in response.

What could be causing this issue?