-
Notifications
You must be signed in to change notification settings - Fork 17
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
Create 3 support #2
Comments
As far as I can tell, ethereum/EIPs#3171 isn't official, but I have added support for create3-factory. It takes the address of the caller, deployer contract, and the bytecode of the deployer's proxy contract, as there are multiple deployer contracts to choose from. |
i may doing it wrong, but given the contract bytecode, the deployer-address (0x9fBB3DF7C40Da2e5A0dE984fFE2CCB7C47cd0ABf) and the msg.sender (my) address.. i get a salt, but when i test it it gives me a different final contract address.. what am i missing? |
Just to confirm, did you set the bytecode to |
nope, but it's working now! where i could find that? i used the bytecode from etherscan and it didn't work, with this it's working! great!! |
The bytecode needed is the bytecode of the proxy contract the deployer uses, not the deployer itself. You can find it here. |
damn, thank you! i didn't understand that at first glance.. thank you again for all the help! +++ |
It would be great to add create3 support for just using the salt and not needing the initcode hash.
The text was updated successfully, but these errors were encountered: