How to Deploy a Smart Contract: Local Testing to Mainnet

Frequently Asked Questions

01.What is the difference between forge create and forge script for deploying smart contracts?

`forge create` is a single-contract deployment command suited for quick or one-off deployments. `forge script` uses Solidity deployment scripts with the `vm.startBroadcast()` cheatcode, supports multi-contract deployments, and produces a broadcast log for replay or CI integration. For production workflows, `forge script` is preferred because it provides deterministic, auditable deployment artifacts.

02.Which Ethereum testnet should you use for smart contract deployment in 2025?

Sepolia is the recommended primary testnet for smart contract and dApp development in 2025. Goerli was deprecated in April 2024 and is no longer maintained. Holesky operates alongside Sepolia but targets infrastructure and validator testing rather than application development. All new projects should target Sepolia for pre-mainnet validation.

03.How do you verify a smart contract on Etherscan after deploying with Foundry?

Add the `--verify` flag and the `--etherscan-api-key` flag to your `forge script` or `forge create` command. You must also configure the `etherscan` section of `foundry.toml` with the target network name and the API endpoint URL. Foundry submits the flattened source code and constructor arguments to the block explorer's verification API automatically after broadcast.