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
The current aztec_backend and aztec_wasm_backend Nargo uses are based on the TurboPlonk version of Aztec Backend, which lacks efficient implementations of useful primitives (e.g. Keccak256 in 18k constraints, ECDSA verification in 36k constraints) that the UltraPlonk version offers.
Proposed solution
Switch to the UltraPlonk version of Aztec Backend.
Alternatives considered
No response
Additional context
At the moment of submitting this issue, this is known to be blocked by certain upgrade works on both Aztec Backend and Barretenberg needed for integration with Noir, including but not limited to:
The content you are editing has changed. Please copy your edits and refresh the page.
Savio-Sou
changed the title
[Nargo] Upgrade to the UltraPlonk Version of Aztec Backend
Epic: Upgrade to the UltraPlonk Version of Aztec Backend
May 12, 2023
Problem
The current
aztec_backend
andaztec_wasm_backend
Nargo uses are based on the TurboPlonk version of Aztec Backend, which lacks efficient implementations of useful primitives (e.g. Keccak256 in 18k constraints, ECDSA verification in 36k constraints) that the UltraPlonk version offers.Proposed solution
Switch to the UltraPlonk version of Aztec Backend.
Alternatives considered
No response
Additional context
At the moment of submitting this issue, this is known to be blocked by certain upgrade works on both Aztec Backend and Barretenberg needed for integration with Noir, including but not limited to:
Tasks
The issue is created more for tracking purposes.
The text was updated successfully, but these errors were encountered: