Repository navigation
fullnode e79070a7 (constraint set 11) for chain 22 / v0.8.7, and cut-chain22.sh - #15
Merged
Merged
Conversation
…s take the 0.8.6 path crates The coverage job checked out fullnode main unpinned; it now checks out FULLNODE_REF, fullnode main e79070a7 (PR #194 set-11 re-vendor, circuits 41d64acd; #197 the chain-22 fleet cutover). Set v0.8.7 at the tag. bridge-codec and randprotocol-core/src/bridge are byte-identical between v0.8.6 and e79070a7, so the lockfiles move only the path entries (0.8.0/0.8.2 -> 0.8.6). vectors/attestations.json regenerates byte for byte and matches fullnode's copy at e79070a7. README: the vectors tool has two binaries, so its commands name --bin vectors. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo
…set 11), with a selftest Derived from cut-chain21.sh. Differences: genesis_hash moves with chain_id (BR-1005), from GENESIS_HASH, which has no default because it exists only at the cut, and is checked against RAND_RPC and each guardian host's own node. A host config without a genesis line (a pre-BR-1005 daemon) is left without one, with a NOTE. Chain 21's genesis is never accepted. The relayer's rand swap to v0.8.7 takes RAND_OLD_SHA (read with the new read-only status step) and RAND_NEW_SHA (v0.8.7's signed SHA256SUMS) from the environment and keeps rand.pre-c22. selftest: 35 checks, ssh/scp/curl shimmed, contacts nothing. config.example.toml: chain_id 22, genesis_hash a marked TODO for the cut. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo
…e recipients Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…nce 2026-11-21) Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8
dendisuhubdy
marked this pull request as ready for review
November 21, 2026 04:36
Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8
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.
This moves the bridge onto fullnode main
e79070a7: zkVM constraint set 11, for the chain-22 cut and v0.8.7. It includes fullnode #194 (the set-11 re-vendor, circuits41d64acd) and #197 (deploy/cutover-fleet-chain22.sh). Do not merge before the cut gates. The live bridge serves chain 21 until the cut. Nothing here was deployed, and no live server was contacted.Set 11 and the bridge
The bridge computes nothing that set 11 changes:
crates/bridge-codecandrandprotocol-core/src/bridgeare byte-identical from v0.8.6 to e79070a7.rand bridge-mint, the wallet the relayer calls.So:
cut-chain22-genesis.shcarries chain 21'sbridgesection and asserts it: emitter, emitters, guardian sets, PQ set, pause key, fees and rotation.What moved
coverage.yml): fullnode was checked out at an unpinnedmain. It is now checked out atFULLNODE_REF=e79070a714988105c571ddae3dfeed96b4b39e93. Setv0.8.7at the tag.bridge-codec/randprotocol-coremove, 0.8.0/0.8.2 → 0.8.6.vectors/attestations.jsonregenerates byte for byte and matches fullnode's copy at e79070a7.pq-cosignatures.jsonalso regenerates byte for byte. The chain-21 governance vectors stay: they pin a layout at a real genesis.daemons/mainnet/cut-chain22.sh(new, derived fromcut-chain21.sh): the steps are status / stop / relayer-rand / droplet 1..6 / relayer / laptop / start / rollback-rand / selftest.chain_id21 → 22 andgenesis_hash(BR-1005).GENESIS_HASHcomes from chain22.record. It is checked againstRAND_RPCand each guardian host's own node, and chain 21's hash is refused.BURN_SEQis checked against the chain, as before.RAND_OLD_SHAis read withstatus.RAND_NEW_SHAcomes from v0.8.7's signed SHA256SUMS.genesis_hashline is left without one, and the script prints a NOTE. Such a config belongs to a pre-BR-1005 daemon: bridge tags up to v0.8.6 lack the field and refuse an unknown one.config.example.toml:chain_id = 22. The genesis hash is a marked TODO.mainnet/*.tomlstay on chain 21 because they mirror the live hosts. This follows every earlier cut, where the repo copies were updated after the cut.--bin vectors, and AGENTS.md has a chain-22 prep entry.Tests (build droplet, Rust 1.98.1, against fullnode e79070a7)
daemons: cargo test --release --lockedanvil_e2e(anvil/forge/cast installed, so it ran, not skipped)daemons: cargo clippy --release --all-targets -D warningssolana: cargo test --release --lockedtools/vectors: --bin vectors -- --check,--bin pq-vectors -- --checkevm: forge test(Mac; OZ v5.0.2)cut-chain22.sh selftest(Mac; shellcheck -S warning clean)cut-chain21.sh selftestNot run: Tron (
deploy/trx.sh nile --dry-run). Its sources mirrorevm/, and nothing in them changed.At the cut (the bridge's part of
cutover-fleet-chain22.sh)cut-chain22.sh status(to recordRAND_OLD_SHA), thenstop. Settle every in-flight lock on chain 21 first.switch, runrelayer-rand <v0.8.7 Linux rand>. A set-9randcannot mint on chain 22. The relayer wallet's first scan on chain 22 empties and rescans its note store.droplet 1..6,relayerandlaptopwithGENESIS_HASH,BURN_SEQandRAND_NEW_SHA. Then run the fleet'sBRIDGE_ON_CHAIN22=yes … bridge-start, or this script'sstart(guardians first, the relayer last).mainnet/*.tomlwith chain 22 and its genesis;rand-bridge-audit;Decide before the cut: rand1 addresses change under set 11.
pk = H_PK(nk)is a Poseidon2 output, so the same wallet seed has a new address and a new recipient hash on chain 22.recipientstable, a lock that names a pre-cut recipient hash, or a randbridge.org deposit address cached from a set-9 wallet. Each of these would mint to a set-9pk, and no set-11 wallet can spend that note.🤖 Generated with Claude Code
https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo