Transaction type in RPC calls

[deffrian]

Expected behaviour

Transactions executed as transactions of type set in rpc request.

Actual behaviour

Transaction type ignored.
For example in hive test eth_estimateGas/estimate-with-eip4844 transaction type is set to 0x5. This probably should cause invalid argument error, but transaction executed as blob transaction.

[s1na]

To give some context: the Transaction structure in the specs takes in a type field which is supposed to determine the type of the tx from the user-side. We don't have this field and infer the type based on the fields, which I think is a good UX. The question is what to do now? Nethermind sees the type: 0x5 in the test above and rejects the input. We just ignore that field and proceed.

The only reason I can see for having a type field is: if we set the default tx type to 0x2 then it will become impossible for user to submit a type 0x1 tx. But I don't see any reason for doing that.