ASERT Explained

ASERT (Absolutely Scheduled Exponentially Rising Targets, implemented as aserti3-2d) is Bitcoin Cash’s difficulty adjustment algorithm, live since November 2020, which recalculates mining difficulty for every single block instead of every 2,016 blocks like Bitcoin. It measures how far the chain’s real timeline has drifted from its ideal 10-minute-per-block schedule since a fixed anchor point, and steers difficulty back exponentially with a two-day half-life. The effect that matters to solo miners: continuous, cliff-free adjustment that erases the profitable windows opportunistic hashrate uses to raid a chain — protecting the odds of everyone who mines steadily.

Key takeaways

• Per-block, not per-epoch. Bitcoin holds difficulty fixed for ~2,016 blocks then jumps; ASERT nudges it every block. No plateaus means no windows — the single most important consequence for miners.
• The formula is one line. next_target = anchor_target × 2^((actual_time − scheduled_time) / half_life). Difficulty is just the anchor’s difficulty scaled by how far ahead or behind schedule the chain has drifted.
• Two-day half-life is the tuning knob. Run two days ahead of schedule and difficulty doubles; two days behind and it halves. Fast enough to track real hashrate, slow enough to ignore lucky-block noise.
• It was built to reward steady miners. ASERT’s explicit design goals included minimizing the profit advantage of switch-miners who hop between chains — which is exactly the protection a solo miner on a minority chain wants.
• The same design can trap a chain that’s too small. A brief hashrate flood spikes difficulty; when it leaves, a tiny chain can grind for ~6.6 days recovering from a 10× spike. This is why ASERT’s behavior on small chains is a feature and a hazard at once.

This article sits in our difficulty-science cluster alongside the Bitcoin Cash profile, where ASERT is the chain’s armor, and the BC2 retarget-window guide, which explores the opposite world — a chain where windows still exist and can be played. Understanding ASERT is understanding why some chains have those windows and others don’t.

The problem ASERT was built to solve

Every proof-of-work chain must answer one question continuously: as hashrate joins or leaves, how do we keep blocks arriving about every ten minutes? Bitcoin’s original answer — recalculate every 2,016 blocks from the previous epoch’s pace — works beautifully when hashrate is enormous and stable. On a smaller chain it fails in a specific, exploitable way.

Bitcoin Cash learned this the hard way. Its first difficulty algorithm after the 2017 fork, and an emergency adjustment before it, produced violent oscillations: difficulty would drop, opportunistic “switch miners” would flood in to mint easy blocks, difficulty would lurch back up, they’d leave, and the chain would stall until the next drop — a sawtooth that hurt everyone mining steadily. The pattern had a name and a victim: the profitable window, and the loyal miner whose share it diluted. ASERT was designed, after extensive simulation against competing algorithms, specifically to flatten that sawtooth — and its stated goals included keeping block times near target, keeping confirmation times near target, and reducing the profitability gap between steady miners and switchers.

How aserti3-2d actually works

The whole algorithm is one elegant formula:

next_target = anchor_target × 2^{((time_delta − ideal_block_time × (height_delta + 1)) / half_life)}

Read it in plain language. Take a fixed anchor block from the chain’s past — for Bitcoin Cash, the block just before ASERT activated. Its difficulty is the permanent baseline. Now for any new block, compute two things: time_delta, how much real time has actually passed since the anchor, and the scheduled time, which is simply ideal_block_time (600 seconds) times the number of blocks since the anchor. The difference between them — is the chain ahead of or behind its ideal timetable? — goes into the exponent, divided by the half-life. If the chain is exactly on schedule, the exponent is zero, 2⁰ = 1, and difficulty equals the anchor’s. Run ahead of schedule and the exponent goes positive, doubling difficulty for every half-life of lead. Fall behind and it goes negative, halving difficulty for every half-life of lag.

Two design choices make it robust. Because the anchor is absolute (a fixed point, never a rolling window), rounding imprecision can’t accumulate over months — every block is computed fresh from the same origin. And because floating-point math produces different results on different processors — a consensus catastrophe waiting to happen — ASERT approximates the exponential with fixed-point integer arithmetic and a cubic polynomial, so every node on every machine computes byte-identical difficulty. It’s a control-system feedback loop dressed as three lines of integer code.

The two-day half-life: the number that matters

The half-life is ASERT’s personality. Bitcoin Cash chose two days (technically 288 blocks’ worth of ideal time), and the human-readable version is exactly as clean as it sounds: for every two days the chain gets ahead of schedule, difficulty doubles; for every two days it falls behind, difficulty halves.

Why two days specifically? It’s a balance point found in simulation. Too short a half-life and difficulty twitches at every lucky streak of fast blocks, overreacting to statistical noise — the chain never settles. Too long and it responds sluggishly to genuine hashrate changes, drifting off-target for days and reopening the very windows it was meant to close. Two days sits in the sweet spot: responsive within roughly a day to real shifts, deaf to the random jitter of individual blocks. The practical arithmetic that falls out of it: recovering from a 2× difficulty spike takes 2 days, a 4× spike 4 days, and a 10× spike about 6.6 days — numbers that become very important the moment a chain is small.

What ASERT means for a solo miner

Three consequences, in order of importance.

Your steady odds are protected. This is the headline. On an epoch-retarget chain, a burst miner can wait for a difficulty drop, flood in during the easy window, and leave before the correction — every easy block they mint is one you didn’t, diluting your share of a rigged interval. ASERT erases that window: difficulty rises the instant they arrive and falls the instant they leave, block by block, so there’s no lag to farm. The loyal miner’s expected share stays clean.

The difficulty you see is honest. On Bitcoin, today’s difficulty reflects the network of up to two weeks ago; on an ASERT chain it reflects the network of the last few blocks. When you compute your odds — in the calculator or by hand — an ASERT chain’s number is a live price, not a trailing average, so your probability estimate is as current as the chain itself.

You cannot time it — and neither can anyone else. The flip side of protection is that ASERT offers no clever entry point. There’s no difficulty drop to swoop in on, because any drop is already priced in for the whole network simultaneously. This is the exact opposite of the playable dynamic on retarget-window chains, and it’s a fair trade: you give up the chance to game the schedule in exchange for a guarantee that nobody games it against you.

The small-chain paradox: ASERT’s sharpest edge

Here is where the elegance turns double-edged. ASERT’s responsiveness assumes a chain has enough steady hashrate that difficulty tracks a real, persistent signal. Give it a chain with very little hashrate, and a single large miner becomes a weapon — not always maliciously, sometimes just by showing up.

The failure mode: a big miner points serious hashrate at a tiny chain for a few hours. Blocks fly, the chain races far ahead of schedule, and ASERT dutifully spikes difficulty upward — perhaps 10×. Then the big miner leaves. Now the chain’s normal, modest hashrate faces a difficulty built for ten times its size, and blocks slow to a crawl. At the standard two-day half-life, clawing back from a 10× spike takes about 6.6 days — nearly a week in which the chain is effectively frozen, confirmations stall, and the loyal miners the algorithm was meant to protect are the ones left grinding. It’s the difficulty-algorithm version of a stress injury: the muscle that makes a healthy chain strong can tear a weak one.

This is why newer and smaller SHA-256 chains that adopt ASERT frequently launch with a shortened half-life — recovering from spikes in hours instead of days — accepting a bit more noise sensitivity in exchange for survivability. It’s also a large part of why very small chains are riskier to mine than their attractive odds suggest, a trade-off worth understanding fully before pointing hashrate at the bottom of the ladder.

Conclusion

ASERT is one of proof-of-work’s quiet masterpieces: a one-line formula, an integer approximation of an exponential, and a two-day half-life that together turn a violent difficulty sawtooth into a smooth, cliff-free curve. For the solo miner on Bitcoin Cash, it works invisibly and in your favor — protecting your share from switch-miners, keeping your odds honest to the minute, and asking only that you give up a gaming opportunity you’d never have won anyway.

And in its sharpest edge — the small-chain spike trap — it teaches the deepest lesson in the difficulty-science cluster: the same mechanism can be armor or hazard depending entirely on how much hashrate stands behind it. Know which chain you’re on, and you know which ASERT you’re mining.