A mini ASIC can make a compact Bitcoin solo-mining project, but it does not create regular income. First choose whether you want ordinary pooled rewards, a solo-pool service or a self-operated node and mining server. Then check the hardware and calculate block odds using explicit assumptions.
Start with the purpose of your mini-mining project
For learning, a compact miner can help you understand proof of work, pool connections and operating conditions. If the purpose is recurring payouts, investigate ordinary pool rules and complete running costs. If the purpose is solo block finding, understand the very small chance before choosing equipment.
Labels such as “lottery miner” do not change the mathematics. Set a budget for the hardware and operation that does not depend on finding a block. This guide provides a probability example and setup checks; it does not report physical hardware tests or forecast a return.
Compare ordinary pooled mining, a solo pool and your own node
| Route | Where work comes from | Reward and setup checks |
|---|---|---|
| Ordinary pooled mining | The pool’s mining service distributes work and records shares. | Participants receive rewards under the provider’s payout method, fees and thresholds. Small or regular payouts are not guaranteed by this guide. |
| Solo pool | A third-party solo-mining service supplies the endpoint and infrastructure. | Reward eligibility depends on finding a qualifying block and the operator’s terms. Check fees, stale-block treatment and the payout destination. |
| Self-operated solo mining | Your validating node supplies block-template data through a compatible mining server. | You operate the node and server route. A Stratum-speaking ASIC needs a compatible Stratum service or bridge; a Bitcoin Core RPC URL is not automatically a pool endpoint. |
The Bitcoin developer mining guide explains solo and pool operation and the distinction between shares and valid blocks. Provider rules vary, so inspect the actual service rather than relying on the word “pool”.

Match the device, node and endpoint
Check the exact model, supported algorithm, firmware and pool protocol. For Bitaxe, use the official ESP-Miner project and the instructions for your board and firmware version. Configure the endpoint, port and worker or payout format supplied by the intended operator.
For a self-operated route, a synced Bitcoin Core node is one part of the setup. Core’s getblocktemplate RPC method supplies block-construction data. The mining-server software must turn that into work compatible with your device and submit valid results. Check that complete path; merely running Core on the network does not connect the ASIC to it.
Keep node RPC authenticated and private. Do not enter wallet private keys or recovery phrases into a miner. Independently check the receiving address and all fallback endpoints; a healthy local hashrate does not prove the destination is yours.
Worked examples: what are the odds of a mini miner finding a block?
For a fixed Bitcoin difficulty, a standard approximation is:
Expected blocks (λ) = hashrate in H/s × active seconds ÷ (difficulty × 232).
Chance of at least one block ≈ 1 − e−λ.
These examples use a deliberately fixed 100 trillion difficulty, 365 days and 100% uptime. They are illustrative hashrates, not current network readings or specifications for named products.
| Productive hashrate while running | Chance of at least one block in 365 days |
|---|---|
| 1TH/s | 0.007342% |
| 5TH/s | 0.036706% |
| 10TH/s | 0.073399% |
Percentages are rounded to six decimal places. Even the largest example has a high probability of finding no block in that year. The formula approximates independent attempts with a Poisson model. Future difficulty, productive hashrate, uptime and stale work can change the actual outcome; a long-run mean is not a date when a reward becomes due.
Enter your own hashrate, difficulty and runtime in the solo mining calculator. Enter uptime separately from your while-running productive hashrate; do not deduct the same downtime twice. A pool fee changes the reward paid rather than the target a hash must meet.
Assess electricity separately: watts ÷ 1000 × active hours × your price per kWh. Include the node, external supply and cooling where they sit outside the miner’s stated power. Use the Bitcoin operating-cost calculator for those assumptions. An expected block value spread across years is not cash available to pay this month’s electricity bill.
Prepare power, cooling and the network
Use the exact device and power-supply instructions. A miner’s low-voltage DC input and an adapter’s AC input are different ratings; match connector, polarity and current capacity as well as voltage. Ventilate both miner and power equipment and check the actual installation requirements. The home Bitcoin mining setup guide covers the wider space, heat, sound and electricity checks.
Keep the management interface on a trusted network, change supplied credentials where supported, and avoid unnecessary inbound exposure. Only use firmware intended for the exact hardware. Retain a configuration record without publicly sharing credentials or receiving-account details.
Troubleshoot useful work rather than waiting for a win
| Symptom | Check next |
|---|---|
| Local hashrate but no accepted work | Endpoint, protocol, port, connection logs and the operator’s worker view. Check its expected share interval before diagnosing a fault from a short wait. |
| Shares accepted but no block reward | Shares usually meet an easier target than Bitcoin blocks. Read the chosen pool’s payout rules; accepted shares are not proof that a block was found. |
| Own node is synced but ASIC cannot connect | Confirm a compatible mining server or Stratum bridge exists between Core and the ASIC; RPC and Stratum are different interfaces. |
| Wrong destination after a restart | Saved configuration, worker/address format and every fallback endpoint. Stop and correct the destination before further operation. |
| No block after a long run | Verify productive work and configuration independently. Absence of a block alone does not establish that a low-hashrate solo setup is faulty. |
Verify the first run and restart
- Start with the manufacturer-supported settings and record the hardware, firmware, supply and intended destination.
- Confirm device connectivity, local operating conditions and accepted work or mining-server evidence over an appropriate observation period.
- Compare local hashrate with server-side evidence, accounting for how each reports averages and shares.
- After a normal supported restart, confirm that the intended endpoint and receiving configuration remain in place.
- Retain the configuration and operating record. Do not judge commissioning by whether a Bitcoin block appears during the test.
For a Bitaxe-specific first run, follow the setup and troubleshooting guide. Check logs and documented operating limits before changing firmware or tuning.
Before choosing hardware
- Choose the mining route and understand its actual reward rules.
- Check the exact algorithm, model, operating mode, power equipment and network requirements.
- Model block probability and total running costs with separate, explicit assumptions.
- Confirm the available space can accommodate power, heat and sound.
- Check included equipment, condition and current availability on the individual product page.
Compare compact home Bitcoin miners and the Bitaxe range. For Avalon models, use the Nano and home-miner comparison. A model’s hashrate alone does not establish that it suits your space or will generate predictable income.
Key terms in plain English
- Bitcoin Core:
- Widely used Bitcoin software. It can check blocks and transactions and provide wallet, network and operator tools.
- Node:
- A computer running network software that checks data and talks to other computers on the network.
- ASIC:
- A computer built to do one specialised job. A mining ASIC is designed for a particular proof-of-work algorithm.
- Hashrate:
- The amount of mining work a machine attempts each second. More hashrate does not guarantee more profit.
- Efficiency:
- How much electricity a miner uses for a set amount of work. Lower joules per terahash usually means better efficiency.
Frequently asked questions
Can a mini ASIC find a Bitcoin block?
A compatible SHA-256 miner can attempt to find a valid Bitcoin block, but a small hashrate has a very small chance over a typical ownership period. There is no scheduled win. Use the solo mining calculator with an explicit difficulty, hashrate, runtime and uptime.
Is a solo pool the same as mining through my own node?
No. A solo pool supplies the mining service and has its own operator, endpoint, fees and reward rules. A self-operated route uses your own validating node plus compatible mining-server software where the device needs a Stratum connection. Merely owning a node does not mean your miner uses it to create work.
Can I enter a Bitcoin Core RPC address in an ASIC pool field?
Do not assume the protocols match. Bitcoin Core’s getblocktemplate is an RPC method; a miner configured for Stratum needs a compatible mining server or bridge. Follow the exact device and server documentation, and keep authenticated node RPC private.
Do accepted shares mean I have won Bitcoin?
No. A share can demonstrate submitted work at a pool’s easier share target without meeting Bitcoin’s block target. Accepted-share evidence helps check connectivity and productive work. Reward eligibility and payout depend on the chosen service’s actual rules.
Does waiting longer make a block due?
No. At unchanged difficulty, each new hash is another independent attempt. More operating time increases the chance across the whole period, but an average interval is not a countdown and a long run can still end without a block.
How should I enter hashrate and uptime in the calculator?
Use productive hashrate while the miner is running, then enter the proportion of the period it will run as uptime. If your hashrate average already includes offline periods, do not apply the same downtime again. Difficulty changes and future performance can change the result.
Does a pool fee change the chance of finding a block?
A fee deducted from a reward changes the amount paid, not the probability of a hash meeting the block target. Connectivity, stale work and downtime can affect productive attempts. Check the operator’s current fees and reward conditions separately.
Which hardware should I compare for a home solo project?
Compare the exact home-miner listings and Bitaxe models against their supply, cooling and network requirements. Check included equipment, condition and availability on the product page. Higher hashrate alone does not establish suitability or predictable income.
Key points to remember
Separate device suitability, the mining-server route, proof of productive work and reward probability. They answer different questions. A small solo setup may operate correctly without finding a block throughout its useful life.
Next steps
Use the solo calculator to test your assumptions, then check the exact product and home setup requirements. If the site cannot support the machine you are considering, review hosting eligibility and complete site costs before buying.
Make the decision before relying on a reward
Choose a project whose hardware and operating costs fit your purpose without depending on a solo block win. Verify the miner’s actual work route, keep the probability assumptions visible, and reassess when difficulty, firmware or operating conditions change.
Primary references
References checked 28 October 2026. The odds table is an independently calculated illustration, not live network data or a product test.
- Bitcoin developer mining guide — solo mining, pools, shares and the proof-of-work target.
- Bitcoin Core getblocktemplate RPC reference — the node’s block-template interface.
- Official ESP-Miner project — device software and pool-protocol configuration context; use the instructions for the exact version.





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.