• BTC/USD $60,363 ▲ +2.94%
  • BCH/USD $213.69 ▲ +5.45%
  • DGB/USD $0.0024 ▲ +3.30%
  • XEC/USD $0.000005 ▲ +3.93%
  • PPC/USD $0.223 ▲ +5.84%
  • NMC/USD $0.824 ▲ +1.44%
  • BC2 HR
  • BCH2 HR
  • Pool HR 938.83 TH/s
  • Miners 207 online
  • Last Block 2 days ago
Guides

The Ultimate BitAxe Guide.

Everything you need to know — from first boot to reading stratum logs. All examples use SoloPool.eu.

Section 1

Setting Up the BitAxe

1.1 Power & Initial Boot

Plug your BitAxe into a 5 V USB-C power supply. It boots automatically — the OLED screen displays its own IP address within a few seconds. On first boot it enters a Wi-Fi setup mode and broadcasts its own temporary Wi-Fi hotspot.

1.2 Connecting to the Wi-Fi Hotspot

1
On your phone or PC, scan for a Wi-Fi network starting with BitAxe-xxxx and join it (no password needed).
2
Open a browser and go to the IP shown on the BitAxe OLED — usually 192.168.4.1.
3
Under the Network tab, enter your home Wi-Fi SSID and password, then save.
4
The BitAxe reboots, joins your Wi-Fi, and shows its new local IP on the OLED. Navigate to that IP.

Note: BitAxe chips only connect to 2.4 GHz networks — 5 GHz bands are not supported. If you use an ASUS router, temporarily disable AI Protection or the device won't join your home network.

1.3 Entering Your Mining Credentials

Under the Settings tab in AxeOS, fill in the stratum fields for SoloPool.eu:

Stratum Host bch.solopool.eu no stratum+tcp:// prefix
Port 3333 or 3334 for TLS
Username bitcoincash:qYOURADDRESS.workername BCH address + optional worker tag
Password x any value works

Worker naming: appending .bitaxe1 to your address lets you track multiple devices separately on the miner stats page. See the Worker Naming Guide for details.

Click Save & Apply. The BitAxe reboots and should start hashing within 30 seconds. You'll see accepted shares appear on your miner stats page shortly after.

Section 2

Understanding the AxeOS Dashboard

2.1 Hashrate Metrics

Hashrate is an instantaneous estimate of your miner's speed, calculated over the last few seconds. Because each hash is a random trial, share counts in any short window follow a Poisson distribution — expect large swings up and down. This is normal.

Average Hashrate is smoothed over a longer window (1–5 minutes). This is the number to watch — it filters out the noise and shows your true sustained speed. A healthy BitAxe Gamma runs around 1–2 TH/s depending on overclock settings.

Don't panic at dips. Seeing the instantaneous hashrate drop to zero or spike to 3× normal is just statistical variance, not a hardware problem. Watch the average — if it stays stable, your miner is healthy.

2.2 Efficiency (J/TH)

Efficiency tells you how much electricity is used per unit of hashing work. Lower is better.

Formula: Efficiency (J/TH) × Hashrate (TH/s) = Power draw (Watts)

// Example: BitAxe Gamma at stock settings 15 J/TH × 1.2 TH/s = 18 W 18 W × 24 h = 432 Wh = 0.432 kWh/day At €0.25/kWh → €0.11 per day to run

kWh is how electricity suppliers charge you — check your bill for your unit rate. Efficient mining means more hashes per euro spent on electricity.

2.3 Share Statistics

Accepted Shares
Valid work submitted
Each accepted share means your miner submitted a hash that exceeded the pool's share difficulty. For BitAxe devices this is typically ~1000 — the device requests this via a mining.suggested_difficulty message.
Rejected Shares
Discarded by the pool
Rejected shares are usually stale (arrived after a new block was found) or caused by a hardware or network error. A reject rate above 1% is worth investigating — check your latency to the stratum server.
Best Difficulty
Highest share ever found
The highest difficulty hash your miner has ever submitted. This is pure luck — it can jump into the billions within minutes or stay low for weeks. It is not a performance metric. Do not use it to judge whether something is wrong.
Best Difficulty (All Time)
Your personal record
The highest difficulty hash submitted across all sessions. BCH network difficulty is roughly 888 billion — reaching that means your miner found a block. You can see your best share on the pool stats page.

Setting difficulty too high causes your miner to take a long time to find any share, making pool stats appear stale or offline. Leave it at the device default — the pool will negotiate the right difficulty automatically.

2.4 Graphs & Trend Lines

The AxeOS graph plots three lines on the same time axis:

  • Instantaneous hashrate (solid) — jumpy, Poisson-driven, short window (~5 s)
  • Average hashrate (dashed) — smoothed over 1–5 minutes, shows real sustained speed
  • ASIC temperature (red) — plotted on the right Y-axis in °C
Pattern: Normal
Random spikes & dips
Instantaneous line bounces around the average. Average stays flat. Temperature is stable. Nothing to do — this is just Poisson variance.
Pattern: Thermal throttle
Rising temp, falling speed
Temperature climbs → both instantaneous and average hashrate drop together. The ASIC is throttling to protect itself. Improve airflow or reduce frequency.
Pattern: Network lag
Low rate, stable temp
Instantaneous hashrate is low but temperature is normal and average is stable. Likely share submissions are being delayed. Check your internet connection or pool latency.
Pattern: Overclock crash
Sudden drop to zero
Hashrate falls to zero or reboots happen repeatedly. Usually voltage too low for the clock speed set. Reduce frequency in 25 MHz steps until stable.

2.5 Power Statistics

All readings come from a TI INA260 digital power monitor between the 5 V supply and the ASIC. It measures real-time watts, input voltage, current, clock speed, and core voltage.

MetricWhat it isSafe range
Power (W)Real-time electrical draw of the ASIC rail~15 W stock · up to ~30 W overclocked
Input Voltage (V)Bus voltage on the 5 V rail4.9–5.1 V  below 4.8 V = risk of reset
ASIC Frequency (MHz)Core clock of the BM13xx chip525 MHz stock  1000 MHz+ = high heat
Core Voltage (V)Voltage fed to the ASIC core1.10–1.20 V stock  max ~1.25 V for overclocks

Overclocking safely: increase frequency in steps of 20–25 MHz at a time. Check stability at each step before going further. Core voltage above 1.25 V combined with high temperature accelerates chip wear. The INA260 only measures the ASIC rail — the ESP32's own draw (~1–3 W) is not included.

2.6 Heat & Fan Speed

The heat section shows three values: ASIC temperature (die), VRM temperature (the voltage regulator), and fan speed as a percentage of max RPM.

SensorIdealWarningCritical
ASIC (die)40–65 °C65–70 °C>70 °C — throttles; >75 °C — wear risk
VRM<100 °C100–110 °C>120 °C — regulator failure risk
Fan SpeedAuto (AxeOS curve)Sustained 100%100% + rising temp = inadequate airflow

Fan speed runs 1 000–7 200 RPM on stock fans and is controlled automatically by AxeOS. Sustained 100% fan speed means the device is fighting to keep cool — improve airflow, clean dust from heatsinks, or reduce your overclock. Noctua 5 V fans are a popular upgrade for quieter, more effective cooling.

Dust is the enemy. Clean heatsinks and fan blades monthly — a dust layer can raise VRM temperature by 10–15 °C and reduce ASIC lifespan noticeably.

Section 3

Reading the Stratum Logs

AxeOS shows a live log of every message sent and received over the stratum connection. Once you know the pattern, errors become obvious immediately.

3.1 Connection Handshake

On first connect, the BitAxe sends a subscribe then an authorize message:

→ {"id":1,"method":"mining.subscribe","params":["AxeOS/1.0","00000001"]} ← {"id":1,"result":[["mining.notify","..."],"extranonce1",4],"error":null} → {"id":2,"method":"mining.authorize","params":["bitcoincash:qYOURADDRESS.bitaxe1","x"]} ← {"id":2,"result":true,"error":null}

result: true on authorize = you are connected and authenticated. result: false means bad credentials — double-check your BCH address.

3.2 Receiving Work

After authorization, the pool continuously pushes new jobs via mining.notify:

← {"id":null,"method":"mining.notify","params":[ "jobId", // reference for your submit "prevHash", // previous block hash "coinbase1", // coinbase transaction part 1 "coinbase2", // coinbase transaction part 2 ["merkles..."], // merkle branches "version", // block version "nbits", // compact difficulty target "ntime", // current timestamp true // cleanJobs — discard previous work ]}

When cleanJobs is true, a new BCH block was found on the network and all previous work is obsolete. AxeOS switches to the new job immediately.

3.3 Submitting a Share

When your ASIC finds a hash that exceeds the pool's share difficulty, AxeOS submits it:

→ {"id":4,"method":"mining.submit","params":[ "bitcoincash:qYOURADDRESS.bitaxe1", "jobId", "extranonce2", "ntime", "nonce" ]} // Accepted: ← {"id":4,"result":true,"error":null} // Rejected (stale): ← {"id":4,"result":false,"error":[21,"Job not found",null]}

3.4 Common Log Errors

Here are the errors you're most likely to see and what they mean:

The share arrived after a new BCH block was found on the network, making the job it was solving obsolete. This is normal — occasional stale shares are expected. A high rate of stale shares usually means your internet latency to the stratum server is too high. Try the TLS port 3334 which has better keepalive behaviour.
Your miner submitted the exact same nonce twice for the same job. This typically indicates a bug or a crash-loop in AxeOS. Update your firmware and check for hardware issues.
Authentication failed. Check that your BCH address is correct (must start with bitcoincash:q), that there are no typos in the worker name, and that the stratum host is exactly bch.solopool.eu with no prefix.
The BitAxe connected but isn't receiving jobs. Check your port — 3333 for plain TCP, 3334 for TLS. Some firewalls block non-standard ports; try the other one. Also confirm the stratum host has no stratum+tcp:// prefix.
More than ~1% rejected shares is worth acting on. Common causes: high latency to the pool (try a VPN or different DNS), an overclocked ASIC producing invalid hashes, or a flaky USB power supply causing voltage sags. Run at stock settings to isolate the cause.
Ready to start mining?
Point your BitAxe at SoloPool.eu and start hunting blocks.
Start Mining Worker Naming FAQ