You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
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:
acvm-backend-barretenberg should be replaced while BlackBox functions are resolved with a library providing those.
The text was updated successfully, but these errors were encountered:
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.
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:
The text was updated successfully, but these errors were encountered: