Choose a Bitcoin mainnet wallet
Use an address you control as the miner username. Never enter a seed phrase or private key in pool settings.
Hosted Bitcoin solo-mining pool
Configure a SHA-256 ASIC or supported Bitaxe, then check accepted shares and data timestamps on the wallet dashboard.
The published fee policy assigns 1% of connected hashrate to the platform and 99% to your solo share.
Mining endpoints
Full setup detailsQuick start
Set the wallet login and endpoint, then use miner logs and dashboard timestamps to check the connection.
Use an address you control as the miner username. Never enter a seed phrase or private key in pool settings.
Enter the matching host and port, or use the full Stratum URL if your miner has a single URL field.
Use the wallet address alone, or append a period and short worker label such as .worker01.
Check the miner log and wallet dashboard for the expected worker, accepted-share data, and its latest timestamp.
If your share finds a valid Bitcoin block, the published policy says its subsidy and transaction fees go to the configured wallet without an additional reward deduction. This describes the policy; it does not prove a future block or payment.Read the full fees and rewards policy.
Mechanics
Submitted shares can show that a miner is working and communicating with the pool. They do not make the next hash more likely to find a block.
Understand solo miningProbability
Use a timestamped network-difficulty snapshot and a Poisson model to estimate the chance of at least one block.
Open the probability calculatorFAQ
No. Solo mining is probabilistic. A probability estimate describes a model under stated assumptions; it does not promise a result within any period.
An accepted share indicates that submitted work met the pool's share target. It is useful telemetry, but it is not the same as finding a Bitcoin block.
The telemetry backend, its data source, or the network-difficulty source may be delayed or unavailable. The interface keeps unknown values distinct from valid zeros.
The current backend contract supports a rolling window of up to 24 hours. Longer history is not promised until storage and retention are implemented.