Skip to content

Comments

feat: add indexed multi-pairing support for G2#14

Open
RadNi wants to merge 2 commits intoa16z:mainfrom
LayerZero-Research:amir/indexed-multi-pairing
Open

feat: add indexed multi-pairing support for G2#14
RadNi wants to merge 2 commits intoa16z:mainfrom
LayerZero-Research:amir/indexed-multi-pairing

Conversation

@RadNi
Copy link
Contributor

@RadNi RadNi commented Feb 19, 2026

  • Implemented sequential and parallel multi-pairing functions for G2 points, allowing for indexed access from a cache.
  • Introduced an optimized dispatch function that selects between sequential and parallel execution based on feature flags.

- Implemented sequential and parallel multi-pairing functions for G2 points, allowing for indexed access from a cache.
- Introduced an optimized dispatch function that selects between sequential and parallel execution based on feature flags.

Co-authored-by: Cursor <cursoragent@cursor.com>
@RadNi RadNi force-pushed the amir/indexed-multi-pairing branch from db99549 to 601a1cb Compare February 19, 2026 22:47
- Narrow cfg gate on sequential variant to exclude parallel builds
- Escape square brackets in doc comment to fix rustdoc warning

Co-authored-by: Cursor <cursoragent@cursor.com>
RadNi added a commit to LayerZero-Research/jolt that referenced this pull request Feb 20, 2026
- Replaced the previous tier-2 commitment calculation with an indexed version that utilizes nonzero row indices, improving efficiency in the commitment process.
- Introduced a new vector to store nonzero indices, enhancing the clarity and performance of the bytecode commitment logic.
- This change depends on a16z/dory#14

These changes streamline the handling of bytecode commitments in the zkvm module, contributing to overall performance improvements.
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