Identify which Starknet v3 fee bound rejects a transaction
A v3 fee budget has separate quantity and unit-price limits for each resource. A large total budget cannot make up for an inadequate price cap in one required dimension.
Compare each resource against its own cap
Estimate the transaction under the chain’s current rules and inspect all resource bounds, including L1 gas, L2 gas and L1 data gas where required. The abbreviated example shows only two resource entries in illustrative units.
L2_GAS: max_amount = 40000, max_price_per_unit = 100
L1_DATA_GAS: max_amount = 100, max_price_per_unit = 5
If the L1 data gas unit price is six, a cap of five is insufficient even when plenty of L2 gas budget remains. Increasing only the L2 gas quantity leaves that price mismatch untouched. Check estimated consumption independently from the block price.
Rebuild before signing changes
Bounds form part of the transaction that the account authorizes. Rebuild and sign the updated transaction under the correct transaction version. Price changes between estimate and inclusion remain possible, so record the estimate block when investigating a rejection. docs.starknet.io Starknet documentation