Why does CraftCoin difficulty change every block?

CraftCoin retargets every block (DigiShield, Dogecoin-1.14 class) — the rule its relaunch codebase carries. Instead of waiting out a 2,016-block epoch like Bitcoin or Litecoin, every new block triggers a recalculation against the 60-second target, damped so one lucky or unlucky block only nudges the value. The next adjustment is always about a minute away.

Does CraftCoin have halvings?

Measured: no. The subsidy stepped once, by design, early in the schedule — 10 CRC through block 31,999, 2 CRC from block 32,000 — and has stayed a flat 2 CRC for more than a million blocks since: still 2 CRC at block 1,113,203, read from actual coinbases on our own node on 2026-10-03. There is no 100,000-block halving cadence here, unlike most of its Dogecoin-1.14-class siblings. The announced total supply is 100,000,000 CRC; at a flat 2 CRC a minute that ceiling is many decades out, and we report the schedule as the coinbases show it, not as documents promise it.

Is CRC harder to mine than LTC or DOGE?

The difficulty numbers cannot be compared — each chain's difficulty is a ratio against its own genesis minimum, and the chains run different block targets. In practice the question dissolves: through AuxPoW the same scrypt machines mine LTC, DOGE and CRC at once, so nobody chooses between them — a pool roster chooses which kickers ride along, and for CRC that roster is mostly F2Pool's.

A pressure gauge computed from recent block pace: g is derived from elapsed time versus target and E = (g² − 2) / (πg), clamped to [−1, +1] — positive means blocks are running slower than target (difficulty pressure easing), negative means faster (pressure building). The full recipe, constants included, is published in the API response at basintwo.com/api/chain/crc.

CraftCoin Difficulty — Live, Per-Block DigiShield

What is difficulty?

Difficulty is a single network-wide number that sets how much computational work it takes to find a valid CraftCoin block. The higher it is, the more scrypt hashes — on average — must be tried before a block lands. It exists so that no matter how much of the Litecoin parent-pool basket points at this chain, blocks keep arriving roughly every 60 seconds.

The headline reading (e.g. "11.18 M") is the raw difficulty scaled for display — M = million (×10⁶). It is a ratio against the minimum difficulty of the chain's first block: that many times harder to mine than at genesis — a block stamped, on this chain, 2013-06-12.

How DigiShield recalculates it — every block

new_difficulty = old_difficulty × (target_timespan ÷ damped_actual_timespan)
· recomputed at EVERY block — a ~1-minute cadence on this chain (DigiShield)
· damping tempers each step, so one fast or slow block only nudges the value

Bitcoin and Litecoin adjust in 2,016-block epochs; CraftCoin's Dogecoin-1.14-class relaunch code dropped epochs for DigiShield, so difficulty drifts continuously instead of jumping — there is no epoch progress bar and no next-adjustment date on this page because the next adjustment is always about a minute away.

Our headers hold a live demonstration of why that matters on a merge-mined chain: the relaunch's first ~18 hours produced 41,700 blocks, parent-pool scrypt work hammering a chain whose difficulty started near genesis-minimum, with DigiShield climbing block by block to meet it. An epoch-retargeting chain would have spent weeks in that state. One more honesty note: the cadence we publish is measured on our own node — the repository README still carries a 60-block sampling rule from an earlier era, which is exactly why we measure instead of quoting documentation.

The pressure gauge: e_hafeer, recipe included

The "Difficulty pressure" tile is e_hafeer, a signed [−1, +1] reading of recent block pace. +1 means blocks are running far slower than target, so difficulty pressure is easing — a tailwind for the machines already here; −1 means far faster, pressure building — the same machines are about to earn proportionally less. As of 2026-10-03 it read +0.004 — inside the neutral band. The receipt is the recipe itself, served inside every API response and quoted here verbatim:

last 2016 block timestamps: g = sqrt(2 x elapsed/target), clamped to [0.542826416334146, 3.684419069923939] (the positive root of x^2+pi*x-2=0 and its Vieta partner 2/root); E=(g^2-2)/(pi*g). +1 = blocks far slower than target (difficulty pressure down), -1 = far faster (pressure up)

One display convention is ours, not the recipe's, so we state it: the tile colors the reading only beyond ±0.005 — green above +0.005 (pressure easing), amber below −0.005 (pressure building), neutral in the band between. With the formula above and the raw feed, every pixel of that coloring is checkable.

Merged mining and difficulty

Each chain computes its own difficulty — Litecoin in 2,016-block epochs, CraftCoin every block. The work feeding both is the same scrypt work, routed by parent-pool merge rosters, and on CRC that routing is unusually concentrated: our own AuxPoW records put about 84% of recent blocks under F2Pool parent tags (as of 2026-10-03). So this page largely tracks one basket's behavior — when that roster re-aims, blocks run fast, e_hafeer swings negative, and difficulty climbs within minutes.

One claim we deliberately do not make: a fixed difficulty ratio between CRC and LTC. That shortcut assumes the whole Litecoin fleet mines the cross, and our measured attribution says CRC's carriage is mostly one pool's slice — so no ratio is quoted. We say so rather than guess.

Why it matters for miners

Your revenue is your share of the network, so a sustained +5% rise in difficulty cuts revenue per MH/s by about 4.8% (1 − 1/1.05). On CRC that arrives as a drift, not a cliff — per-MH/s earnings erode or recover block by block instead of stepping every epoch. And because CRC reaches scrypt miners as a kicker on LTC payouts (F2Pool, PPLNS, 1-CRC threshold is the carriage we verified end-to-end), this chain's difficulty moves the bonus layer of a rig's income, stacked on top of the LTC side rather than replacing it. Our archive also catches CRC blocks under LitecoinPool.org, Mining-Dutch and Binance Pool parent tags — AntPool tags appear only back in the December 2024 launch window — so check those pools’ payout pages before counting on a CRC kicker.

FAQ

Why does CraftCoin difficulty change every block?: CraftCoin retargets every block (DigiShield, Dogecoin-1.14 class) — the rule its relaunch codebase carries. Instead of waiting out a 2,016-block epoch like Bitcoin or Litecoin, every new block triggers a recalculation against the 60-second target, damped so one lucky or unlucky block only nudges the value. The next adjustment is always about a minute away.
Does CraftCoin have halvings?: Measured: no. The subsidy stepped once, by design, early in the schedule — 10 CRC through block 31,999, 2 CRC from block 32,000 — and has stayed a flat 2 CRC for more than a million blocks since: still 2 CRC at block 1,113,203, read from actual coinbases on our own node on 2026-10-03. There is no 100,000-block halving cadence here, unlike most of its Dogecoin-1.14-class siblings. The announced total supply is 100,000,000 CRC; at a flat 2 CRC a minute that ceiling is many decades out, and we report the schedule as the coinbases show it, not as documents promise it.
Is CRC harder to mine than LTC or DOGE?: The difficulty numbers cannot be compared — each chain's difficulty is a ratio against its own genesis minimum, and the chains run different block targets. In practice the question dissolves: through AuxPoW the same scrypt machines mine LTC, DOGE and CRC at once, so nobody chooses between them — a pool roster chooses which kickers ride along, and for CRC that roster is mostly F2Pool's.
What is e_hafeer?: A pressure gauge computed from recent block pace: g is derived from elapsed time versus target and E = (g² − 2) / (πg), clamped to [−1, +1] — positive means blocks are running slower than target (difficulty pressure easing), negative means faster (pressure building). The full recipe, constants included, is published in the API response at basintwo.com/api/chain/crc.