Set up a Bitaxe by identifying the exact board, matching its power equipment, joining the intended Wi-Fi network and verifying pool-accepted work. This guide gives a first-run path for a Gamma setup, followed by the existing home-network controls. Use the instructions for your supplied revision and installed AxeOS build.
Bitaxe Gamma first-run checklist
Check the device input before applying power. The Gamma hardware project specifies 5V DC and active cooling. A mains adapter’s AC input rating is separate from its DC output. Match the output, current capacity, connector and polarity to the supplied board; a plug fitting the socket does not prove compatibility.
- Identify the hardware. Record the printed board revision and seller’s instructions. The project maintains separate 601 and 602 configurations; do not select firmware from the Gamma name alone.
- Check what was supplied. Confirm the board, cooling, stand and power equipment against the order. The Gamma 602 product listing identifies the offered model; this guide does not establish included accessories or stock.
- Join the intended network. Follow the supplied onboarding instructions, enter the intended Wi-Fi details, then find the assigned local address from the device or router. Use the local AxeOS interface to continue.
- Configure the mining destination. Copy the compatible pool endpoint, port and worker or payout format from that operator’s current instructions. Check any backup destination too; a prefilled setting is not proof that work will be credited to you.
- Verify useful work. Check connection status and accepted work in the pool’s own view as well as AxeOS. Record firmware, hashrate, temperature and power assumptions at the supplied settings before considering changes.
- Keep a recovery record. Save the approved settings and source of the matching firmware. Follow the network guidance below so local administration works without exposing AxeOS directly to the internet.
For a solo setup, compare the Bitcoin solo block probability using the actual accepted hashrate and runtime. Accepted shares are not a Bitcoin block win, and an expected time is not a payout deadline.
If the first run is not working
| Observation | Check next |
|---|---|
| Cannot reopen AxeOS after Wi-Fi setup | Find the assigned address in the router and confirm that the administration device can reach that network. Guest-client isolation may block local access. |
| AxeOS shows hashrate but the pool does not show accepted work | Recheck the endpoint, port and worker or payout format against the pool’s instructions. Compare both views over the same interval. |
| Unstable power or unexpected resets | Recheck the exact board’s power requirements and the approved adapter. Do not substitute a higher-voltage supply to try to cure instability. |
| Unexpected temperature or cooling behaviour | Check the supplied cooling arrangement and the limits for that revision. Return to the documented operating baseline and ask the seller if the behaviour remains abnormal. |
| Uncertain firmware or board identity | Record the printed revision and installed version, then check the official project and seller instructions before choosing an update or recovery image. |
Collect the exact revision, installed version, symptom and relevant log before asking for setup help. This is a commissioning checklist, not a report of a physical test on your unit.
Key terms in plain English
- ASIC:
- A computer built to do one specialised job. A mining ASIC is designed for a particular proof-of-work algorithm.
- Mining pool:
- A service that combines work from many miners and shares rewards using stated rules.
- Firmware:
- Software stored on the miner that controls its hardware. Use a trusted source and check model compatibility.
- Wallet:
- Software or hardware that manages the keys used to control cryptocurrency. A wallet is not the same as an exchange account.
- Due diligence:
- Checks carried out before making a decision, signing a contract or paying money.
Create a separate network zone
Use the router’s guest or IoT function where it provides genuine client isolation and prevents access to the trusted LAN. A different Wi-Fi name alone does not guarantee segmentation.
Connect a trusted administration device temporarily when configuration is needed. If the router cannot permit controlled management without opening the trusted network, consider a VLAN-capable access point or get networking help.
Do not place the miner on a guest network that blocks all local access before confirming how AxeOS will be administered. Design the rule deliberately rather than disabling security to make setup easier.
Keep work devices, network storage, cameras and home automation in appropriate separate zones. An experimental miner should not become a bridge to higher-value systems.

Onboard without sharing more access than needed
Follow the current Bitaxe or seller process to join the temporary setup access point, then provide only the intended 2.4GHz network credentials. Verify the device name before entering them.
Use a dedicated network password where possible, not the main business or personal Wi-Fi secret. Change any default administration credential supported by the installed AxeOS build.
Record the MAC address and assigned IP from the router so an unknown duplicate can be investigated. A DHCP reservation makes local administration and monitoring more predictable.
Close the onboarding network or reset it according to the documented behaviour after connection. Do not leave a configuration access point available unnecessarily.
Restrict internet and local management
| Flow | Ordinary policy | Reason |
|---|---|---|
| Bitaxe to pool | Allow required endpoint and port | Submit intended work |
| Bitaxe to DNS and time | Allow controlled services | Resolve and maintain time |
| Internet to Bitaxe | Block unsolicited inbound | Prevent public management |
| Bitaxe to trusted LAN | Block by default | Limit lateral movement |
| Admin to Bitaxe | Allow from controlled device or VLAN | Manage intentionally |
| Bitaxe to unknown services | Monitor or restrict | Detect drift and hidden routes |
Consumer routers differ, so test that the isolation works. From the miner network, confirm that private computers and storage cannot be reached.
Do not put the miner in a DMZ or use universal port forwarding. Those settings commonly expose administration rather than securing it.
Verify DNS, time and pool destinations
Use a trusted DNS route and keep router firmware maintained. A changed DNS response can direct a hostname away from the intended service even when AxeOS still displays the familiar name.
Confirm pool hostnames and ports from the provider’s current official page. Save the expected worker and payout relationship outside the device.
Correct time assists logs and secure connections. Investigate repeated clock or name-resolution faults instead of substituting unknown DNS and firmware suggested in an unsolicited message.
Where the router supports it, review destinations and traffic volume. Unexpected pools, repeated unknown hosts or large changes after an update deserve investigation.
Use safe remote access
The simplest safe choice is local-only administration. Pool dashboards can provide ordinary performance visibility without opening AxeOS remotely.
If remote configuration is required, use a properly configured VPN terminating on the router or a controlled gateway. Protect it with strong unique credentials and multi-factor authentication where available.
Do not rely on obscuring a port number. Internet scanners can still find exposed services, and a compact hobby device should not be the public edge of the home network.
Limit who can change pool and wallet details. Monitoring access does not require configuration authority.
Maintain firmware and recovery
Get AxeOS or seller firmware from an independently verified source for the exact board. Read release notes, back up settings and retain the previous approved image and recovery method.
Test a new build on one device and verify accepted work, temperatures, power and network destinations. Open-source code helps inspection but a downloaded binary still needs provenance.
Review network rules after reset because a recovery image can restore default credentials or onboarding behaviour. Remove old devices and credentials when hardware is sold or retired.
Keep a brief incident note for unknown access, changed pools or firmware failure. Preserve logs and isolate the device before wiping evidence.
UK home-network checklist
- Update the router and create a genuinely isolated IoT or guest zone.
- Use dedicated Wi-Fi credentials and a predictable DHCP assignment.
- Block unsolicited internet access and Bitaxe access to trusted devices.
- Permit only required DNS, time and approved pool routes where practical.
- Verify worker and payout records independently of AxeOS.
- Use local administration or a controlled VPN, never direct port forwarding.
- Record firmware source, recovery and expected network destinations.
- Review router, miner and pool evidence after every material change.
Frequently asked questions
Do Gamma 601 and Gamma 602 use the same setup or firmware image?
Identify the printed board revision first. The official ESP-Miner project keeps separate 601 and 602 configurations and instructs users to match factory images to the hardware version. Follow the exact revision and seller instructions; a shared Gamma name does not establish that every setting or image is interchangeable.
What power supply does a Bitaxe Gamma need?
The Gamma project specifies a 5V DC device supply with suitable current capacity, connector and polarity, plus active cooling. The adapter’s AC mains input is a separate rating. Check the board and approved power equipment before connection; do not select an adapter just because its plug fits.
Does the Gamma 602 listing include a PSU, stand and cooling?
Check the current Gamma 602 listing and written order contents. Included equipment can vary between suppliers and configurations. This setup guide does not confirm a particular bundle, accessory or stock position.
Why can I not reach AxeOS after connecting Wi-Fi?
The device may have received a different local address, or the administration device may be on a network that cannot reach it. Check the router’s device list and the intended guest or IoT rules. Keep administration local; do not solve the problem by forwarding AxeOS from the public internet.
Does hashrate in AxeOS prove that my pool is receiving work?
No. Confirm the pool endpoint, port and worker or payout format, then check accepted work in the pool’s own view over a comparable interval. Check backup pool settings as well. A local hashrate display alone does not verify the destination or payout relationship.
Does an accepted share mean I have won a solo Bitcoin block?
No. Ordinary accepted shares demonstrate submitted work, not a successful Bitcoin block. Use the solo probability calculator to explore hashrate and runtime assumptions; neither an expected time nor a displayed best share guarantees a future reward.
Should I change firmware before the first mining run?
Do not treat reflashing or tuning as a required first step. Record the supplied version, board revision and settings, check the trusted project and seller instructions, and establish a working baseline. If an update or recovery is needed, use a matching image and a documented recovery process.
Key points to remember
A secure Bitaxe setup UK design gives the device only the network access it needs. Isolate it from personal and business systems, keep management local or behind a controlled VPN, and verify every pool and firmware route. This reduces the consequence of a weak build without preventing the compact miner from doing its intended work.
After router replacement or a factory reset, repeat the segmentation test before reconnecting the miner. Consumer equipment can restore permissive defaults, change guest-network isolation or enable automatic port features. Treat network replacement as a new security configuration and approval event, not as a transparent routine hardware swap.
Next steps
Compare current Bitaxe hardware, confirm the exact order contents, then use this first-run and network checklist. For other compact models, read the home Bitcoin mining setup guide and compare the home-miner category.
Conclusion: Bitaxe setup UK
Place Bitaxe on a guest or IoT network that cannot initiate connections to personal computers, storage or business devices. Do not forward AxeOS ports from the router. Use a controlled VPN for remote administration and keep firmware and pool sources verified.
Sources and further reading
Gamma hardware and ESP-Miner sources checked 28 October 2026. Setup labels and recovery procedures can vary by revision and installed build.
- Bitaxe Gamma hardware project: Device input, cooling and hardware documentation.
- Official ESP-Miner board configurations: Separate revision configurations.
- AxeOS miner repository: Primary AxeOS project repository.
- NCSC connected-device safety guidance: Primary UK cyber-security advice for home devices.
- NCSC device security guidance: Primary UK connected-device security guidance.





Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.