Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

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

Clarification request - PK management of CreateX deployer #60

Closed
radeksvarz opened this issue Dec 24, 2023 · 0 comments
Closed

Clarification request - PK management of CreateX deployer #60

radeksvarz opened this issue Dec 24, 2023 · 0 comments
Assignees
Labels
documentation 📖 Improvements or additions to documentation
Milestone

Comments

@radeksvarz
Copy link

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?

Repository owner locked and limited conversation to collaborators Dec 24, 2023
@pcaversaccio pcaversaccio converted this issue into discussion #61 Dec 24, 2023
@pcaversaccio pcaversaccio self-assigned this Dec 24, 2023
@pcaversaccio pcaversaccio added the documentation 📖 Improvements or additions to documentation label Dec 24, 2023
@pcaversaccio pcaversaccio added this to the 1.0.0 milestone Feb 21, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
documentation 📖 Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants