It is possible that the computed replaySafeHash begins with 0xef. In such a case, our implementation, inspired by this example, would result in a contract bytecode also starting with 0xef.
With the London upgrade, create and create2 calls will fail if the deployed bytecode begins with 0xef.
This PR updates the constructor of the ERC1271InputGenerator contract to prefix the returned replaySafeHash with a constant 0xff byte. This prevents the aforementioned error from occurring.
It is possible that the computed
replaySafeHash
begins with0xef
. In such a case, our implementation, inspired by this example, would result in a contract bytecode also starting with0xef
.With the London upgrade,
create
andcreate2
calls will fail if the deployed bytecode begins with0xef
.This PR updates the constructor of the
ERC1271InputGenerator
contract to prefix the returnedreplaySafeHash
with a constant0xff
byte. This prevents the aforementioned error from occurring.