PR #7156 bumped ZisK to v1.1.0-alpha, but only for the ziskos path — the L1/L2 prover guest under crates/guest-program/bin/zisk plus the cargo-zisk toolchain in .github/actions/install-zisk.
The stateless-validator guest is still on v1.0.0-alpha. It does not depend on ziskos directly: it reaches ZisK through ere-platform-zisk, pinned by ere revision in crates/guest-program/stateless-validator/bin/zisk/Cargo.toml, with .github/scripts/zkvm-version.sh mirroring the SDK version that ere-catalog resolves at that revision and tag_release.yaml compiling the ELF from ere-compiler-zisk Docker images at ERE_TAG. So the two ZisK versions in the tree now disagree, and released assets are still named stateless-validator-ethrex-zisk-v1.0.0-alpha.
Why it was not done in #7156
eth-act/ere#404 (feat: update zisk to v1.1.0-alpha) merged on 2026-08-18, but the newest ere release is v0.15.0 from 2026-08-06, so no release — and no release-tagged compiler/server image — carries it yet. Moving the shared ERE_REV to that commit would also pull in unrelated OpenVM and SP1 changes that landed in ere since the currently pinned revision, which does not belong in a ZisK bump.
Per-commit GHCR tags for the ere commit do exist (ere-compiler-zisk:4a5a1ab, ere-server-zisk:4a5a1ab, both confirmed present), so this is unblockable early if we decide pinning an unreleased ere commit is acceptable. The repo's current convention is a released ERE_TAG.
What to do when ere cuts a release
- Bump the
ere-platform-* revision in the three crates/guest-program/stateless-validator/bin/*/Cargo.toml manifests and refresh their committed lockfiles.
- Update
ERE_REV and the zkvm_version table in .github/scripts/zkvm-version.sh to the SDK versions ere-catalog resolves at the new revision — the script deliberately fails closed if the manifests move off ERE_REV, so a stale table cannot silently mislabel a published artifact. Re-check the SP1 and OpenVM entries too, not just ZisK.
- Bump
ERE_TAG in tag_release.yaml to the matching release.
- Update the expected asset names in
.github/workflows/pr_lint_gha.yaml and docs/eip-8025.md.
- Expect the guest ELF and VK to change: ZisK v1.1.0-alpha ships a new linker script that moves the whole RAM layout, so any pinned verification key must be regenerated.
Related
PR #7156 bumped ZisK to v1.1.0-alpha, but only for the
ziskospath — the L1/L2 prover guest undercrates/guest-program/bin/ziskplus thecargo-zisktoolchain in.github/actions/install-zisk.The stateless-validator guest is still on v1.0.0-alpha. It does not depend on
ziskosdirectly: it reaches ZisK throughere-platform-zisk, pinned by ere revision incrates/guest-program/stateless-validator/bin/zisk/Cargo.toml, with.github/scripts/zkvm-version.shmirroring the SDK version thatere-catalogresolves at that revision andtag_release.yamlcompiling the ELF fromere-compiler-ziskDocker images atERE_TAG. So the two ZisK versions in the tree now disagree, and released assets are still namedstateless-validator-ethrex-zisk-v1.0.0-alpha.Why it was not done in #7156
eth-act/ere#404 (
feat: update zisk to v1.1.0-alpha) merged on 2026-08-18, but the newest ere release is v0.15.0 from 2026-08-06, so no release — and no release-tagged compiler/server image — carries it yet. Moving the sharedERE_REVto that commit would also pull in unrelated OpenVM and SP1 changes that landed in ere since the currently pinned revision, which does not belong in a ZisK bump.Per-commit GHCR tags for the ere commit do exist (
ere-compiler-zisk:4a5a1ab,ere-server-zisk:4a5a1ab, both confirmed present), so this is unblockable early if we decide pinning an unreleased ere commit is acceptable. The repo's current convention is a releasedERE_TAG.What to do when ere cuts a release
ere-platform-*revision in the threecrates/guest-program/stateless-validator/bin/*/Cargo.tomlmanifests and refresh their committed lockfiles.ERE_REVand thezkvm_versiontable in.github/scripts/zkvm-version.shto the SDK versionsere-catalogresolves at the new revision — the script deliberately fails closed if the manifests move offERE_REV, so a stale table cannot silently mislabel a published artifact. Re-check the SP1 and OpenVM entries too, not just ZisK.ERE_TAGintag_release.yamlto the matching release..github/workflows/pr_lint_gha.yamlanddocs/eip-8025.md.Related
ziskos-side bump