STARK proof generation failure in Cairo VM execution

Cairo VM Constraint Violation Outcome

The Cairo VM compiles programs into arithmetic constraints; unsatisfied constraints prevent STARK proof generation, halting state transitions.

Recovery Uncertainty

State recovery depends on the underlying ledger's block‑height revert, as the VM lacks native checkpointing for granular rollback. This creates ambiguity when a memory heap limit is exceeded versus a hard constraint violation.

• What criteria does the VM use to classify a memory heap overflow as recoverable versus a terminal constraint failure?
• Is there a way to pinpoint the offending opcode in the trace without re‑executing the entire program?