L1MessageTx transactions are unsigned objects and as such can not be authenticated. Therefore we should not allow for these transactions to be consumed from the transaction pool. Instead we should modify the payload attributes on the engine api to support for a trusted entity to inject these transactions as they are read from L1.
Overview
L1MessageTx
transactions are unsigned objects and as such can not be authenticated. Therefore we should not allow for these transactions to be consumed from the transaction pool. Instead we should modify the payload attributes on the engine api to support for a trusted entity to inject these transactions as they are read from L1.