Skip to content

deploy: chain-22 cut — NODE21 for chain 21's genesis probe; state_proof_keys by key set - #200

Merged
dendisuhubdy merged 2 commits into
mainfrom
fix/cut22-chain21-probe-node21
Nov 21, 2026
Merged

dendisuhubdy merged 2 commits into
mainfrom
fix/cut22-chain21-probe-node21

Conversation

@dendisuhubdy

Copy link
Copy Markdown
Member

Two refusals from the real chain-22 cut on 2026-11-20, run from the build droplet at v0.8.7:

  1. The chain-21 genesis probe. $NODE init deploy/genesis-chain21.json fails because a set-11 rand-node refuses chain 14–21 files by design. The new input NODE21 (chain 21's v0.8.6 rand-node) runs that one probe and defaults to NODE. Chain 21's treasury id is d5fd1883… under both binaries, so treasury_id_of is unchanged.
  2. The CON-601 perps.state_proof_keys check compared dict key order. rand-node writes the fields sorted, so the four correct tier-18 shapes were refused. The check now compares the key set; the values and per-file sha256 pins are still checked.

With both fixes, the cut ran with rc=0 (rehearsal genesis ea067d48…, set aside; the launch re-cuts). SELFTEST=1: 546 passed and 1 failed. The failure was environmental: the droplet had no durian checkout at the default DURIAN path. A re-run with DURIAN set is noted below.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8

…), and reads state_proof_keys by key set

Two refusals hit on the real cut (2026-11-20, from the build droplet):

- The probe that re-derives chain 21's genesis hash ran `$NODE init` on
  deploy/genesis-chain21.json. NODE is the cut build (v0.8.7, constraint set 11), which refuses to
  init any chain 14-21 file by design ("proofs were made under constraint set 9 ... refusing to
  init"). NODE21, chain 21's rand-node (v0.8.6), now runs that one probe. It defaults to NODE, so the
  self-test's fake node keeps working. Chain 21's treasury id is the same under both binaries
  (d5fd1883...), so treasury_id_of keeps NODE.
- The CON-601 check compared perps.state_proof_keys entries by dict key ORDER. rand-node writes the
  fields sorted, so the four correct canonical shapes were refused. It now compares the key set; the
  values and the per-file sha256 pins are checked as before.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8
@dendisuhubdy

Copy link
Copy Markdown
Member Author

SELFTEST=1 re-run with DURIAN pointed at the set-11 engine artifacts: 547 passed, 0 failed.

rand-node beacon status --rpc refuses a bare host:port ("relative URL without a base"), so wait
failed all 25 validators on the live chain 22 (2026-11-21 03:16Z); with the scheme, 25/25 open.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8
@codecov

codecov Bot commented Nov 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@dendisuhubdy
dendisuhubdy merged commit b419531 into main Nov 21, 2026
23 checks passed
@dendisuhubdy
dendisuhubdy deleted the fix/cut22-chain21-probe-node21 branch November 21, 2026 04:35
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