Junkcoin Pool Share Shift

Each pool’s share of today’s JKC blocks against its own trailing week, scored in σ — attribution read from the Litecoin coinbase inside each AuxPoW header, on our own node.
F2Pool -1.8 pp -2.1σ · quiet dated fallback figures of 2026-10-31 — fetching live…
2026-10-30 (UTC day) vs trailing 7 days · F2Pool 87.1% → 85.3% · 1,471 blocks that day · from our own node
Read these figures honestlymerged-mined (AuxPoW) under LTC parent pools: hashrate here is the slice of the parent-pool basket pointed at this chain, and ribbon capitulation/recovery reflects parent-pool basket add/drop decisions, not direct miner economics on this chain
Pool share % of the day’s blocks · daily
Daily share of JKC blocks by parent pool, last 30 full UTC days — parent-pool tag from the AuxPoW header on our own node. One line per pool (top 6 by trailing share); today’s partial day is not drawn.
scroll = zoom · swipe / drag = move · double-click = reset
fetching the series from our own node…
how it’s computed →

Each day’s share is that pool’s blocks divided by all JKC blocks found that UTC day, the pool read from the Litecoin coinbase inside each AuxPoW header. Only complete days are drawn — today never is.

The six pools with the largest trailing share are drawn; everything else is counted as other. The headline score is z = (s − s̄) / √(s̄(1−s̄)/N) against the trailing seven full days: |z| ≥ 4 is an event, pools under 2% of trailing share are not scored, and days with fewer than 50 blocks are skipped.

Blocks that day
1,471
2026-10-30 · last full UTC day
Pools scored
3
≥ 2% of the trailing week’s blocks
Events, 30 days
0
|z| ≥ 4 · pool-days
Attribution
parent-pool tag from the AuxPoW header
read from the Litecoin coinbase
PlainDid one mining pool suddenly win a lot more, or far fewer, of today's Junkcoin blocks than it normally does? Quiet means no.
MinerEach pool's share of the day's blocks is compared with its own trailing week. Scored in σ, so ordinary block luck — large on a single day — is separated from machines actually moving between pools.
Advancedz = (s − s̄) / √(s̄(1−s̄)/N): s = pool share today, s̄ = its trailing-7-day share, N = blocks today. Event at |z| ≥ 4 — luck alone crosses that line less than once per pool per century of days.
Shift events (|z| ≥ 4) — last 30 full days
no |z| ≥ 4 event in the last 30 full days — every scored pool stayed within luck of its trailing week
How it’s measuredserved verbatim in /api/pools/jkc → recipe · this block repaints from the live response
s_p(d) = blocks found by pool p on UTC day d / all blocks that day; baseline = the pool's share over the trailing 7 full days; z = (s_p(d) - baseline) / sqrt(baseline*(1-baseline)/N_d) (binomial, N_d = blocks that day); event = |z| >= 4; pools below 2% trailing share are not scored

What a pool share shift is

Pool share shift is the one-day change in a mining pool’s share of Junkcoin blocks, measured against that pool’s own trailing week and scored in standard deviations of block luck. On Junkcoin the pool behind a block is read from the Litecoin coinbase embedded in its AuxPoW header — JKC is merge-mined under Litecoin parent pools, so a shift here is a shift in whose parent work carried JKC that day, not a decision any JKC-side miner made. In our dated attribution study (2026-10-02 → 2026-10-10), F2Pool 87.5%, Made in USA 8.0% and Mining-Dutch 2.6% of JKC blocks carried those tags. The Junkcoin Foundation publishes its own merge-mining tutorials aimed at home miners.

How much is luck on Junkcoin

Junkcoin targets a block every 60 seconds — about 1,440 a day — so a pool holding 87.5% of the chain — F2Pool, in our dated attribution study (2026-10-02 → 2026-10-10) — expects to wobble about ±0.9 percentage points on an ordinary day from luck alone. The event line is drawn at four of those standard deviations, from that arithmetic and nothing else; a day that reads 2σ is weather, not news. Retarget cadence is irrelevant here (Junkcoin difficulty retargets every 1,440 blocks (~24 hours at the 60-second target) — measured at epoch boundary 1,166,400 on our own node, 2026-10-09): difficulty decides how many blocks a day there are, not who finds them.

FAQ

Is a 2σ move on Junkcoin an event?
No. With about 1,440 JKC blocks a day, a pool holding 87.5% of the chain wobbles about ±0.9 percentage points from luck alone. The line is drawn at 4σ so that pure luck produces fewer than one false event per pool per century of days.
Does this say who mines Junkcoin?
It names who found the Litecoin parent block. Junkcoin is merge-mined under Litecoin parent pools, and some parent pools do not pay JKC to their miners — the note at the top of this page says so. A shift here is a shift in whose parent work carried JKC that day.
Why share of blocks and not hashrate per pool?
Pool hashrate is not on-chain; block counts are. A pool’s share of the day’s blocks times the network hashrate is an estimate with its own luck error bar, so we score the share itself — the quantity our Junkcoin node can actually count.
Source: BasinTwo's own Junkcoin full node — the pool shares, the receipt and the tip height come from /api/pools/jkc, /api/chain/jkc and /api/nodes/jkc, the same public JSON anyone can read; integrity seals ride every response. Updated every 60s in your browser.