You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploying a contract using a salt and a bytecode leads to a successful transaction. But the address of the deployed contract does not contain any bytecode after the transaction.
This means it is not possible to use the precomputed address with CREATE2.
Steps to Reproduce
Example:
I created a contract factory. I can also determine my future address using CREATE2, but deploying the contract doesn't work. I'll send the address of the deployed contract. This has no bytecode but events are tracked. This seems like a bug to me.
Summary
Deploying a contract using a salt and a bytecode leads to a successful transaction. But the address of the deployed contract does not contain any bytecode after the transaction.
This means it is not possible to use the precomputed address with CREATE2.
Steps to Reproduce
Example:
I created a contract factory. I can also determine my future address using CREATE2, but deploying the contract doesn't work. I'll send the address of the deployed contract. This has no bytecode but events are tracked. This seems like a bug to me.
Example contract deployed with salt and bytecode
The following link shows the FactoryContract. A new contract with a “salt” should be deployed in the “createWallet” function. But it doesn't work.
Example contract of a contract factory
The text was updated successfully, but these errors were encountered: