l2geth: allow for unprotected txs
The old transaction batch serialization assumed that the correct chain id was used as there was a custom transaction serialization used. Now that the full RLP of the transactions are submitted to L1 for availability, it is possible to enable non EIP155 transactions. This allows for universal addresses to be used, where the same address exists across many chains. A test is updated to test specifically that transactions that are not protected with a chain id can be submitted and accepted by the sequencer.
Showing
Please register or sign in to comment