starknet_os: os resources test - add send_message_to_l1

[dorimedini-starkware]

No description provided.

[dorimedini-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

• starknet_os: os resources test - add send_message_to_l1 #14143 : 2 dependent PRs (#14144 , #14153 ) 👈 (View in Graphite)
• starknet_os: os resources test - add replace_class #14142
• starknet_os: os resources test - support virtual builtins, add sha256 #14141
• starknet_os: define sha256 batch resources constants #14140
• starknet_os: os resources test - add keccak #14139
• starknet_os: os resources test - add 3 more syscalls #14138
• starknet_os: os resources test - remove all fee transfer syscalls #14137
• starknet_os: os resources test - add emit event #14136
• starknet_os: os resources test - add meta tx #14135
• starknet_os: os resources test - measure linear factor, add deploy #14134
• starknet_os: os resources test - library call #14129
• starknet_os: initial test, measure call contract resources #14128
• blockifier_test_utils: add option to deploy from zero in test accounts #14258
• starknet_os_flow_tests: helper function to declare explicit classes #14257
• starknet_os: os resources test - create fixed deployable account #14173
• main

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

[reviewable-StarkWare]

This change is 

[cursor]

PR Summary

Medium Risk
Changes protocol fee/gas constants and OS program hashes for 0.14.4, which affects transaction charging and client-side proving allowlists; scope is limited to syscall accounting and test harness.

Overview
Adds send_message_to_l1_syscall to the OS resources measurement contract and folds SendMessageToL1 into the syscall regression suite by dropping it from UNMEASURABLE_SYSCALLS and asserting the expected L1 message in the flow test.

SendMessageToL1 costs are lowered to match measured OS overhead: n_steps 144 → 124 in versioned constants, SEND_MESSAGE_TO_L1_GAS_COST 14470 → 12470 in Cairo OS constants, with matching updates to blockifier syscall tests, versioned-constants diff regression, and central systest blob/receipt fixtures (fees and L2 gas).

OS program hashes (program_hash.json, allowed virtual OS hash slot 2) are refreshed after the Cairo constants change.

^{Reviewed by Cursor Bugbot for commit 1cc8b43. 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 a359fa6. Configure here.}

[yoavGrs]

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

---

crates/blockifier_test_utils/resources/feature_contracts/cairo1/os_resources_test_contract.cairo line 115 at r2 (raw file):

        // send message to l1 syscall.
        // TODO(Yoni, 1/6/2022): In this case the number of steps depends on the payload size -
        //  consider counting it.

Yes, it should be linear.
I don't know what payload size represents an average cost.
In Python, there is 1 element.

Code quote:

        // TODO(Yoni, 1/6/2022): In this case the number of steps depends on the payload size -
        //  consider counting it.

[yoavGrs]

@yoavGrs made 1 comment and resolved 1 discussion.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on Yoni-Starkware).

---

crates/blockifier_test_utils/resources/feature_contracts/cairo1/os_resources_test_contract.cairo line 115 at r2 (raw file):

Previously, yoavGrs wrote…

Yes, it should be linear.
I don't know what payload size represents an average cost.
In Python, there is 1 element.

Oh, you're doing it now, NVM