Skip to content
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

use deterministic CREATE2 opcode #20

Open
rainbreak opened this issue Oct 19, 2018 · 1 comment
Open

use deterministic CREATE2 opcode #20

rainbreak opened this issue Oct 19, 2018 · 1 comment

Comments

@rainbreak
Copy link
Member

Constantinople will add the CREATE2 opcode, which has contract addresses that are a function of the code hash. This would remove the need for caching.

https://eips.ethereum.org/EIPS/eip-1014

@PaulRBerg
Copy link

This would remove the need for caching.

A hypothetical execute function that renounces caching would need the deployer address, the salt, and the construction bytecode as parameters.

What do you do if no contract is found for that set of parameters? Do you deploy it via the DSProxy? Do you revert? Users might prefer to use their own factories instead of letting the DSProxy do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants