Skip to content

create2.md

Latest commit

 

History

History
82 lines (55 loc) · 4.15 KB

create2.md

File metadata and controls

82 lines (55 loc) · 4.15 KB
Raw

wallet-cli contract create2

Compute the address a CREATE2 deployment would land on.

Synopsis

wallet-cli contract create2 --deployer <address> (--code <hex> | --code-file <path>) --salt <n> [options]

Description

Pure local arithmetic: no node is contacted, nothing is broadcast, and no account or password is involved. The result is the same on every TRON network, so --network does not affect it. TRON only — on an EVM network the command fails with family_mismatch.

TRON's derivation is not Ethereum's — do not compute it with an EVM calculator. The address is

sha3omit12( deployer (21 bytes, 0x41-prefixed) ‖ salt (32 bytes) ‖ keccak256(code) )

where sha3omit12 takes bytes [11:32] of the keccak256 digest, overwrites the first byte with 0x41, and Base58Check-encodes the result. There is no 0xff prefix: the 21-byte 0x41-prefixed deployer already separates the domain. The same deployer, salt, and code therefore yield different addresses on TRON and Ethereum.

The code must be the creation bytecode with constructor arguments already appended — not the runtime bytecode. One byte of difference in the constructor arguments gives an entirely different address. Creation bytecode usually runs to tens of thousands of characters, which is why --code-file exists; a 0x prefix and any whitespace are stripped from either form.

--salt is a decimal integer (64-bit signed). It is placed in the low bytes of a 32-byte salt with the rest zero-filled; hex salts are not accepted.

Deploying with CREATE2 itself requires the chain to have TVM Constantinople enabled, but this command is arithmetic only and is not subject to that.

Options

Option Description
--deployer <address> Required. Address performing the CREATE2 — a factory contract or a plain account
--code <hex> Creation bytecode, constructor arguments included. One of --code / --code-file
--code-file <path> Read the creation bytecode from a file — preferred, since it is usually very long. One of --code / --code-file
--salt <n> Required. Salt as a decimal integer, zero-padded to 32 bytes

Plus the global options.

Examples

wallet-cli contract create2 --deployer TQkXm4vN...5Zt7Uw --code-file ./MyToken.creation.hex --salt 1
Contract address (CREATE2)
  Deployer   TQkXm4vN...5Zt7Uw
  Salt       1  (0x000000…0001)
  Code hash  c8f4a1...b91b
  Address    TXm5RQ7d...9kPa

Short bytecode can go inline instead:

wallet-cli contract create2 --deployer TQkXm4vN...5Zt7Uw --code 6080604052... --salt 255 -o json
{"schema":"wallet-cli.result.v1","success":true,"command":"contract.create2","data":{"deployerAddress":"TQkXm4vN...","salt":255,"saltHex":"0x00000000000000000000000000000000000000000000000000000000000000ff","codeHash":"c8f4a1...b91b","address":"TWq8dK3n...2mHb"},"meta":{"durationMs":3,"warnings":[]},"chain":{"family":"tron","network":"tron:728126428","chainId":"728126428"}}

Output

Field Type Meaning
deployerAddress string The deployer as given, base58
salt number | string The salt as given, decimal. A string when it falls outside the safe-integer range, so a full int64 salt survives JSON
saltHex string The zero-padded 32 bytes that actually enter the hash
codeHash string keccak256 of the creation bytecode
address string The resulting contract address, base58

The command never contacts a node, but it is still a TRON chain command: the envelope carries the usual chain block for the selected network. --network is optional here and only picks which network the block names.

Exit status

0 success · 1 execution failure · 2 usage error (missing_option — no --deployer or --salt; file_not_found — --code-file does not exist; invalid_value — neither or both code sources, an unreadable code file, malformed deployer address, non-hex code, or a salt outside the signed 64-bit range).

See also

contract deploy · contract info · encoding convert