t8n doesn't load invalid JSON transaction about evmone

[chfast]

Here the problem is the transaction serializer doesn't really want to encode an invalid transaction. And we serialize the transaction to compute its hash.

I think we can remove these restrictions and encode values as they are. Similar restriction is for signature's $v$ value.

Do other clients are able to do this?

[winsvega]

other clients use rlp. but yes geth had similar crash issue. because on the one hand the rlp is valid.
but on the other hand the transaction structure is invalid.
I think it is just the matter of how t8n treats this transactions. I would expect - if anything goes wrong with tx, just put it in rejected transaction list in out.json

[winsvega]

http://retesteth.ethdevops.io/temp/evmone/evmone_Cancun_block1_0x0e55be/txs.json

I see that for t8n if tx is creation it does not being exported at all into .json. but this could be an old geth requirement.
can as well just export for creation transactions to : "",

[chfast]

to : ""

Do you mean this should also be interpreted as a create transaction?