CraftCoin Network Hashrate
What is CraftCoin's hashrate?
Hashrate is the number of scrypt hash attempts pointed at CraftCoin each second, shown here in TH/s (terahashes per second, 10¹² hashes/s). CraftCoin targets one block every 60 seconds, so hashrate decides how the chain's flat 2-CRC-per-block drip is divided among the machines doing the work — and on this chain the figure exists nowhere else: no explorer publishes it, and F2Pool's own coin page still shows the pre-relaunch block time.
The headline number is computed from our own node's headers: the total work the chain accumulated over the last day — the sum of difficulty × 2³² per block — divided by the elapsed seconds. That exact recipe ships inside the API response itself, next to the number.
Whose hashrate is this, really?
Mostly one pool's. CRC is merge-mined under Litecoin parent pools (AuxPoW chain ID 0x2024, verified in our node's block versions), and the parent coinbases stored inside our AuxPoW records name the workers: F2Pool tags signed 614 of the last 730 CRC blocks as of 2026-10-03 — about 84% — with LitecoinPool.org near 11% and Mining-Dutch and Binance Pool behind it. The number above is the slice of the Litecoin basket those rosters point at CRC.
The consequence is sharper here than on any sibling: one roster decision moves most of this chain's hashrate at once. F2Pool adding CRC on 2025-03-24 effectively WAS this chain's hashrate arriving — and the ribbon indicators on a cross read exactly that kind of basket decision, not miner capitulation in the Bitcoin sense.
How we measure it — and why we don't borrow numbers
headline estimate = total work over the last day ÷ elapsed seconds (the API recipe, from our own headers)
There is no CRC number to borrow even if we wanted one: the only explorer link miningpoolstats carries was unreachable when we checked (2026-10-03), and F2Pool's coin page lags our tip with placeholder dashes. Our CraftCoin node is synced block-by-block from genesis over the coin's P2P network — no snapshots, no third-party feeds — and integrity seals ride every API response. The "Implied hashrate" tile applies the first formula to the live difficulty as a cross-check on the day average; on a chain that retargets every block (DigiShield, Dogecoin-1.14 class), the two legitimately diverge for a while whenever difficulty has just moved.
Why it matters for miners
Your expected share of this chain's reward stream equals your hashrate divided by network hashrate — but you don't point a rig at CRC. You point a scrypt machine at a pool that carries it; F2Pool is the payer we verified end-to-end (PPLNS, 1-CRC threshold), and CRC rides in as a kicker on your LTC payouts, for hashes you were already doing. 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's hashrate move with Litecoin pools?
- Because almost none of the work is CRC-side work. CraftCoin is merge-mined (AuxPoW) under Litecoin parent pools, and our own AuxPoW records put F2Pool's tags on about 84% of the last 730 blocks (as of 2026-10-03), with LitecoinPool.org, Mining-Dutch and Binance Pool carrying most of the rest. The hashrate pointed at this chain is whatever slice of the Litecoin fleet those rosters aim at it — a roster change moves this number with no CRC-side decision anywhere.
- What is merged mining (AuxPoW)?
- One round of hashing, two chains. A Litecoin miner embeds a commitment to a CraftCoin block in its LTC work; a solution good enough for CraftCoin's difficulty counts on the CRC chain via AuxPoW, at zero extra electricity. CraftCoin signals this with AuxPoW chain ID 0x2024 — a relaunch-year vanity hex we verified in our own node's block versions. That carriage, not standalone CRC rigs, is where CRC blocks come from.
- Can CRC's hashrate change when no miner touched CRC?
- Yes — and this chain is close to a pure case. When F2Pool folded CRC into its LTC merge roster on 2025-03-24, work arrived without a single machine changing what it hashed; if a dominant roster dropped it, most of the chain's hashrate would leave the same way. Basket add/drop decisions are precisely what the ribbon indicators on the CRC dashboard are reading.
- Where is the historical chart?
- No public CraftCoin hashrate history series exists anywhere, and we do not draw charts from data we do not have. BasinTwo's own node has archived every CRC block forward since 2026-10-02; the chart ships the day our archive serves the series.