JSON-RPC 0.8.0: add l1_data_gas to RESOURCE_BOUNDS_MAPPING
#2379
Assignees
Milestone
Comments
kkovaacs
added a commit
that referenced
this issue
Nov 15, 2024
This is a partial implementation: since we don't _really_ use these new values other than passing those on to the Starknet gateway when submitting new transactions the new field is not added to the `ResourceBounds` type in the common crate. We'll have to do that once these values need to be stored in storage and used in the P2P protocol when adding proper support for Starknet 0.13.4. Closes: #2379
This was referenced Nov 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Transaction v3 resource bounds mappings should now contain bounds for
l1_data_gasin addition tol1_gasandl2_gas. This is something we need to change in the common transaction types as well and also in storage.How this affects things like transaction hash computation for v3 transactions is not yet known.
The text was updated successfully, but these errors were encountered: