Miner Log Reader: How to Interpret Your SoloFury Report (2026)

The SoloFury Miner Log Report is a complete, plain-text snapshot of your solo-mining activity, generated on demand from your /miner/ page. One file captures real-time hashrate, per-worker health, share quality, difficulty-tuning suggestions, 24-hour statistics with an ASCII chart, blocks found, and pool and network context. Unlike a dashboard screenshot, it is structured text you can save for the record, parse with scripts, or attach to a support email. This guide explains every section and what to do for each warning.

Key Takeaways

• The log is a one-click, plain-text snapshot from your /miner/ page — save it, script it, or attach it to support.
• Start with the Executive Summary. If it reads ALL GOOD, there is nothing to investigate.
• Worker Health Analysis is the key troubleshooting section — it flags per-worker drops and offline workers, with a suggested action for each.
• Share Quality and Difficulty Optimization tell you whether your connection is clean and well-tuned; leaving the password as x lets the pool auto-tune difficulty.
• Statistical TTF is an average, not a schedule — about 63% of blocks arrive within one TTF and 95% within three.

How do you download your log?

1. Open solofury.com/miner/ with your wallet in the URL: ?addr=YOUR_WALLET&coin=COIN.
2. Wait for the dashboard to fully load (a few seconds — the report uses live API data).
3. Click the .LOG button on the identity card.
4. Your browser downloads a file named solofury-COIN-WALLET-DATE.log.

1. Executive Summary

A one-glance overview: status, worker count, current hashrate versus 24h average, lifetime blocks, total mined, and the top issues. Read this first — it tells you whether anything needs attention.

Status values:

• ALL GOOD — every worker is healthy, with no degradation beyond 25%.
• ISSUES DETECTED — one or more workers have warnings (drops of 25–50%, or late shares of 3–10 minutes).
• CRITICAL — one or more workers are offline (over 10 minutes) or severely degraded (over 50%).

If the report says ALL GOOD, you can stop here and check back tomorrow.

2. Overview

Wallet-level aggregated stats: hashrate moving averages across time windows (the 1-minute is most volatile; the 7-day is the most stable benchmark), the count of online workers, lifetime share totals (accepted, rejected, invalid, stale, duplicate), efficiency (the percentage of submitted shares accepted — aim for above 99.5%, ideally 99.9%), round luck (above 100% means you have already submitted more shares than statistically expected for a block this round), and your best share ever (your closest approach to the network target).

3. Worker Health Analysis

This is the most important section for troubleshooting. The analyzer compares each worker’s current hashrate against its own 1-hour and 24-hour moving averages, and checks how recently it submitted a share.

Typical cases and what to do: a worker offline for over 10 minutes means checking power, the network cable, and that the stratum URL is reachable. A drop of 50% or more is usually thermal throttling or a failing hashboard — check cooling first. A 25–50% drop is mild; monitor for half an hour before acting. Late shares with normal hashrate point to a network or stratum issue — try switching to your closest of SoloFury’s nine regions to cut latency. The log includes a suggested action for each problematic worker.

4. All Workers (table)

A full tabular view of every worker, regardless of status, for side-by-side comparison. The columns: HASHRATE / 1H / 24H / 7D averages (the 7-day shows your true capacity), UPTIME (time connected since first share), BEST DIFF (the worker’s highest-difficulty share — higher is closer to a block), LAST SHARE (time since its last share, normally under a minute), and STATUS (health, per section 3).

5. Difficulty Optimization

SoloFury uses vardiff (variable difficulty): it automatically tunes each worker’s share difficulty to keep a steady, efficient share rate, so you normally never touch it. This section reports whether your current difficulty is well-matched to your hashrate and suggests an adjustment if not:

• Raise — your difficulty is on the low side, producing many low-value shares; the pool adjusts this automatically.
• Lower — your difficulty is on the high side, producing too few shares for smooth tracking; this is most relevant for low-hashrate Bitaxe-class miners.
• Optimal — no action needed.

6. Share Quality Analysis

A breakdown of rejected shares by type: Reject (submitted but did not meet target — often stale work or a firmware issue), Invalid (malformed; should be near zero and usually signals a software bug), Stale (for an outdated block, because your miner was still on the previous job when a new one arrived — some staleness is normal, but above 1% suggests latency to the pool), and Duplicate (the same share twice, usually a network glitch).

Quality badges summarize it: Excellent is a total bad-share rate under 0.1% (one in a thousand or rarer), Good is under 1%, and Below normal is over 1% — investigate your network or firmware.

7. Statistics (last 24h)

Aggregated metrics from the 24-hour history (sampled every few minutes): hashrate average, max, and min (a big min-to-max gap suggests instability); peak-versus-average spikiness (a small gap is smooth, a large one suggests on/off behavior); effective uptime (the percentage of samples with hashrate above 10% of average — 100% is continuous operation); and 24-hour share counts to compare against your usual baseline.

8. Wallet-Level Outages

Lists total-wallet blackouts in the last 24 hours, where the entire wallet’s hashrate fell below 15% of its average — catching a power outage at your site, a network failure on your side, or (rarely) a pool-side outage. Single-worker failures are not shown here; those live in section 3.

9. Hashrate Timeline (24h)

A two-part view of the day’s hashrate: an ASCII chart sketching the curve (the Y-axis shows absolute values, the X-axis spans 24 hours ago to now), and hourly snapshots showing your hashrate and the network difficulty at each hour. Use it to spot daily cycles, slow declines, or sharp drops.

10. Blocks Found by This Wallet

A real list of blocks your wallet has found on the pool. Each entry shows the HEIGHT (verifiable on any block explorer), the DATE (UTC), and the WORKER that submitted the winning share. This is filtered to your wallet address.

11. Network Context

The wider context for your coin: current network hashrate and difficulty, your share of the network, and the Statistical TTF (Time To Find) — the average expected time to your next block, computed as 1 / (your_HR / network_HR × blocks_per_day).

12. Pool Context

Pool-wide stats — hashrate, miners, workers, idle and disconnected counts, fee, luck, and uptime — to verify the pool is healthy while troubleshooting. If pool stats look normal but your miner shows issues, the problem is on your side.

Frequently asked questions

How often should I download a log? For active monitoring, once a day or whenever you notice something abnormal; for records, weekly or monthly. The file is small (tens of kilobytes), so keeping many is fine. The Report ID in the header lets you reference a specific one in support emails.

Can I script the log generation? Not the file itself (the button runs in your browser), but you can fetch the same underlying data from the public API — for example https://solofury.com/api/client/YOUR_WALLET (add ?coin=COIN for non-BCH coins) and /api/pool. These return JSON, so you can build your own report in any language.

The log says my worker dropped, but the dashboard looks fine — why? The “now” value can briefly spike back up while the 1-hour and 24-hour averages stay lower, since those are rolling windows. A warning against the 24-hour average means the worker ran below capacity for most of the day and only just recovered. The log compares against the longer window to catch sustained issues a snapshot would miss.

The Statistical TTF says 30 days — will I find a block in 30 days? No. TTF is the average expected time. Because block-finding is exponential, you have about a 63% chance within one TTF (30 days here), about 86% within two (60 days), and about 95% within three (90 days). Some periods deliver two blocks, others none — that is the nature of solo mining.

What is the difference between “Rejected” and “Invalid” shares? A rejected share was well-formed but did not meet the target difficulty, often due to stale work — a small number is normal from latency. An invalid share was malformed (bad format or nonce) and almost always signals a software or firmware bug.

I see a “LATE share” but my worker is mining — what is wrong? “LATE” means more than three minutes since the last share. Causes include a brief network drop to the stratum, a legitimately high difficulty (so shares are simply infrequent), or the worker having just gone offline before the pool fully detects it. Cross-check the dashboard hashrate: if it is still showing, it is usually a transient connectivity blip.

Why is my efficiency below 99.9%? Efficiency is accepted shares divided by submitted shares. A small shortfall comes from normal stale shares due to latency; a larger one points to a network or firmware problem. Switching to your closest region (one of SoloFury’s nine regions) is the most common fix.

Where can I get more help? Email [email protected] with the .log file attached and the Report ID from its header, which helps match your report to the issue. See also the Miner Health Check and Reading Your Worker Stats guides.

Next Steps

• Run the Miner Health Check guide to act on any flagged worker.
• Learn every dashboard metric in Reading Your Worker Stats.
• Understand the TTF math and timing in the Difficulty Adjustment Calendar.
• Download a fresh log from your miner page after any change to confirm it worked.