[PastaPastaPasta]

Issue being fixed or feature implemented

Backport of #7980 (develop) to v24.0.x, so v24.0.0-rc.5 ships with fresh seeds, checkpoints, nMinimumChainWork, defaultAssumeValid, chainTxData and assumed sizes. These are the per-release chain parameter updates from doc/release-process.md. The pattern matches #6920 for v23: develop first, then the release branch.

What was done?

Both #7980 commits were cherry-picked with -x onto the v24.0.x tip (47814b0). Two adaptations were needed:

• src/chainparams.cpp: develop moved this file to src/kernel/chainparams.cpp, so the same hunks were applied here. The changed lines are identical to chore: update seeds, checkpoints, minimum chain work, assumevalid and tx stats for v24 #7980's.
• contrib/seeds/README.md: this branch still has the pre-asmap README. Only the protx list valid true 2563000 fix is carried over. The seed lists and src/chainparamsseeds.h were generated with develop's tooling (asmap-based ASN lookup) and are byte-identical to chore: update seeds, checkpoints, minimum chain work, assumevalid and tx stats for v24 #7980's. The input files on both branches were identical before the change.

Values, all read from fully synced v24.0.0-rc.4 nodes:

	Mainnet	Testnet
Block	2563000	1550000
Hash (new checkpoint, defaultAssumeValid)	000000000000000346a1804da4832b0b69dd9a7f96b14c7cb54585a9ac6ae98f	000000116cd3c11d44c88cbc0a26804bd277a5d790f684ec3a8aaa820690318c
nMinimumChainWork	0x…c15981a81af44a6abe1a	0x…03ed573a939487fc
chainTxData (getchaintxstats 17280 <hash>)	1793218693 / 71411418 / 0.1306891420721072	1788899589 / 8494561 / 0.0139463532250889
m_assumed_blockchain_size	57 → 62 (synced datadir 56G, plus 10%)	10 (unchanged; synced datadir 6.3G)

Seeds:

• Mainnet: 239 IPv4 and 10 onion seeds from protx list valid true 2563000.
• Testnet: 25 seeds from protx list valid true 1581000.
• The 15 onion seeds that failed two Tor connection attempts were removed.

See #7980 for the full method.

How Has This Been Tested?

• Re-checked just before this PR on the synced nodes, read-only:
  • getblockheader at 2563000 (612 confirmations) and at 1550000 returns exactly the hashes and chainwork above.
• On chore: update seeds, checkpoints, minimum chain work, assumevalid and tx stats for v24 #7980 (develop), with the same values and seed data:
  • The unit tests that read chain parameters pass.
  • A node on empty mainnet and testnet datadirs with -dnsseed=0, bootstrapping only from the new fixed seeds, synced headers past both new checkpoints. Mainnet reached 2563592 from 239 seeds and testnet reached 1581891 from 25 seeds. There were no checkpoint or bad-fork errors.
• On this branch: built dashd and test_dash at da6c192 (Linux x86_64, depends). The unit tests versionbits_tests, validation_tests, validation_chainstatemanager_tests, net_tests and checkqueue_tests pass with *** No errors detected.
• Follow-up check, not run: release-process.md's -reindex-chainstate -assumevalid=0 pass over mainnet history.
• Mainnet EHF state at the tip: from V20 activation to 2563584 there are no MNHF_SIGNAL transactions for bit 13 or 14, and no block in the last 4032 signals them.

Breaking Changes

None.

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have assigned this pull request to a milestone

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-29T23:05:58.952705Z We couldn’t complete this review. Comment @codex review to try again.	da6c192	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[thepastaclaw]

🕓 Review not started yet because the new head is waiting for the 30-minute push debounce.

• Request normal review — click when the PR is ready for review.
• Request priority review — click to move this review to the front of the queue.

Commit 129a1fc. Normal review starts when eligible; priority review starts as soon as a slot is available.

[thepastaclaw]

Final validation — Phase 1 + Phase 2

No actionable in-scope defects were identified. The chain-parameter updates and regenerated fixed-seed data are internally consistent and match the intended backport, with successful title validation, conflict prediction, and amd64 container builds; arm64 container builds were still in progress at the evidence timestamp.

Review provenance

Source: reviewer 1: muse-spark-1.3-contributor (agent: phase1-reviewer, role: general); reviewer 2: gpt-6.1-sol (agent: phase2-reviewer, role: general); reviewer 3: gpt-6.1-sol (agent: phase2-reviewer, role: backport-reviewer); reviewer 4: gpt-6.1-sol (agent: phase2-reviewer, role: dash-core-commit-history); final verifier: gpt-6.1-sol (agent: sol-verifier, role: final-verifier)

• Triage: normal by gpt-6.1-sol (effort low) — This is a contained release-parameter and seed-data update, but it changes chain validation assumptions and peer bootstrap data enough to warrant ordinary review without meeting the critical-surface threshold.
• Phase 1 reviewers: muse-spark-1.3-contributor — general (completed, effort xhigh); agent phase1-reviewer
• Phase 1 model: muse-spark-1.3-contributor — not quota-gated; passed over gemini-3.8-flash-high (antigravity quota lookup failed), glm-5.3-flash (not used above high effort; tier asks max)
• Fresh verifier: gpt-6.1-sol — final-verifier; agent sol-verifier
• Phase 2 reviewers: gpt-6.1-sol — general (completed, effort high); agent phase2-reviewer, gpt-6.1-sol — backport-reviewer (completed, effort high); agent phase2-reviewer, gpt-6.1-sol — dash-core-commit-history (completed, effort high); agent phase2-reviewer