hardhat

Define a module with buildModule() using m.contract() for each contract and m.getParameter() for constructor args, then run npx hardhat ignition deploy with the module path and target network. Ignition resolves dependencies, tracks state in ignition/deployments/, and supports verification via npx hardhat ignition verify.

Hardhat suits teams needing TypeScript integration, complex deployment orchestration via Ignition, and a large npm plugin ecosystem. Foundry is better for fast compilation, fuzz testing, and Solidity-native tests. Both can coexist using the @nomicfoundation/hardhat-foundry plugin.

Import loadFixture from @nomicfoundation/hardhat-toolbox/network-helpers and pass it an async function that deploys your contracts. It snapshots EVM state on first call and reverts to that snapshot on subsequent calls, giving each test clean state without redeploying.

Verification fails when constructor arguments, compiler version, or optimizer settings differ from the original deployment. Pass exact constructor args via a --constructor-args file, match the solidity settings in hardhat.config.ts, and wait a few minutes after deployment for Etherscan indexing.

Yes, forking with a pinned blockNumber requires archive data since standard RPC endpoints only serve recent state. Use an archive-tier provider such as Alchemy Growth, Infura archive, or a local archive node like Erigon or Reth.

Use Hardhat Ignition, the official deployment system from the Hardhat team. hardhat-deploy is a community plugin not maintained by Nomic Foundation. Ignition provides declarative modules, dependency resolution, deployment state tracking, and built-in verification.