chore: update leanSpec commit

[MegaRedHand]

This PR updates the leanSpec commit to 44f896af5f43f71cdafaa993b61b4f4aa99681c0

[github-actions]

🤖 Kimi Code Review

Review of PR #171

File: Makefile

Issue 1: Missing integrity verification for git clone

• Line 28: The leanSpec target clones a repository without verifying the commit hash. This is a security vulnerability for consensus-critical code.
• Suggested fix:

leanSpec:
	git clone https://github.com/leanEthereum/leanSpec.git --single-branch
	cd leanSpec && \
	git checkout $(LEAN_SPEC_COMMIT_HASH) && \
	git verify-commit $(LEAN_SPEC_COMMIT_HASH) || \
	(echo "Commit verification failed! Aborting." && rm -rf leanSpec && exit 1)

Issue 2: No check for existing directory

• Line 28: The target will fail if leanSpec/ already exists, breaking incremental builds.
• Suggested fix:

leanSpec:
	@if [ ! -d "leanSpec" ]; then \
		git clone https://github.com/leanEthereum/leanSpec.git --single-branch; \
	fi
	cd leanSpec && git fetch && git checkout $(LEAN_SPEC_COMMIT_HASH)

Issue 3: Missing dependency declaration

• Line 28: The leanSpec target should be declared as .PHONY since it's not a file target.
• Add after line 30:

.PHONY: leanSpec

These changes improve security and build reliability for consensus-critical code.

---

Automated review by Kimi (Moonshot AI) · custom prompt

[github-actions]

🤖 Codex Code Review

No blocking findings in this diff.

Only change is a pinned dependency commit hash in Makefile:

• LEAN_SPEC_COMMIT_HASH updated from 8b7636... to 44f896....

Assessment:

• Code correctness/security/performance: no direct Rust or consensus-path code changed, so no immediate behavioral risk in fork choice, attestation handling, finalization, state transition, XMSS, or SSZ logic from this PR alone.
• Maintainability: still pinned to an exact commit, which is good for reproducibility.

Residual risk/testing gap:

• The actual risk is in the content of the new leanSpec commit itself, which is not visible in this diff. I’d recommend verifying upstream changes between those two commits and running full consensus/regression tests after updating.

---

Automated review by OpenAI Codex · custom prompt

[github-actions]

🤖 Claude Code Review

This is a minimal chore PR — a single-line change bumping the LEAN_SPEC_COMMIT_HASH from 8b7636bb to 44f896af.

---

Review: chore: update leanSpec commit

Scope: 1 line changed in Makefile — LEAN_SPEC_COMMIT_HASH bump.

What this does

Updates the pinned leanSpec test fixtures commit used by make leanSpec/fixtures. The fixture generator (uv run fill) will regenerate spec tests from the new commit when a developer next runs make test or rm -rf leanSpec && make leanSpec/fixtures.

Correctness

• The hash format is valid (40-char hex SHA-1).
• The checkout mechanism (cd leanSpec && git checkout $(LEAN_SPEC_COMMIT_HASH)) will hard-pin to this exact commit, so there's no floating-ref risk.
• No other files reference LEAN_SPEC_COMMIT_HASH, so the change is self-contained.

Concerns / Suggestions

• No fixture regeneration evidence. Ideally the PR would note that fixtures were regenerated and make test passes with the new spec commit. If CI runs make test (which calls make leanSpec/fixtures), this is automatically validated — worth confirming CI is green before merging.
• Missing changelog note. For traceability it can be useful to mention in the PR body (or a commit trailer) what changed between the two leanSpec commits (new test vectors, spec rule changes, etc.). Not a blocker, just a quality-of-life suggestion for reviewers in the future.

Overall

The change is mechanically correct and low-risk. Approve once CI is confirmed green.

---

Automated review by Claude (Anthropic) · custom prompt

[greptile-apps]

Greptile Summary

Updates the leanSpec dependency to commit 44f896a. This is a straightforward dependency version update that changes the commit hash used when cloning the leanSpec repository during the build process.

• Single line change updating LEAN_SPEC_COMMIT_HASH variable
• No logical or syntactic issues detected
• Assumes the new commit has been tested for compatibility

Confidence Score: 5/5

• This PR is safe to merge with minimal risk - it's a simple dependency version update
• The change only updates a commit hash reference for a dependency. There are no code logic changes, no security implications, and the syntax is correct. The only potential risk would be if the new leanSpec commit introduces breaking changes, but this would be caught in CI/testing.
• No files require special attention

Important Files Changed

Filename	Overview
Makefile	Updates LEAN_SPEC_COMMIT_HASH from 8b7636b to 44f896a - simple dependency version update

_{Last reviewed commit: f6d5eef}