AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 22 Bitcoin

Merge bitcoin/bitcoin#36196: contrib, kernel: fixed seeds, chainparams, headerssync params, and assumeutxo updates pre-32.0

Public commit record

What the developer wrote

Authored by merge-script

81/100 · Strong
Merge bitcoin/bitcoin#36196: contrib, kernel: fixed seeds, chainparams, headerssync params, and assumeutxo updates pre-32.0

fed50258f8f07d5549f2b53689671ca1412b2d63 kernel: add recent assumeutxo snapshot (Ava Chow)
7eb4cec1a983e199bf2b0f3986f50b56a2d30ccb kernel: Update headerssync params (Ava Chow)
42d93d40de3586e0e482de70320b4993b8a06317 kernel: update chainTxData (Ava Chow)
a25511dfbcd3412526e18e639e3df2aa4b751c08 kernel: update defaultAssumeValid and minimumChainWork (Ava Chow)
67726a63a41f7f9d89e0c8d7772b17eb1f7113b4 kernel: update assumed blockchain and chainstate sizes (Ava Chow)
fcfc1df041b8cecbc2bb4bf6836f5ba643f298a5 contrib: Update fixed seeds (Ava Chow)
6385aa1df8ab413c66c9b2f83df4eed4e9c03417 contrib: Update makeseeds for 30.3 and 31.x (Ava Chow)

Pull request description:

All the updates per the release process, except asmap.

Assumeutxo snapshots are available at https://achow101.com/files/utxo-snapshots/

ACKs for top commit:
fanquake:
ACK fed50258f8f07d5549f2b53689671ca1412b2d63
sedited:
Reproduced ACK fed50258f8f07d5549f2b53689671ca1412b2d63

Tree-SHA512: ae6d79a5216fe6a919376aa36da9afd1b0ae81d8aba96ab88fa85f3c5c0b5fe13d91ead66103ca7ba54b05a638363145c31d40c2050ec79bf3dab4fb1b4da666
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This is a routine Bitcoin Core release-maintenance commit. It refreshes the list of network seed nodes, updates the built-in checkpoints that tell the software how much blockchain history to trust by default, adds newer 'assumeutxo' snapshots for faster initial setup, and adjusts header-sync tuning parameters. None of these changes fix a known bug or vulnerability; they are standard pre-release housekeeping to keep the client in sync with the live network.

Recommended action

No security action required. Treat as normal release-process maintenance; verify the new checkpoints and assumeutxo hashes against independently observed chain data if performing a release audit.

Security signals we found

01

Hard-coded network seeds changed (expected release-process refresh)

02

minimumChainWork/defaultAssumeValid checkpoints advanced (expected release-process refresh)

03

New assumeutxo snapshots added (expected release-process refresh)

04

headerssync anti-DoS parameters regenerated (expected release-process refresh)

Risk score

Why this scored 22/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 5/15
Confidence 9/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.