Transparent Bitcoin solo mining

A clearer way to solo mine Bitcoin.

Connect your miner, check the telemetry available for your wallet, and understand the probability behind every attempt.

Mining endpoints

Full setup details

No account is required. Up to five recent valid addresses are saved only in this browser.

Quick start

From ASIC to observable shares.

Use verified details, inspect the miner, and treat accepted shares as operational evidence.

01

Use a Bitcoin wallet

Your wallet address identifies the dashboard used to display available telemetry.

02

Configure the endpoint

Choose the published TCP or TLS endpoint and use your wallet address as the username.

03

Start hashing

Apply the settings on your miner and wait for accepted-share telemetry.

04

Verify the signal

Confirm timestamps, expected workers, and recent activity on the wallet dashboard.

Mechanics

Shares show work. Blocks remain probabilistic.

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 mining

Probability

Estimate odds without pretending they are certainty.

Use a timestamped network-difficulty snapshot and a Poisson model to estimate the chance of at least one block.

Open the probability calculator

FAQ

Clear answers to the first questions.

Is solo mining guaranteed to find a block?

No. Solo mining is probabilistic. A probability estimate describes a model under stated assumptions; it does not promise a result within any period.

What does an accepted share prove?

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.

Why can a dashboard value be unavailable?

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.

How much history can I view?

The current backend contract supports a rolling window of up to 24 hours. Longer history is not promised until storage and retention are implemented.