Currently, the module contracts are deployed using the Arachnid CREATE2 deployer, that relies on a non-EIP-155 transaction.
Proposed solution
In order to ensure that we have full EIP-155 compatibility, we should deploy our module contracts using the Safe singleton factory, the same deployer contract used by the core Safe smart account contracts.
Alternatives
Continue to use the non-EIP-155 compatible deployer contract.
Context / issue
Currently, the module contracts are deployed using the Arachnid
CREATE2
deployer, that relies on a non-EIP-155 transaction.Proposed solution
In order to ensure that we have full EIP-155 compatibility, we should deploy our module contracts using the Safe singleton factory, the same deployer contract used by the core Safe smart account contracts.
Alternatives
Continue to use the non-EIP-155 compatible deployer contract.