Skip to content

feat: merge-train/barretenberg#20511

Open
AztecBot wants to merge 4 commits intonextfrom
merge-train/barretenberg
Open

feat: merge-train/barretenberg#20511
AztecBot wants to merge 4 commits intonextfrom
merge-train/barretenberg

Conversation

@AztecBot
Copy link
Collaborator

@AztecBot AztecBot commented Feb 13, 2026

BEGIN_COMMIT_OVERRIDE
chore!: pairing points audit (#20456)
fix: default pp handling (#20516)
chore: Address DSL audit comments (#20074)
END_COMMIT_OVERRIDE

Review of the stdlib (and native) `PairingPoints` class. No bug fixes.
Changes include:
- "Default" pairing points are point at infinity (mimicking native)
instead of arbitrary valid points
- Add `reconstruct_from_public` for use in codec
- More complete testing suite for basic functionality and tagging
mechanism
- Sanity tests for native `PairingPoints` class

VK change is due to change in default pairing point representation from
arbitrary valid to inf
Copy link
Collaborator

@ludamad ludamad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Auto-approved

@AztecBot
Copy link
Collaborator Author

🤖 Auto-merge enabled after 4 hours of inactivity. This PR will be merged automatically once all checks pass.

@AztecBot AztecBot enabled auto-merge February 14, 2026 03:45
iakovenkos and others added 2 commits February 14, 2026 12:45
simplifying external api and making pp aware of its defaultness, so that
set_public() chooses the right path
### 🧾 Audit Context

Address DSL audit comments.

### 🛠️ Changes Made

- Fix typos in docs
- Fix broken links (they now point at a fixed commit)
- Simplify deserialisation function
- Fix wrong parameter in QuadConstraintTests
- Change usage of `std::visit` from `if`/`else` with `constexpr` to
`overloads`. This ensures compiler failure if we forget to handle some
cases (as it was: we were not handling `Call`)

### ✅ Checklist

- [ ] Audited all methods of the relevant module/class
- [ ] Audited the interface of the module/class with other (relevant)
components
- [ ] Documented existing functionality and any changes made (as per
Doxygen requirements)
- [ ] Resolved and/or closed all issues/TODOs pertaining to the audited
files
- [ ] Confirmed and documented any security or other issues found (if
applicable)
- [ ] Verified that tests cover all critical paths (and added tests if
necessary)
- [ ] Updated audit tracking for the files audited (check the start of
each file you audited)

### 📌 Notes for Reviewers

(Optional) Call out anything that reviewers should pay close attention
to — like logic changes, performance implications, or potential
regressions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants