Skip to content

feat(jolt-claims): Move Jolt lattice packing semantics into jolt-claims#1648

Merged
markosg04 merged 3 commits into
a16z:feat/akita-protocol-integrationfrom
LayerZero-Research:sumchecker/jolt-claims-akita-refactor-spec
Jun 25, 2026
Merged

feat(jolt-claims): Move Jolt lattice packing semantics into jolt-claims#1648
markosg04 merged 3 commits into
a16z:feat/akita-protocol-integrationfrom
LayerZero-Research:sumchecker/jolt-claims-akita-refactor-spec

Conversation

@sumchecker

Copy link
Copy Markdown
Contributor

Summary

  • Moves Jolt-specific lattice packing semantics into jolt-claims, including family IDs, view formulas, validity requirements, openings, relations, and layout derivation helpers.
  • Keeps jolt-openings focused on generic packing mechanics by making PackingFamilyId a generic physical identifier.
  • Updates Akita verifier/prover support to consume the jolt-claims lattice API while preserving committed bytecode/program-image and trusted-advice precommitted opening boundaries.

Spec Alignment

  • jolt-openings owns generic packing layout, view transport, rank/digest mechanics.
  • jolt-claims owns Jolt lattice semantic families and validity/view formulas.
  • jolt-verifier remains the adapter/orchestrator for config, errors, and Stage 8 dispatch.
  • Bytecode subfamilies use one Jolt namespace with stable tags and checked composite indices to stay close to the prior/spec shape while avoiding aliasing.

Validation

  • cargo clippy -p jolt-openings -p jolt-claims -p jolt-verifier --features akita,field-inline -q --all-targets -- -D warnings
  • cargo nextest run --release -p jolt-openings -p jolt-claims -p jolt-verifier --cargo-quiet --features akita,field-inline

sumchecker and others added 2 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>
@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.

@github-actions github-actions Bot added the no-spec PR has no spec file label Jun 25, 2026
Co-authored-by: Cursor <cursoragent@cursor.com>
@markosg04 markosg04 merged commit 11c9a03 into a16z:feat/akita-protocol-integration Jun 25, 2026
19 of 20 checks passed
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.

2 participants