class ECDSASignature(Container): y_parity: boolean r: uint256 s: uint256
Nice to see that the new transaction format replaces the RLP transaction encoding with SSZ and moves
chain_id to be a field allowing for using
boolean for `y_parity.
There’s potential for some optimisation here at the expensive of some clarity: EIP-2098: Compact Signature Representation
Was this discussed yet?
parity field seems to have a 1 byte overhead so this is neglible.