Contract gate info reporting tool #6190
Labels
A-ux/devex
Area: relates to external ux / devex. (Users typically are devs) (See also A-internal-devex)
T-feature-request
Type: Adding a brand new feature (not to be confused with improving an existing feature).
As per (noir-lang/noir#4962) we will be removing
nargo info
asnargo
moves away from all backend specific operations. We will now expect bb to take in an ACIRProgram
(collection of multiple ACIR circuits) and spit out a JSON gates report (#6168). However, bb does not know about contracts and arguably should not know about them (it should not matter to bb how an ACIR program was generated).We need some tool as part of aztec's developer suite that allows developers to fetch gate information on their contract using the new
bb info
command. A new tool will be best imo as gate counts are only really relevant for private functions as public functions work in an entirely different execution paradigm. Perhaps some sort of general tool that generates "gas" reports that distinguishes between public/private functions will be most beneficial for devs.The text was updated successfully, but these errors were encountered: