Skip to content

v0.8.7: version, changelog and release notes (chain 22, constraint set 11) - #198

Merged
dendisuhubdy merged 2 commits into
mainfrom
release/v0.8.7
Nov 20, 2026
Merged

dendisuhubdy merged 2 commits into
mainfrom
release/v0.8.7

Conversation

@dendisuhubdy

Copy link
Copy Markdown
Member

The v0.8.7 bump: the chain-22 release on zkVM constraint set 11. Nothing is tagged, signed or published. The owner tags and signs on a real TTY (sequence below). Do not merge until the owner is ready to tag; merge with a squash, then tag the merge commit.

Changes

file change
Cargo.toml workspace version 0.8.6 → 0.8.7
Cargo.lock the seven workspace crates → 0.8.7. Done with cargo update -w on the build droplet, because --offline failed on the rand-zkvm-cuda git dependency. The diff is exactly those 7 lines.
crates/randprotocol-node/src/rpc.rs the rand_getVersion test expects 0.8.7
CHANGELOG.md Unreleased becomes v0.8.7 — PLACEHOLDER-TAG-DATE; new rows for #197 (cutover-fleet-chain22.sh) and the version; the asset list
docs/releases/v0.8.7.md (new) the set-11 gas change as a governance record (bundle 20 479 → 22 527, auth 1 279 → 1 407, msauth 436 159 → 355 775, with the per-row weights); the chain-22 cut; the operator upgrade steps (fleet, a standalone node, downstream); the rollback
README.md v0.8.7 row in the release table
AGENTS.md the set-11 entry no longer says "PR open, NOT merged"

Same shape as v0.8.6's bump (6eeed699), plus the release notes. v0.8.6 had no notes file; a chain cut needs one, as chain 21 had docs/chain21-cut-runbook.md.

Placeholders, filled at the tag or the cut: PLACEHOLDER-TAG-DATE, -TAG-COMMIT, -CI-RUN, -SHA256SUMS, -CHAIN22-GENESIS-HASH, the CHAIN_CONSTRAINT_SETS row (22, "PLACEHOLDER-CHAIN22-GENESIS-HASH", 11),, -LAUNCH-UTC and -OWNER-SIGNOFF (for the gas governance record). grep -rn PLACEHOLDER- CHANGELOG.md docs/releases finds them all.

One doc conflict for the owner. docs/deploy.md says "A release for chain 22 is tagged only from a tree on which check-limits passes". That cannot hold for v0.8.7: stage and beacon-init need the release before the cut, and the genesis hash, and so the row, exist only after it. v0.8.0 and chain 21 worked the same way (genesis-chain21.json landed after the tag, in 58c7afd2). The notes read the sentence as applying to the first release after the cut.

Test

On the build droplet (the Mac built nothing): cargo test --release --locked -p randprotocol-node --lib version_reports_build_and_chain passed (1 test). The two v0.9.0-gated defaults (RPC-201, PRIV-601) key on 0.8. and are unaffected.

Tag-and-sign sequence (the owner)

0. Preconditions:

  • this PR is squash-merged;
  • ci is green on the merge commit M;
  • chain 21 is still on v0.8.6.

1. Tag fullnode (annotated, naming the green run; release.yml refuses otherwise):

cd ~/Github/randprotocol/fullnode && git fetch origin
M=$(git rev-parse origin/main); git log --oneline -1 $M      # "v0.8.7: version, changelog and release notes …"
gh run list -R randprotocol/fullnode -w ci.yml --commit $M --json databaseId,conclusion,event   # a push run: success
RUN=<that run id>
git tag -a v0.8.7 $M -m "v0.8.7 — chain 22 onward: constraint set 11 (Grain Poseidon2, declared poseidon2 height, rate-1/4 quotient layout, versioned rVM keys, cell-count gas), EVM block context, the beacon, pinned perps state-proof keys; refuses chains 14-21
ci: run $RUN (success) at $M"
git push origin v0.8.7
gh run watch -R randprotocol/fullnode $(gh run list -R randprotocol/fullnode -w release.yml -L1 --json databaseId -q '.[0].databaseId')

release.yml then does the following:

  • it checks that the msauth blob and the four perps keys match the pins compiled into rand-node;
  • it attests all eight files;
  • it publishes rand-node, rand, rand-prover, msauth-vk-production.bin, perp-vk-production-t18-pg14-in16-pub{7,8,9,10}-p2h20.bin and SHA256SUMS.

2. Check SHA256SUMS before signing. It must have eight lines. The seven chain-22 fleet files must be listed at these values:

REL=~/.rand-chain22/release-v0.8.7; mkdir -p "$REL"
gh release download v0.8.7 -R randprotocol/fullnode -D "$REL"
cat "$REL/SHA256SUMS"; wc -l < "$REL/SHA256SUMS"          # 8
#   rand-node                                          <new>
#   rand                                               <new>
#   rand-prover                                        <new>   (not staged by the cutover)
#   msauth-vk-production.bin                           168d79a880b13b6d3e5b1f2a0f50561590712179c63189b52038cb2172a971b3
#   perp-vk-production-t18-pg14-in16-pub7-p2h20.bin    4dc1f18bdd6d9104ba1622710cf2c146f71759676dbdcb70dad036152242e8b4
#   perp-vk-production-t18-pg14-in16-pub8-p2h20.bin    6392e5e9b7348f3729ba2031e0e3ec9788d6ed62a14521526482c92615f55106
#   perp-vk-production-t18-pg14-in16-pub9-p2h20.bin    c31636aa281004163e6fe0debd81854f11d7bca6c8062a91b1501c7e593e5bf0
#   perp-vk-production-t18-pg14-in16-pub10-p2h20.bin   ae3d0dc276061fd2a87b2e91b239f6dcccb746b49dedeecfdb2aab977c95c370
for f in rand-node rand rand-prover msauth-vk-production.bin perp-vk-production-t18-pg14-in16-pub{7,8,9,10}-p2h20.bin; do
  gh attestation verify "$REL/$f" -R randprotocol/fullnode >/dev/null && echo "attested $f" || echo "NOT ATTESTED $f"; done

3. Sign. Run this in a separate, real Terminal; the key is passphrase-protected. Use a checkout at the tag:

cd ~/Github/randprotocol/fullnode && git checkout v0.8.7     # or a worktree at the tag
deploy/sign-release.sh "$REL/SHA256SUMS" ~/.rand-release/release_ed25519   # ssh-keygen -Y sign -n rand-release; writes SHA256SUMS.sig, then verifies 1 of the required 1
gh release upload v0.8.7 "$REL/SHA256SUMS.sig" -R randprotocol/fullnode

A second holder, when there is one, uses deploy/sign-release.sh --append and uploads SHA256SUMS.sig2.

4. Verify the published set. Run the library under bash; sourced into zsh it resolves paths wrongly:

gh release view v0.8.7 -R randprotocol/fullnode --json assets -q '.assets[] | "\(.name) \(.updatedAt)"'   # SHA256SUMS.sig present
bash -c ". deploy/lib/verify-release.sh
  verify_release_sums $REL/SHA256SUMS $REL/SHA256SUMS.sig &&
  for f in rand-node rand rand-prover msauth-vk-production.bin perp-vk-production-t18-pg14-in16-pub{7,8,9,10}-p2h20.bin; do verify_binary $REL/\$f $REL/SHA256SUMS \$f || exit 1; done && echo ALL VERIFIED"

The cutover's preflight re-checks all seven fleet files against the signed sums (RELEASE_SUMS=$REL/SHA256SUMS).

5. Snapshot tags on the other repositories. These follow v0.8.6's convention: an annotated v0.8.7 tag naming the monorepo commit. Per CLI-751, outside fullnode such a tag marks the snapshot, not a release of that repository. Tag only after the monorepo pin commit for v0.8.7 lands, each at the commit that commit pins:

  • clients;
  • circuits, on the org remote randprotocol/zkp-circuits, at the pin 41d64acd. The v0.8.6 circuits tag was 20 commits past the node's pin (CLI-751);
  • bridge, durian.market, randscan, zusd.money and randbridge.org;
  • the monorepo.
git -C <repo> tag -a v0.8.7 <pinned commit> -m "Rand Protocol v0.8.7 — chain 22, constraint set 11 (monorepo <short sha>)" && git -C <repo> push <remote> v0.8.7

6. After the roll. Move the monorepo's configuration/release/ pin to the signed v0.8.7 pair: SHA256SUMS, .sig and the set-11 msauth blob. The fullnode's deploy/lib/verify-release.sh has changed since v0.8.6, so the monorepo's pinned copy and deploy-scripts/lib/verify-release.upstream also need refreshing. Without that, respawn-host.sh refuses.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo

@codecov

codecov Bot commented Nov 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

…t 11)

- Workspace version 0.8.7: Cargo.toml, the seven workspace crates in
  Cargo.lock (cargo update -w on the build droplet; offline failed on the
  rand-zkvm-cuda git dependency), the rand_getVersion test.
- CHANGELOG: Unreleased becomes v0.8.7 (tag date a PLACEHOLDER), with a row
  for #197's cutover-fleet-chain22.sh and the asset list.
- docs/releases/v0.8.7.md: the set-11 gas change as a governance record
  (bundle 20 479 -> 22 527, auth 1 279 -> 1 407, msauth 436 159 -> 355 775;
  the per-row weights), the chain-22 cut, the operator upgrade steps and the
  rollback. The chain-22 genesis hash and the CHAIN_CONSTRAINT_SETS row are
  PLACEHOLDER-... until the cut.
- README release table: v0.8.7. AGENTS.md: #194 is merged.

Not tagged, not signed, not published.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo
@dendisuhubdy
dendisuhubdy merged commit bf5aabd into main Nov 20, 2026
23 checks passed
@dendisuhubdy
dendisuhubdy deleted the release/v0.8.7 branch November 20, 2026 01:55
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