Giters

pcaversaccio / createx

Factory smart contract to make easier and safer usage of the `CREATE` and `CREATE2` EVM opcodes as well as of `CREATE3`-based (i.e. without an initcode factor) contract creations.

Home Page:https://createx.rocks

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Clarification request - PK management of CreateX deployer

radeksvarz opened this issue · comments

commented

CreateX is awesome contract to ensure having the same address on the different EVM chains.

It is assumed that CreateX will be deployed on the future / not yet rolled out EVM chains.

In order to satisfy this assumption following risks shall be addressed:

  • risk of loss of deployer's PK (this would result into impossibility to deploy to the new chains having replay protection )

  • risk of leakage of deployer's PK (this could result in frontrunning the CreateX deployment transaction)

Can you please address these risks and describe mitigations here / into README?