chore(release): v1.11.34 - #827
Merged
Merged
Conversation
The arming release. Two consensus-visible gates fire from this build, and both require every node to be running it beforehand: * ADDRESS_PROOF_HEIGHT 966_000 (#824, H-7, #605) * MESH_ENVELOPE_V2_HEIGHT 966_400 (#825, H-11, #604) Deliberately ~400 blocks apart rather than sharing a height, so a mesh problem in that window is attributable to one gate rather than two. MESH_ENVELOPE_V2 is the reason that matters: it does not degrade, it PARTITIONS — a node left on an older binary rejects every mesh message from every upgraded peer, and the only way back is upgrading it. ⛔ ALL EIGHT must carry this before 966_400. At 965,085 that is ~8 days. Also carries #826: the deploy now prunes stale `$BINARY.bak.*` to the two most recent instead of accumulating them forever. Measured before the fix, after the v1.11.33 roll: vm1 39 files / 1.4 GB, vm4 38 / 765 MB, vm5 33 / 712 MB. Both lockfiles synced; `tests/integration-sv2`, `crates/stratum-apps` and `prototypes/ghast-bench` carry no workspace version and still resolve under `--locked`. Checked with `grep -F`, since an unescaped `1.11.33` matches digits inside dependency checksums. Claude-Session: https://claude.ai/code/session_01Td1vvfowptTTnu88qG2iym
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
1 participant
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.
The arming release.
Two consensus gates fire from this build
ADDRESS_PROOF_HEIGHTMESH_ENVELOPE_V2_HEIGHTDeliberately ~400 blocks apart rather than sharing a height, so a mesh problem in that window is attributable to one gate rather than two.
⛔ The roll requirement is not routine here
MESH_ENVELOPE_V2does not degrade — it partitions. A node left on an older binary rejects every mesh message from every upgraded peer, and the only way back is upgrading that node. All eight must carry this build before 966_400.Chain is at 965,085, so roughly 6 days to the first gate and 8 to the second. Comfortable, but this is the roll where "we'll catch the last node tomorrow" is not an option.
Also carries
#826 — the deploy prunes stale
$BINARY.bak.*to the two most recent instead of accumulating them forever. Measured before the fix, after the v1.11.33 roll: vm1 39 files / 1.4 GB, vm4 38 / 765 MB, vm5 33 / 712 MB. This release is the first roll that will clean up after itself.Lockfiles
Both synced.
tests/integration-sv2,crates/stratum-appsandprototypes/ghast-benchcarry no workspace version and still resolve under--locked(verified). Stale-reference check usedgrep -F— an unescaped1.11.33matches digits inside dependency checksums and reports phantoms.Roll plan
Canary vm5 → 60m soak → vm6/vm7/vm8 → vm4 → vm3 → vm2 → vm1,
pool_sv2→ghost-pool→translator_sv2per node, stopping on any non-zero exit. Build with--features ghost-pool/zk-production— without it the binary refuses to start on mainnet and the gate rolls it back.https://claude.ai/code/session_01Td1vvfowptTTnu88qG2iym