apollo_http_server,blockifier_reexecution,starknet_api: move tx json deserializer to starknet_api

[avi-starkware]

Why

apollo_http_server — part of every node build — depends on the entire blockifier_reexecution crate (which drags in blockifier with the reexecution feature, google-cloud-storage, blocking reqwest, and more) for exactly one item: the deserialize_transaction_json_to_starknet_api_tx serde helper.

What

Moves deserialize_transaction_json_to_starknet_api_tx (and its private helper upper_case_resource_bounds_names) to starknet_api::serde_utils, where the Transaction types it produces live and where serde compat helpers already exist — apollo_http_server already imports from that module. The function body is moved verbatim; only visibility changed (upper_case_resource_bounds_names becomes private — it had no callers outside the deserializer) and a doc comment was added.

• apollo_http_server no longer depends on blockifier_reexecution at all.
• blockifier_reexecution imports the function from starknet_api (its serde_utils keeps the reexecution-specific hashmap helpers).
• No dependency additions anywhere: starknet_api already had serde_json; both consumers already had starknet_api.

Validation

• cargo build -p starknet_api -p blockifier_reexecution -p apollo_http_server — passes.
• cargo test on all three crates — 87 + 19 + 37 passed, 0 failed; the raw_rpc_json_test suite (which exercises the moved deserializer on real transaction JSON fixtures) confirmed passing through the new import path.
• cargo clippy --no-deps --all-targets on all three — clean.
• scripts/rust_fmt.sh — applied.

🤖 Generated with Claude Code

[reviewable-StarkWare]

This change is 

[avi-starkware]

• starknet_api: do not panic on malformed resource_bounds in tx json deserializer #14412
• apollo_http_server,blockifier_reexecution,starknet_api: move tx json deserializer to starknet_api #14408 👈 (View in Graphite)
• main-v0.14.3

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

[github-actions]

Artifacts upload workflows:

• Started at 2026-06-07T13:24:44Z
• Started at 2026-06-07T13:25:03Z

[cursor]

PR Summary

Low Risk
Behavior-preserving relocation with existing tests on the deserializer; only build graph and import paths change for consumers.

Overview
deserialize_transaction_json_to_starknet_api_tx (and its private upper_case_resource_bounds_names helper) moves from blockifier_reexecution::serde_utils into starknet_api::serde_utils, next to the Transaction types and existing serde helpers. Logic is unchanged aside from a new doc comment and making the helper crate-private.

apollo_http_server drops the blockifier_reexecution dependency entirely and imports the deserializer from starknet_api (alongside bytes_from_hex_str). blockifier_reexecution now calls the shared helper from starknet_api; its serde_utils only keeps the reexecution-specific hashmap parsing helpers.

This is a dependency slimming change for node builds: the HTTP server no longer pulls in the reexecution stack for a single serde function.

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

[Yoni-Starkware]

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

[AvivYossef-starkware]

@AvivYossef-starkware reviewed 7 files and all commit messages, and made 1 comment.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on avi-starkware).