Pepecoin Hashrate Migration

Whether mining power is arriving at or leaving Pepecoin right now — read from the direction of its per-block difficulty steps over the last 240 blocks, on our own node.
-0.3σ quiet dated fallback figures of 2026-10-31 — fetching live…
last 240 blocks (≈ 4 h) · mean difficulty +12.1% vs the prior 4 h · this chain’s typical 4-h move ±10.2% · as of 2026-10-31 · 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
Migration meter σ · one point per 60 blocks · 7 days
The meter in σ, one point per 60 blocks over the last 7 days, from our own node’s headers. Dotted guides = ±2σ (ordinary), dashed = ±4σ; 3σ reads “moving”, 5σ “strong”.
scroll = zoom · swipe / drag = move · double-click = reset
fetching the series from our own node…
how it’s computed →

Every Pepecoin block retargets difficulty, so each block leaves a step r = ln(D_i/D_{i−1}). Under steady hashrate the steps are near-independent and zig-zag; when hashrate is arriving or leaving they keep the same sign for hours. The meter is the lag-1 autocorrelation of the last 240 steps × √240 — under the constant-hashrate null that is a standard normal, so the σ scale is exact, not fitted.

Beside it the page shows the 4-hour mean-difficulty change against this chain’s own typical 4-hour move, measured over our archive — so a large but ordinary swing is not mistaken for a sustained one.

Window
240 blocks
≈ 4 h at the 60-second target
Mean difficulty, 4 h
+12.1%
vs the prior 240 blocks
Typical 4-h move
±10.2%
this chain’s own spread, from our archive
Reading
quiet
quiet below 3σ · moving 3–5σ · strong above
PlainIs mining power arriving at or leaving Pepecoin right now? Quiet means it is holding steady.
MinerPepecoin retargets every block, so difficulty steps up or down each block. When the steps keep going the same way for hours, hashrate is moving. Luck alone makes the steps zig-zag.
Advancedr = ln(D_i/D_{i−1}); σ = AC1(r) × √240 over the last 240 blocks. Under constant hashrate AC1 ~ N(0, 1/240): 3σ reads 'moving', 5σ 'strong'. The 4-hour mean-difficulty change is shown beside this chain's own typical 4-hour move, measured from our archive.
How it’s measuredserved verbatim in /api/chain/pep → recipe.migration · this block repaints from the live response
r_i = ln(difficulty_i / difficulty_{i-1}) per block; AC1 = lag-1 autocorrelation of r over the last 240 blocks (about 4 h at a 60 s target); sigma = AC1 x sqrt(240), because under constant hashrate the r_i are near-independent and AC1 ~ N(0, 1/240); net_4h = mean difficulty of the last 240 blocks vs the prior 240; typical_4h = the spread of that ratio over our own archive (not a Poisson figure — hashrate itself wanders)

What hashrate migration is

Hashrate migration is the persistence of Pepecoin’s per-block difficulty steps — a run of steps in one direction that block luck alone would not produce — read as mining power arriving at or leaving the chain. Pepecoin retargets every block (DigiShield, Dogecoin-1.14 class): every block moves difficulty by the damped ratio of the last interval to the 60-second target, so a chain whose hashrate is steady zig-zags around its level block by block, and a chain whose hashrate is moving steps the same way for hours.

Whose power moves on Pepecoin

On Pepecoin the power that moves is parent-pool power: PEP is merge-mined under Litecoin parent pools, so a “moving” reading here usually means a parent roster added or dropped PEP, not that PEP-side machines were switched on or off. In our dated attribution study (2026-10-02 → 2026-10-10), F2Pool 30.3%, ViaBTC 26.5% and AntPool 20.1% of PEP blocks carried those tags. In most LTC merge rosters PEP is the default second kicker after BELLS.

Ordinary swings on this chain

The typical 4-hour move for Pepecoin — ±10.2% in mean difficulty as of 2026-10-31 — is shown next to the live 4-hour change so a reader can tell a large but ordinary swing from a sustained one. On a 1,440-block-a-day chain a 4-hour window is 240 blocks, which is why the meter’s null distribution is N(0, 1/240) and why the σ scale needs no calibration.

FAQ

Why does Pepecoin qualify for this meter when Litecoin does not?
Pepecoin retargets every block (DigiShield), so each block leaves a difficulty step whose direction can be tested for persistence. Chains that retarget in epochs — Bitcoin, Litecoin, Namecoin — step once per epoch, and the meter is undefined between steps; for them the next-adjustment band is the equivalent instrument.
What does quiet mean here?
That the last 240 difficulty steps zig-zag the way luck alone would: the lag-1 autocorrelation of ln(D_i/D_i-1) is within 3 standard deviations of zero under the constant-hashrate null, whose variance is 1/240. It does not mean difficulty was flat — a 10.2% swing in the 4-hour mean is ordinary on Pepecoin.
Is this the Difficulty Ribbon?
No. The Difficulty Ribbon is a market-facing indicator built from moving averages of difficulty. This meter uses no market data and no moving average: it tests whether consecutive per-block retargets on Pepecoin keep the same sign longer than chance allows.
Source: BasinTwo's own Pepecoin full node — the meter, the 4-hour figures and the 7-day history come from /api/chain/pep and /api/nodes/pep, the same public JSON anyone can read; integrity seals ride every response. Updated every 60s in your browser.