AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 60 Cryptographic libraries

cryptonote: scope 202612 PoW workaround

Public commit record

What the developer wrote

Authored by selsta

68/100 · Adequate
cryptonote: scope 202612 PoW workaround

The block 202612 PoW workaround previously applied to any block at
height 202612. Restrict it to the object hashes of the known historical
mainnet, testnet, and stagenet block hashing blobs so new chains do not
inherit the fixed PoW hash, which would prevent sync or mining past that
height if their difficulty is higher.

Reported-by: DataHoarder
Co-authored-by: jeffro256 <jeffro256@tutanota.com>
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit narrows a long-standing special-case workaround for Monero block 202612. Previously, any new blockchain fork would have inherited a hard-coded proof-of-work hash at that exact height, which could stop nodes from syncing or miners from producing valid blocks if the network's difficulty was higher than the fixed value. The change now applies the workaround only to the known historical mainnet, testnet, and stagenet blocks, so new or private chains compute proof of work normally.

Recommended action

Review whether any other network-specific hard-coded workarounds in the consensus path are similarly over-broad. Ensure downstream forks and private testnets are aware that block 202612 now requires the exact historical hashing blob to receive the legacy PoW hash. Run the new unit tests on all supported build configurations.

Security signals we found

01

Hard-coded consensus bypass scoped to explicit historical block hashes

02

Potential chain-split/sync failure for new networks or private testnets at height 202612

03

Workaround originally intended for a historical block-202612 bug now restricted

04

Added unit tests assert both preservation of legacy hash and rejection of arbitrary blobs

Risk score

Why this scored 60/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 8/15
Affected reach 10/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.