Skip to content

chore(aeneas): pin sha256 hashes (drop dev-mode for the Level-2 example)#14

Open
avrabe wants to merge 1 commit into
mainfrom
chore/aeneas-pin-hashes
Open

chore(aeneas): pin sha256 hashes (drop dev-mode for the Level-2 example)#14
avrabe wants to merge 1 commit into
mainfrom
chore/aeneas-pin-hashes

Conversation

@avrabe

@avrabe avrabe commented Jun 6, 2026

Copy link
Copy Markdown
Contributor

Hardens the merged Aeneas verification example: hash-verifies the Lean 4.28.0-rc1 toolchain (added to _KNOWN_VERSIONS, require_hashes back to default) and the aeneas binary (per-platform sha256). Hashes computed by streaming the pinned release tarballs through shasum -a 256.

Validation: bazel query //:hello_compiled resolves with hashes required; CI re-downloads + verifies on the heavy job (MODULE edit changed the cache key).

Follow-up: aeneas_lean_lib's internal Lean download + the aeneas source tarball (needs a source-sha256 attr). mathlib is git-tag-pinned; charon already hash-pinned.

🤖 Generated with Claude Code

Makes the aeneas verification example hermetic/reproducible (DD-007):
- Add Lean 4.28.0-rc1 to _KNOWN_VERSIONS (4 platform hashes); the example's
  lean.toolchain is now fully hash-verified (drop require_hashes=False).
- Pin the aeneas binary via per-platform sha256 on aeneas.toolchain.

Hashes computed by streaming the pinned release tarballs through shasum -a 256.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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