EIP-6493: SSZ Transaction Signature Scheme

[etan-status]

Alternative design based on multidimensional fees:

EIP-7706: Create a separate basefee and gaslimit for calldata

The EIP describes three changes: Switch to a multidimensional fee structure Allowing priority fees for blob transaction Introduction of a separate calldata gas fee I’m wondering about the encoding of the max_fees_per_gas and priority_fees_per_gas vectors on JSON-RPC. Natively, they would be represented as a list of integers (in the typical string representation), without any guidance on which of the fees corresponds to what type of fee. For example, there must be external knowledge that the s…