…lass#4224) **Motivation** Noticed a weird behavior while testing lambdaclass#4211. Once the configured `max_gas_limit` was reached, no further deposits were included in subsequent blocks until a new batch is started. This happens because we first update the `privileged_range`, and if the transaction is later rejected (for example, due to the gas limit), we don’t remove the nonce from the range. As a result, when the next block starts, we try to add the tx again, but since the nonce was already included to the range, the transaction is marked as out-of-order. #### Why haven’t we seen the error before? There is an `if` check that prevents the error from appearing in our daily usage: ```Rust // Check if we have enough space for the StateDiff to run more transactions if acc_size_without_accounts + size_accounts_diffs + SIMPLE_TX_STATE_DIFF_SIZE > safe_bytes_per_blob { warn!("No more StateDiff space to run transactions"); break; }; ``` This is an early return that checks if we have enough space for a simple transfer in our `stateDiff`, and stops adding transactions to the block if we don’t. But, it can happen that we have enough space for a simple transfer, but the transaction we are trying to add occupies more space than that, making us restore the previous state in another check a[ few lines later](https://github.com/lambdaclass/ethrex/blob/0cae720162fd889eb18417010e5f091c6d097d35/crates/l2/sequencer/block_producer/payload_builder.rs#L215).  **Description** Moves the update of `privileged_range` after all other checks have passed. Issues lambdaclass#4248 and lambdaclass#4243 were created. Closes None

L2: make payload_builder ignore stateDiff size checks when running in validium mode #4248

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions

L2: make `payload_builder` ignore `stateDiff` size checks when running in validium mode #4248