We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
The text was updated successfully, but these errors were encountered:
pcaversaccio
No branches or pull requests
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?
The text was updated successfully, but these errors were encountered: