blockifier: add sierra-emu execution behind feature flag

[avi-starkware]

Adds sierra-emu as an alternative execution backend, gated behind the
`sierra-emu` feature flag. Also adds `with-trace-dump` and
`with-libfunc-profiling` feature flags for execution tracing and
profiling support.

When no new flags are enabled, behavior is identical to upstream.

---

Note

Medium Risk
Execution-path changes and new unsafe/IO-based instrumentation are introduced, but they are gated behind feature flags so default behavior should remain unchanged. Risk is mainly in correctness/compatibility when enabling sierra-emu, with-trace-dump, or with-libfunc-profiling.

Overview
Adds an alternative contract execution backend in blockifier behind the sierra-emu feature flag by extending ContractExecutor to run via sierra-emu::VirtualMachine and wiring a syscall-handler adapter plus type conversions.

Introduces optional instrumentation features: with-trace-dump (writes execution traces to traces/native or traces/emu) and with-libfunc-profiling (collects libfunc profiles into a global LIBFUNC_PROFILES_MAP keyed by tx hash), enabled by using an AotWithProgram executor variant.

Updates workspace/crate manifests and lockfile to add the sierra-emu dependency and related transitive crypto deps, and adds NativeCompiledClassV1::new_from_executor to support constructing compiled classes from the new executor variants.

^{Reviewed by Cursor Bugbot for commit f83e2b7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[avi-starkware]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• blockifier: add sierra-emu execution behind feature flag #13543 👈 (View in Graphite)
• blockifier: introduce ContractExecutor abstaction #13542
• blockifier: add with-libfunc-profiling feature flag #13755
• blockifier: add benchmarking and only-native feature flags #13541
• main-v0.14.2

This stack of pull requests is managed by Graphite. Learn more about stacking.

[reviewable-StarkWare]

This change is 

[github-actions]

Artifacts upload workflows:

• Started at 2026-03-26T17:21:57Z
• Started at 2026-03-26T17:23:56Z
• Started at 2026-03-26T17:21:57Z
• Started at 2026-03-26T17:37:51Z
• Started at 2026-03-26T17:46:04Z
• Started at 2026-03-26T19:16:17Z
• Started at 2026-03-26T19:16:36Z
• Started at 2026-04-06T16:31:58Z
• Started at 2026-04-06T20:33:09Z
• Started at 2026-04-07T21:05:36Z
• Started at 2026-04-07T21:05:58Z
• Started at 2026-04-08T05:05:16Z
• Started at 2026-04-14T11:00:01Z
• Started at 2026-04-14T11:06:04Z
• Started at 2026-04-14T11:33:57Z
• Started at 2026-04-14T12:36:59Z
• Started at 2026-04-14T12:37:33Z
• Started at 2026-04-14T12:42:45Z
• Started at 2026-04-19T09:29:15Z

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[cursor]

Hardcoded is_infinity: false loses point-at-infinity state

Medium Severity

The convert_from_secp_256_k1_point and convert_from_secp_256_r1_point functions hardcode is_infinity: false when converting from sierra-emu to cairo-native point types. Since sierra-emu's point types only have x and y fields (no infinity flag), the point at infinity is represented as (0, 0). When this is converted back to a cairo_native point with is_infinity: false, the downstream ark-ec operations will treat it as the literal finite point (0, 0) — which is not on the secp256k1/r1 curves — rather than the identity element. This causes incorrect results for elliptic curve add and mul operations involving the point at infinity.

Additional Locations (1)

• crates/blockifier/src/execution/native/executor.rs#L631-L640

 

[Yoni-Starkware]

Are you sure this must be in our repo?

@Yoni-Starkware made 1 comment.
Reviewable status: 0 of 5 files reviewed, 1 unresolved discussion (waiting on avi-starkware, noaov1, and TomerStarkware).

[Yoni-Starkware]

@Yoni-Starkware made 1 comment.
Reviewable status: 0 of 5 files reviewed, 2 unresolved discussions (waiting on avi-starkware, noaov1, and TomerStarkware).

---

crates/blockifier/src/execution/native/executor.rs line 1 at r3 (raw file):

#[cfg(feature = "with-trace-dump")]

I think that this logic could be implemented on Native repo. Please try this approach.

[cursor]

PR Summary

Medium Risk
Adds new execution backends and syscall bridging code in blockifier (plus optional trace-dump instrumentation), which could change contract execution behavior or introduce runtime panics when the new feature flags are enabled; default behavior remains unchanged when flags are off.

Overview
Introduces an alternative contract execution path in blockifier behind the new sierra-emu feature flag, extending ContractExecutor to run via sierra-emu and wiring a syscall-handler adapter plus type conversions to reuse the existing native syscall implementation.

Adds optional trace dumping via with-trace-dump (for both AOT and emulated execution) that writes per-run JSON traces (and Sierra sources for emu) under traces/, and updates workspace/crate dependencies and features to include sierra-emu (plus its transitive lockfile changes).

^{Reviewed by Cursor Bugbot for commit db24055. Bugbot is set up for automated code reviews on this repo. Configure here.}