What the developer wrote
Authored by Peter D. Gray
block bump
What changed, and why it matters
This commit simply updates a minimum block height number in the Bitcoin mainnet configuration from 916,210 to 922,061. This is a routine date/height adjustment, not a security fix. It affects when a COLDCARD feature (likely related to a protocol or service activation) becomes available, but does not patch any vulnerability.
No security action required. Treat as routine configuration/maintenance update.
Security signals we found
No security-relevant code changes
Single constant update for activation height
No input validation, cryptography, or authorization changes
Evidence from the diff
The change modifies ccc_min_block in shared/chains.py for the BitcoinMain class. This constant appears to gate activation of a feature based on the current Bitcoin block height. The update pushes the activation threshold forward from block 916,210 (estimated Sep 24, 2025) to block 922,061 (estimated Nov 3, 2025). No logic changes, bounds checks, or security controls were modified.
Changed components
shared/chains.py: BitcoinMain.ccc_min_blockInspect captured patch +1 / −1
diff --git a/shared/chains.py b/shared/chains.py
index ad29e16..fd9efd0 100644
--- a/shared/chains.py
+++ b/shared/chains.py
@@ -313,7 +313,7 @@ class BitcoinMain(ChainsBase):
# see <https://github.com/bitcoin/bitcoin/blob/master/src/chainparams.cpp#L140>
ctype = 'BTC'
name = 'Bitcoin Mainnet'
- ccc_min_block = 916210 # Sep 24/2025
+ ccc_min_block = 922061 # Nov 3/2025
slip132 = {
AF_CLASSIC: Slip132Version(0x0488B21E, 0x0488ADE4, 'x'),
Why this scored 32/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.