I found that
Transaction contains fields:
- v, r, s
- init (contains "smart contract creation code" that should return "smart contract runtime code") OR data (arguments to call smart contract, typically "solidity function name hash" and "function arguments")
There are a number of intrinsic parameters used when creating an account: ........, the salt for new account’s address (ζ) .....
The salt ζ might be missing (ζ = ∅); ......
If the creation was caused by CREATE2, then ζ = ∅.
- The "smart contract initialization code" should
- copy code to memory
- using the RETURN(start_offset_of_memory, end_offset) return the "runtime code"
It seems like if I provide the "salt" (of course together with "init" and all other fields except of "data") field in transaction issued from EOA it will create smart contract with deterministic address (just like CREATE2 opcode does)
But there is no such field "salt" for transaction, and I see that everyone create smart with deterministic address using "ProxyFactory smart contract" (OpenZeppelin 1 and 2 or here the Deployer smart contract)
It seems like:
- IF EOA creates smart contract from transaction - smart contract will be created using CREATE approach implicitly
- IF smart contract creates smart contract - it can be created using CREATE or CREATE2 opcodes
Question: is it possible / why it's not possible to create smart contract with deterministic address from transaction itself without using ProxyFactory approach?