release: upgrade cairo, native, proving-utils

[dorimedini-starkware]

No description provided.

[reviewable-StarkWare]

This change is 

[dorimedini-starkware]

• TMP: patch cairo crates #14073
• blockifier: sha512 syscall #14072
• release: upgrade cairo, native, proving-utils #14200 👈 (View in Graphite)
• main

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

[github-actions]

Artifacts upload workflows:

• Started at 2026-05-26T10:20:58Z

[cursor]

PR Summary

Medium Risk
Wide toolchain bump changes compiled contract gas, bouncer migration costs, and OS hint coverage; native sha512_process_block is still todo!(), which is a footgun for Cairo Native execution.

Overview
This PR bumps the Cairo / native / proving toolchain and refreshes dependent snapshots across the sequencer.

Dependency pins in Cargo.toml move cairo-lang crates from 2.17.0-rc.4 → 2.19.0-rc.0, cairo-native to 0.9.0-rc.7, and proving-utils (privacy-prove, privacy-circuit-verify-v1) to git rev 1e0f8fc. Matching version files are updated (cairo_compiler_version.txt, native_compiler_version.txt). Cargo.lock reflects a large transitive refresh (e.g. indexmap, crypto/hash crates, stwo-circuits git rev c99a181).

Blockifier / execution: syscall and transaction tests are re-baselined for lower gas_consumed, fewer range-check builtins, and updated redeposit amounts. CASM hash migration regression gas in bouncer_test drops (110M→104M Sierra, 240M→225M proving). Native SyscallHandler gains a sha512_process_block stub that **todo!()**s. Stack-trace golden files shift PCs after recompilation.

OS / flow tests: many hint_coverage JSON fixtures add EnterScopeNewNode. Fuzz contract addresses and experimental-libfunc builtin counts (poseidon/blake) are updated.

Risk note: Native Cairo1 paths that hit SHA-512 syscalls will panic until the stub is implemented; gas/bouncer numbers changing with the compiler can affect fee limits and block capacity if production constants are tied to these tests.

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

[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.}

^{Reviewed by Cursor Bugbot for commit fbc7569. Configure here.}

[Yoni-Starkware]

@Yoni-Starkware reviewed 22 files and all commit messages, and made 1 comment.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on dorimedini-starkware).

---

Cargo.toml line 338 at r1 (raw file):

primitive-types = "0.12.1"
privacy-circuit-verify-v0 = { package = "privacy-circuit-verify", git = "https://github.com/starkware-libs/proving-utils", rev = "580135e" }
privacy-circuit-verify-v1 = { package = "privacy-circuit-verify", git = "https://github.com/starkware-libs/proving-utils", rev = "039e52c" }

v1 (latest) should be aligned with privacy-prove

Suggestion:

privacy-circuit-verify-v1 = { package = "privacy-circuit-verify", git = "https://github.com/starkware-libs/proving-utils", rev = "1e0f8fc" }

[dorimedini-starkware]

@dorimedini-starkware made 1 comment.
Reviewable status: 20 of 53 files reviewed, 2 unresolved discussions (waiting on Yoni-Starkware).

---

Cargo.toml line 338 at r1 (raw file):

Previously, Yoni-Starkware (Yoni) wrote…

v1 (latest) should be aligned with privacy-prove

Done.

[Yoni-Starkware]

@Yoni-Starkware reviewed 33 files and all commit messages, made 1 comment, and resolved 1 discussion.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on dorimedini-starkware).

[dorimedini-starkware]

@dorimedini-starkware resolved 1 discussion.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on dorimedini-starkware).