starknet_os: os resources test - add meta tx

[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 )
• 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 👈 (View in Graphite)
• 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
Touches fee-related syscall gas and OS resource tables plus the OS program hash; scope is test/measurement-driven but affects protocol cost accounting for MetaTxV0.

Overview
Adds MetaTxV0 to the OS syscall resource regression suite and aligns constants with remeasured costs.

The OS resources test contract now invokes meta_tx_v0_syscall twice (empty vs longer calldata) so base and calldata-linear costs can be derived like Deploy. MetaTxV0 is removed from the unmeasurable syscall list and added to syscalls with a linear factor; inner-call subtraction clears memory holes so nested __execute__ overhead does not skew MetaTxV0 numbers.

Versioned constants and Cairo OS constants bump MetaTxV0 gas and VM resources (steps and Pedersen builtins). The pinned deployable measurement account takes variable-length calldata on __execute__ / validate paths, with updated Sierra/CASM artifacts. OS program hash in program_hash.json changes with the rebuilt OS.

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

[Yoni-Starkware]

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

---

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

            calldata: array![0, 0, 0, 0].span(),
            signature: array![].span(),
        )

Call the const contract instead, so you could have a base cost without arguments (same comment as the deploy syscall)

Code quote:

        // meta_tx_v0 syscall - base.
        meta_tx_v0_syscall(
            address: self_address,
            entry_point_selector: EXECUTE_FUNCTION_SELECTOR,
            // class hash, address, deployable class hash, extra args len.
            calldata: array![0, 0, 0, 0].span(),
            signature: array![].span(),
        )

[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 7c9637b. Configure here.}

[cursor]

Regression diff has wrong MetaTxV0 values

Medium Severity

The regression diff file claims MetaTxV0/constant/n_steps: 1333 and pedersen_builtin: 13, but the actual blockifier_versioned_constants_0_14_4.json has n_steps: 1315 and pedersen_builtin: 10. The 0.14.3 file has n_steps: 1301 and pedersen_builtin: 9. The regression diff format shows the 0.14.4 value (confirmed by the CallContract/n_steps: 901 entry matching the 0.14.4 file), so these values are inconsistent and will likely fail regression tests.

Additional Locations (1)

• crates/blockifier/resources/blockifier_versioned_constants_0_14_4.json#L363-L368

 

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