Skip to content

proxies:clone

Deploy an ERC-1167 minimal proxy (clone) of an implementation contract. Binds the predicted clone address to . Pass --salt for a deterministic CREATE2 deployment.

⚗️ Experimental — available at next.evmcrispr.com.

Smart blocks: build-time inputs only. Implementation, factory and salt determine the bound clone address.

proxies:clone <variable> <implementation>
NameTypeEvaluationDescription
variablevariableBuild timeVariable to bind the clone address to
implementationaddressBuild timeImplementation contract the clone delegates to
NameTypeEvaluationDescription
--saltbytes32Build timeSalt for deterministic CREATE2 deployment through the Arachnid deployer (override with --via)
--viaaddressBuild timeOverride the CREATE2 factory address used with --salt
--fromaddressBuild timeDeprecated: run the command inside switch --as <address> ( … ). Sender address. Defaults to the acting account. For plain CREATE this is also the prediction deployer.
load proxies
set $vestingImplementation 0xf8D1677c8a0c961938bf2f9aDc3F3CFDA759A9d9
# Plain CREATE clone
proxies:clone $vesting $vestingImplementation
exec $vesting initialize(address,uint64) @me 1767225600
# Deterministic CREATE2 clone (batchable, predictable address)
proxies:clone $vesting $vestingImplementation --salt 0x0000000000000000000000000000000000000000000000000000000000000001
  • Deploys an ERC-1167 minimal proxy that delegates every call to the implementation. Clones are cheap but not upgradeable.
  • The predicted address is bound to the variable before deployment, so later commands in the same script can use it.
  • Plain CREATE clones cannot run inside a batch (the nonce-based prediction would drift) — use --salt there.
  • A plain CREATE clone is predicted from the acting account: the connected one, or the account of an enclosing switch --as <address> ( … ). The --from option is deprecated.