midnight-verify:verify-by-zkir-inspection

Inspect compiled circuits by compiling a Compact contract to generate .zkir JSON output, then parse opcodes, instruction counts, and data-flow traces to verify alignment with claimed structural properties. The inspection produces a structured report.

ZKIR inspection analyzes the .zkir JSON compiled from a Compact contract to verify the compiled circuit structure. You need it when validating compiler behavior, auditing instruction streams, or confirming reported circuit properties match actual output.

Compare full and skip-zk compilation paths by running both builds on the same Compact contract, extracting the .zkir JSON from each, and inspecting instruction streams to validate that reported properties align consistently across both outputs.

Yes, the ZKIR inspection records the compiler version and zkir schema during analysis. It coordinates between full and skip-zk compilation paths and extracts opcodes, instruction counts, and data-flow traces into a structured verification report.

Verification is limited to the structural properties visible in the .zkir JSON output, such as opcodes, instruction counts, and data-flow traces. It does not validate cryptographic execution semantics or runtime behavior beyond what the compiled representation contains.