Repository navigation
deploy: chain-22 cut — NODE21 for chain 21's genesis probe; state_proof_keys by key set - #200
Merged
Merged
Conversation
…), 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
Member
Author
|
SELFTEST=1 re-run with |
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 Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two refusals from the real chain-22 cut on 2026-11-20, run from the build droplet at v0.8.7:
$NODE init deploy/genesis-chain21.jsonfails because a set-11 rand-node refuses chain 14–21 files by design. The new inputNODE21(chain 21's v0.8.6 rand-node) runs that one probe and defaults toNODE. Chain 21's treasury id is d5fd1883… under both binaries, sotreasury_id_ofis unchanged.perps.state_proof_keyscheck 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 defaultDURIANpath. A re-run withDURIANset is noted below.🤖 Generated with Claude Code
https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8