# EthereumClassic (ETC) — Solo Mining Pools & Network State

Live solo mining pool comparison, network difficulty, block reward structure, and Poisson solo mining probabilities for EthereumClassic, as measured by BackPow.

## Network Overview

| Metric | Value | Unit |
| --- | --- | --- |
| Algorithm | Etchash | |
| Network hashrate | 150702465137108.94 | H/s |
| Difficulty | 2003699000000000.0 | |
| Difficulty, 24h average | 2044928000000000.0 | |
| Difficulty, 7d average | 2039601000000000.0 | |
| Block time, observed | 13.637 | seconds |
| Block reward | 1.59 | ETC |
| Spot price | 8.08 | USD |
| Block value | 12.8472 | USD |
| Market cap | 1280672071.0 | USD |
| Tracked solo pools | 12 | count |
| Recommended solo pool | herominers.com (0.9%) | |

## Tracked Solo Pools

| Pool | Solo Fee (%) | Avg Hashrate 7d (raw) | Avg Hashrate 7d | Reliability | Pool URL |
| --- | --- | --- | --- | --- | --- |
| herominers.com | 0.9 | 207113127776.78574 | 207.11 GH/s | OK | https://etc.herominers.com |
| woolypooly.com | 0.9 | 18075280426.964294 | 18.08 GH/s | OK | https://woolypooly.com |
| k1pool.com | 1 | 301711849593.45245 | 301.71 GH/s | OK | https://k1pool.com/pool/etcsolo |
| coolpool.top | 1 | 73104975772.79762 | 73.10 GH/s | OK | https://coolpool.top/pool/etcsolo |
| baikalmine.com | 1 | 10214702995.232141 | 10.21 GH/s | OK | https://baikalmine.com/pools/solo/etc/dashboard |
| 2miners.com | 1.5 | 428910916249.4049 | 428.91 GH/s | OK | https://solo-etc.2miners.com |
| kardanpool.com | 1.5 | 7804767866.071427 | 7.80 GH/s | OK | https://kardanpool.com/etc |
| molepool.com | 2 | 186661246592.26193 | 186.66 GH/s | OK | https://etc.molepool.com |
| ethcore.ru | 0.5 | 2160309729.473055 | 2.16 GH/s | Low hashrate | https://ethcore.ru/pool/etcpoolsolo |
| bitmernsolo.com | 1 | null | — | Low hashrate | http://bitmernsolo.com |
| nushypool.com | 1 | null | — | Low hashrate | https://nushypool.com/etc_solo/pool |
| himpool.com | 2 | 1725798508.2023816 | 1.73 GH/s | Low hashrate | https://himpool.com/pools/etc-solo |

## Expected Time to Solo Mine a Block (Poisson Model)

Block discovery is modeled as a memoryless Poisson process: `P(X >= 1) = 1 - exp(-t / T)` where `T = (Network Hashrate / Miner Hashrate) * Block Time`.

| Hardware / Scenario | Hashrate (raw H/s) | Hashrate (display) | Expected Time | 30-Day Probability |
| --- | --- | --- | --- | --- |
| 1× Jasminer X44-Q | 7790640000.0 | 7.79 GH/s | 3.1 days | 100.0% |
| 10× Jasminer X44-Q | 77906400000.0 | 77.91 GH/s | 7.3 hours | 100.0% |
| 100× Jasminer X44-Q | 779064000000.0 | 779.06 GH/s | 44 min | 100.0% |

## Solo Mining Protocol Rules

- Direct Coinbase Payout: When a solo miner finds a block, the pool constructs the block template with the miner's payout address directly in the coinbase transaction.
- Con Kolivas' Solo CKPool: Regarded as the historical benchmark for Bitcoin solo mining. Its pure C daemon processes shares with zero database overhead and pays miners directly through coinbase transaction outputs.
- Maturation: Newly minted coins require confirmation maturity (typically 100 blocks on Bitcoin and most PoW networks) before they can be transferred or spent.
- Pool Fee Structure: Unlike PPS/PPLNS pools that deduct fees from shared round rewards, solo pools deduct their percentage fee exclusively upon block discovery.
- High Variance: Finding blocks solo is subject to Poisson variance; expected time is a mathematical expectation over many trials, not a countdown timer.

## Provenance

- Retrieved: 2026-10-16T08:56:28Z
- Canonical page: https://backpow.com/solo-pools/EthereumClassic
- Coin economics & CoP datasheet: https://backpow.com/EthereumClassic.md
- All solo pools directory: https://backpow.com/solo-pools.md
- Solo mining odds calculator: https://backpow.com/EthereumClassic
- Live queries over MCP: https://mcp.backpow.com/mcp (tools `calculate_solo_mining_odds`, `get_coin_oracle`)
- Licence: CC BY 4.0 — https://backpow.com/llms.txt

Difficulty, hashrate and price move continuously. This file is a snapshot taken at the time above; for a current reading, query the MCP endpoint rather than caching this document.