Skip to content

feat(jolt-verifier): Refactor Akita verifier packing ownership and public API boundaries#1649

Closed
sumchecker wants to merge 4 commits into
a16z:feat/akita-protocol-integrationfrom
LayerZero-Research:sumchecks/refactor-jolt-verifier
Closed

feat(jolt-verifier): Refactor Akita verifier packing ownership and public API boundaries#1649
sumchecker wants to merge 4 commits into
a16z:feat/akita-protocol-integrationfrom
LayerZero-Research:sumchecks/refactor-jolt-verifier

Conversation

@sumchecker

Copy link
Copy Markdown
Contributor

Summary

  • Move Akita packing adapter ownership out of public jolt-akita and keep jolt-akita native-PCS-shaped.
  • Narrow jolt-verifier Akita prover support behind explicit prover_support APIs while keeping root exports verifier-facing.
  • Fix Stage 8 precommitted proof-count rejection order and add ownership/regression coverage.

Test plan

  • cargo fmt -q
  • cargo nextest run --release -p jolt-openings --cargo-quiet
  • cargo nextest run --release -p jolt-akita --cargo-quiet
  • cargo nextest run --release -p jolt-verifier --cargo-quiet --features akita,core-fixtures
  • cargo nextest run --release -p jolt-verifier --cargo-quiet --features core-fixtures,zk
  • cargo clippy -p jolt-akita -p jolt-verifier --features akita,core-fixtures -q --all-targets -- -D warnings
  • cargo clippy -p jolt-verifier --features core-fixtures,zk -q --all-targets -- -D warnings

sumchecker and others added 4 commits June 25, 2026 11:05
Move Jolt lattice family IDs, layout derivation, and validity formulas into jolt-claims so verifier code only adapts them to physical packing IDs.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions github-actions Bot added the no-spec PR has no spec file label Jun 25, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Warning

This PR has more than 500 changed lines and does not include a spec.

Large features and architectural changes benefit from a spec-driven workflow.
See CONTRIBUTING.md for details on how to create a spec.

If this PR is a bug fix, refactor, or doesn't warrant a spec, feel free to ignore this message.

@sumchecker sumchecker closed this Jun 25, 2026
@sumchecker sumchecker deleted the sumchecks/refactor-jolt-verifier branch June 25, 2026 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-spec PR has no spec file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant