Skip to content

fix(blockifier): pin corrected Cairo Native dictionary entry layout - #5

Draft
Mohiiit wants to merge 2 commits into
devfrom
fix/cairo-native-dict-entry-layout
Draft

Mohiiit wants to merge 2 commits into
devfrom
fix/cairo-native-dict-entry-layout

Conversation

@Mohiiit

@Mohiiit Mohiiit commented Nov 4, 2026 •

Copy link
Copy Markdown
Member

Cairo Native computed the wrong array stride for tuples containing dictionary entries, causing native execution to return 33 where Cairo VM returns 22. Pin the madara-alliance Cairo Native fork at 57e745e1a7883ec07cd8e6d721cc02036a112a89, which fixes this layout discrepancy (madara-alliance/cairo_native#1).

This change preserves the Alliance dev integration line, including the deployed hash-cache work and the existing SNOS Patricia optimizations. Blockifier and the native compiler resolve to the same fixed revision, and dependency resolution passes with the locked graph. The focused VM/native regression fails against the old implementation and passes with the fix across all four optimization levels. The full sequencer suite has not been run.

Madara consumers must align their own Cairo Native dependency and sequencer pins; that integration is scoped to madara-alliance/madara#1306. This change does not recover previously committed inconsistent state.

Upstream status: starkware-libs/cairo_native#1671 fixes the same dictionary-entry layout on main and is included in v0.9.0-rc.9; v0.9.0-rc.8 still contains the bug. This narrowly scoped backport retains the deployed rc.6/Cairo 2.17 dependency line and Pedersen cache extensions. The newer upstream line uses Cairo 2.19.6.

@Mohiiit
Mohiiit changed the base branch from perf/blockifier-hash-cache-runtime-config to dev November 4, 2026 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant