Match the instructions to the installed firmware
Open the miner's local AxeOS interface and note the board and installed firmware version. The official ESP-Miner repository documents pool fields, but hardware revisions, releases and forks can expose different controls. Follow the fields on your own unit; this guide does not certify every Bitaxe board, firmware branch, transport or Stratum V2 combination.
- Use the local device interface; do not expose it publicly to complete this guide.
- Select standard TCP unless the installed firmware supports the pool's TLS connection.
- Stratum V2 requires compatible endpoints and firmware; a TLS port alone does not mean SV2.
Fill the address, port and worker without mixing formats
For separate fields, use btc.solomining.xyz with port 1313 for TCP, or btcssl.solomining.xyz with port 1414 for supported TLS. A complete-URL interface uses the corresponding stratum+tcp or stratum+ssl prefix. Set the username to your Bitcoin address followed by a period and a unique worker label. Use x if a password is required.
- Use a Bitcoin receiving address you control. SoloMining's published policy says this is the destination for a valid block reward from your user-assigned work; this page does not verify a live job or payout.
- A separate host field contains no protocol prefix or port suffix.
- Review the address on the miner after pasting; the generator cannot prove you own it.
Check the original guidance: ESP-Miner / AxeOS · GitHub
Save, receive work, then check accepted shares
Save the configuration and restart mining only if the device requires it. Follow the log from connection to authorization, a received job and a submitted share with an accepted response. Open the wallet dashboard and check the same worker and recent submission time. Share difficulty and hashrate affect how frequently you see feedback, so there is no universal first-share deadline.
- Connected is a useful stage, not the final success condition.
- Keep a recent timestamp and the expected worker name in view.
- An accepted share confirms submitted work met the share target; it is not a Bitcoin block.
Use the matching recovery path if feedback stops
If the device never receives jobs, inspect connection and authorization errors. If jobs arrive but shares are sparse, check the assigned difficulty. If accepted responses exist but the dashboard is empty, compare addresses and the telemetry window. Preserve the original settings before a controlled alternate-pool test rather than changing difficulty, voltage and endpoint together.
- Use the share diagnostic for missing, stale, duplicate or low-difficulty responses.
- Keep worker names distinct when adding more devices.
- Set a backup only through controls your firmware supports, and verify its reward model too.
What changes when you add devices or update AxeOS?
Add unique worker names and check each device after a firmware update. A newer source repository can describe features absent from your installed release. Keep a record of the version and working settings, and retest the connection path when its controls or protocol support change.
Content updated: 3 October 2026 · Policy and sources checked: 6 September 2026
Bitaxe pool configuration questions
Should AxeOS receive the full Stratum URL?
Follow the field layout in your installed version. A separate host field takes only the hostname and a separate port field takes the number. An interface with one full pool URL needs the matching protocol prefix and port. The generator offers both layouts so you can copy the appropriate form.
What goes in the password field?
SoloMining's published setup accepts a blank password where the miner allows it, or x when the interface requires a value. This is not a wallet authentication field. Never paste recovery words, a private key or an exchange password. Other pools may use password options differently, so do not transfer their syntax blindly.
Why is the miner connected but missing from the dashboard?
Verify the expected wallet and worker first, then check the device log for incoming work and accepted submissions. Low hashrate or high assigned share difficulty can make feedback sparse. Telemetry can also be delayed. Identify which stage is missing before treating a blank dashboard as a failed mining connection.
Does this page certify every Bitaxe or AxeOS version?
No. It provides the published connection fields and a verification procedure. Hardware versions, firmware branches and transport controls differ. Check the installed version's documentation, use a supported transport and confirm accepted work on the device and pool. A feature present in source code is not proof it runs on your unit.
Can several Bitaxes use one Bitcoin address?
The published worker format lets you append different labels after the same address, such as a room or device identifier. Give each unit a unique label and verify each worker separately. The dashboard address groups available telemetry; it does not demonstrate address ownership or turn several miners into a shared-reward community pool.