-
Notifications
You must be signed in to change notification settings - Fork 578
feat: merge-train/barretenberg #19418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
`round.cpp` and `round.hpp` contained a `round_to_nearest_byte(num_bits)` function that rounds up `num_bits` to the nearest byte. When constructing the vector of inputs in a Blake2s/Blake3 constraint, `num_bits` is set to 8 (see [this](https://github.com/AztecProtocol/aztec-packages/blob/4fc30d81acf2c727e6becd7376de93185e22dd92/barretenberg/cpp/src/barretenberg/dsl/acir_format/acir_to_constraint_buf.cpp#L666-L667)). Hence, `round_to_nearest_byte` is no longer needed and the number of bytes can simply be set to 1. This PR removes `round.cpp` and `round.hpp`. The relevant constraint files that were dependent are also updated accordingly.
### 🧾 Audit Context Documents translator VM. ### 🛠️ Changes Made - Adds README with translator architecture and relations ### ✅ Checklist - [x] 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 No logic changes --------- Co-authored-by: Claude Sonnet 4.5 <[email protected]>
|
No dependency changes detected. Learn more about Socket for GitHub. 👍 No dependency changes detected in pull request |
TomAFrench
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is reverting a noir sync.
@TomAFrench my bad. Is this the right noir version now? |
## Summary - Adds a more helpful error message when `bb verify` fails because the vk file doesn't exist - Previously users got a confusing "Unable to open file: ./target/vk" error - Now the error provides actionable guidance on how to generate or specify the vk file ## Test plan - Added `VerifyWithMissingVkGivesActionableError` test that verifies the error message contains: - `--write_vk` flag guidance - `bb write_vk` command guidance - `--vk_path` option guidance Fixes #17726
### 🧾 Audit Context Audit of the `utils.hpp` and `utils.cpp` files inside `dsl`. ### 🛠️ Changes Made - Updated some comments - Throw if type is not recognised in `add_to_witness_vector_and_track_indices` - Add commit hashes and update audit scopes ### ✅ 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.
Mostly adding lots of documentation (inline, block and README) - no logic changes. Also adds a handful of AUDITTODOs to be resolved in the next PR. Note: VK changes are trivial and due only to the removal of some unused entries from the `BasicTableId` enum.
Improve the info message displayed when no contract artifacts are found when calling `aztec compile`.
Separated convoluted Transcript subclasses from `UltraFlavor` and other Flavors derived from it. Those are only used in a specific type of failure testing where some proof elements are tampered with. The serde logic now lives in the `StructuredProof` class that supports **all** Ultra and Mega derivatives. Simplification of the Flavors' Transcripts made `VerificationKey` subclasses less convoluted, and as a result I was able to re-use base Native and Stdlib VerificationKey classes for all Ultra-Mega Flavors. Closes AztecProtocol/barretenberg#1355
|
🤖 Auto-merge enabled after 4 hours of inactivity. This PR will be merged automatically once all checks pass. |
BEGIN_COMMIT_OVERRIDE
chore: remove round.cpp and round.hpp in dsl/acir_format (#19412)
chore: docs for translator (#19056)
chore: update noir/noir-repo to match next branch
chore: update avm-transpiler Cargo.lock for noir submodule
fix: revert noir/noir-repo to match next and update Cargo.lock
fix: add actionable error when bb verify cannot find vk file (#19398)
chore:
utils.cppaudit (#19425)chore: sha audit 1 (#19072)
fix: improve no artifacts found message to include search path (#19432)
chore: simplify Flavors' Transcripts + VKs deduplication (#19326)
Add correct VKSerializationMode to AVM VerificationKey Classes
END_COMMIT_OVERRIDE