Skip to content
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.

Replace BlackBox functions vendoring from backend to library #492

Closed
Tracked by #2164
kobyhallx opened this issue Aug 9, 2023 · 2 comments
Closed
Tracked by #2164

Replace BlackBox functions vendoring from backend to library #492

kobyhallx opened this issue Aug 9, 2023 · 2 comments
Assignees

Comments

@kobyhallx
Copy link
Contributor

kobyhallx commented Aug 9, 2023

As a Developer
I would like to be able to resolve BlackBox functions from library linked to execution
so that I am no tightly coupled with backend providing those (currently through Barretenberg backend).

AC:

  1. acvm-backend-barretenberg should be replaced while BlackBox functions are resolved with a library providing those.
@TomAFrench TomAFrench transferred this issue from noir-lang/noir Aug 11, 2023
@TomAFrench TomAFrench transferred this issue from noir-lang/acvm Aug 11, 2023
@TomAFrench
Copy link
Member

We could approach this in two ways:

  • Move the barretenberg wasm binary from acvm_js to another crate which gets included in the acvm crate by default
  • Bring the barretenberg wasm binary up to nargo and then pass it in to ACVM similarly to how we do now but as a BlackBoxSolver rather than as a Backend.

The first is preferable but will need testing to ensure that this works across targets nicely. The second is definitely possible but prevents encapsulation of this barretenberg wasm.

@TomAFrench
Copy link
Member

This can be closed as acvm-blackbox-solver exposes these functions.

@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in Noir Sep 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Archived in project
2 participants