Small review of spacing convention.
Will review the content afterwards, I'm asking L1 client teams what they do with Legacy transactions to get a sense of what to do in Starknet's case.
I would be keen to maximize retro compatibility, wallets (Argent X / Braavos) are easy to upgrade, but not old accounts (OZ first versions, or otherwise). For instance, max_fee could be considered to be: "the maximum amount of steps such that steps_number * fee_per_step == max_fee == 1559_starknet_base_fee and tip == 0"
The sequencer is then free to ignore this transaction until there is a non-zero value to include it.
Small review of spacing convention. Will review the content afterwards, I'm asking L1 client teams what they do with Legacy transactions to get a sense of what to do in Starknet's case.
I would be keen to maximize retro compatibility, wallets (Argent X / Braavos) are easy to upgrade, but not old accounts (OZ first versions, or otherwise). For instance, max_fee could be considered to be: "the maximum amount of steps such that
steps_number * fee_per_step == max_fee == 1559_starknet_base_feeandtip == 0" The sequencer is then free to ignore this transaction until there is a non-zero value to include it.