Skip to content

test: fold long min-chain-work hex reject onto operator_conf_and_argv - #1025

Merged
reardencode merged 1 commit into
masterfrom
test/min-chain-work-hex
Oct 15, 2026
Merged

reardencode merged 1 commit into
masterfrom
test/min-chain-work-hex

Conversation

@rearden-grok

@rearden-grok rearden-grok Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Summary

  • operator_conf_and_argv refuses a 65-digit --min-chain-work hex spec through apply_kv. The error names the 64-digit limit.
  • Deletes minimum_chain_work_hex_and_floor. The 0x65 byte stays on that journey. A non-hex spec still exits 1 from the operator smoke. meets_minimum_chain_work stays on the testnet3 milestone journey and relay_requires_min_chain_work_even_when_following.

Test plan

  • cargo test -p rbitcoin-node --lib operator_conf_and_argv
  • fmt, clippy -D warnings, deny, ast-grep, ci-os-smoke.sh
  • Inverting the length reject makes operator_conf_and_argv fail; the operator was restored before commit
  • Workspace cargo test failed only on end_of_ibd_sh_interrupt (Electrum opened before script A history was complete), which this diff does not touch

operator_conf_and_argv already accepts --min-chain-work=0x65. It now
refuses a 65-digit hex spec through apply_kv, which is the outcome
minimum_chain_work_hex_and_floor asserted. The 0x65 byte, the non-hex
refusal, and meets_minimum_chain_work stay covered by that journey,
the operator smoke, and the testnet3 milestone journey.
@reardencode
reardencode merged commit 411db7a into master Oct 15, 2026
23 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant