Deterministic CREATE2 Address Precomputer

WHAT IT DOES

This tool connects to your EVM wallet and computes deterministic contract addresses using the CREATE2 opcode. It takes a deployer address, bytecode hash (keccak256 of init code), and salt value to predict the address where a contract will be deployed. The tool also checks the current chain to see if the predicted address already has bytecode deployed, allowing you to verify whether a contract has been deployed at the expected address.

HOW TO USE

Connect your Web3 wallet using the Connect button. Enter the deployer address that will execute the CREATE2 deployment in the Deployer Address field. Enter the keccak256 hash of the init code (bytecode) in the Bytecode Hash field. Enter the salt value (hex, 32 bytes) in the Salt field—this can be left empty for a zero salt. Click "Compute Address" to calculate the predicted CREATE2 address. Click "Check Deployment Status" to query the chain and verify if the predicted address already has bytecode deployed. Results appear in the Results card with the predicted address, deployment status, and bytecode presence details.

TECHNICAL MECHANISM: CREATE2 ADDRESS COMPUTATION WITH EIP-1014

The tool implements the CREATE2 address derivation formula defined in EIP-1014. The address is computed as: keccak256(0xff || deployerAddress || salt || keccak256(initCode))[12:]. The tool concatenates the 0xff prefix (1 byte), the deployer address (20 bytes), the salt (32 bytes), and the bytecode hash (32 bytes) into a single 85-byte buffer. The keccak256 hash of this buffer is then computed, and the last 20 bytes of the result form the predicted contract address. For deployment status checking, the tool uses provider.getCode(address) to query the current bytecode at the predicted address. If the returned code is non-empty (not 0x or 0x0), the contract is considered deployed.

WHAT IT CANNOT SEE

This tool cannot guarantee that a predicted address will remain undeployed at deployment time—another transaction may deploy to the same address between computation and deployment. It cannot predict deployment failures due to gas or bytecode issues—the tool does not simulate deployment transactions. It cannot verify that the computed address corresponds to the intended bytecode without external validation—the tool does not check bytecode correctness. It relies on on-chain bytecode queries and may fail for contracts deployed with different initialization parameters—the tool only checks for the presence of bytecode, not its content. It cannot simulate deployment transactions or predict future chain state.

PLEASE NOTE

This is a read-only tool—it never signs transactions or requests write permissions. All data is fetched on-demand and stored only in memory; nothing is persisted across page reloads. The tool supports EVM chains only—Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche, Base, and Fantom. Always verify that the deployer address, bytecode hash, and salt are correct—incorrect inputs will produce incorrect predicted addresses. The bytecode hash must be the keccak256 hash of the full init code, not the runtime bytecode.