-
Notifications
You must be signed in to change notification settings - Fork 115
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
feat: Add Noir DSL with acir_format and turbo_proofs namespaces #198
Conversation
I chatted with @vezenovm about which APIs to keep for use in "barretenberg_wrapper" and "barretenberg_wasm" so this is ready for review! Need to get @kevaundray to review all my refactoring (in case I did something that won't work for Noir) and then crypto-dev folks to review how to make this C++ code better. |
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 looks like what we were doing previously with parts of it cleaned up (gracias :) )
I'm squashing this all for a rebase on master, so if anyone needs the individual commits, you should look now |
f7f0cd1
to
9c67dfe
Compare
…cProtocol/barretenberg#198) * feat: Add Noir DSL with acir_format and turbo_proofs namespaces * chore: Upstream changes to fix proving key serialization in turbo_proofs (AztecProtocol/barretenberg#204) --------- Co-authored-by: kevaundray <[email protected]> Co-authored-by: Maxim Vezenov <[email protected]>
…cProtocol/barretenberg#198) * feat: Add Noir DSL with acir_format and turbo_proofs namespaces * chore: Upstream changes to fix proving key serialization in turbo_proofs (AztecProtocol/barretenberg#204) --------- Co-authored-by: kevaundray <[email protected]> Co-authored-by: Maxim Vezenov <[email protected]>
Description
This upstreams the Noir DSL as developed in https://github.com/noir-lang/aztec-connect and attempts to align with the upstream changes (such as passing a nullptr as pippenger_lagrange). I also tried to apply various refactoring and cleanup where possible but my C++ is terrible—so please let me know where things should be better.
This is currently a draft because I think we are going to cleanup some of the turbo_proofs APIs but I need to catch @vezenovm when he is back from EthDenver.Checklist:
/markdown/specs
have been updated.@brief
describing the intended functionality.