Loading video player...
TL;DR deterministic-deployer-evm is a one-shot CLI that takes your contract (a Foundry artifact path **or** a pre-built registry entry), deploys it via the to as many EVM chains as you want **in parallel**, and (optionally) verifies it on Etherscan all from a single command. Same salt + same bytecode → same address on every chain. No scripts, no folders full of forgotten deploy logs. The Pain - Every Solidity engineer has this inner pain. Deploy to a new chain (or chains) again. Where do I store the deployment scripts, and what's the correct salt for the deterministic address? It gets to be a hell. - On the other side, the product gets a new Solidity dev and the old one didn't invest enough time to onboard them and show where the deployment scripts or salts are stored locally and again, the same loop of *"where is the script and the salt…?"*, or *"what was the solc version???"* - I know this pain because I've been on both sides when you get a message from your previous team, *"Hey mate, do you remember where the deployment script is?"*, or when I find myself running tons of scripts just to find the correct one for a deterministic deployment with the same address across any chain. - And I haven't even started to touch the pain in your lower back when you need to deploy a deterministic address across multiple chains.