Direct answer
Use this estimator for early smart-contract deployment planning, then verify final gas with Forge, Hardhat, or chain simulation.
Simple ERC-style storage contract
Input: Solidity code with one storage write function and a 20 gwei override.
Output: The output should show detected functions, Ethereum deployment estimate, L2 rough estimate, and optimisation flags.
How to use this tool
- 1. Paste Solidity code.
- 2. Choose networks or override gas price.
- 3. Review detected functions and estimated gas.
- 4. Use optimisation notes before deployment.
How EVM gas pricing works
Gas estimates combine operation cost with current or assumed gas price and native-token price. L2s add their own execution and data-availability components, so the cheapest chain can change by workload.
This implementation uses static heuristics rather than a full solc WASM compiler. Treat it as planning guidance, then verify with Forge or Hardhat gas reports before deployment.
Optimisations that move the bill
Storage writes dominate many contracts. Packing variables, using calldata, custom errors, immutable variables, and careful loop bounds can reduce cost. The tool flags common patterns but cannot prove semantic safety.
Assumptions and methodology
This tool uses transparent browser-side calculations and curated assumptions rather than LLM-generated recommendations. Outputs are planning estimates. They should be validated against provider pricing, production traces, engineering quotes, or domain review before money, compliance, safety, or hiring decisions are made.
Numerical defaults are dated and surfaced on the page. The methodology favours explicit assumptions over false precision: every estimate is meant to expose the variable that drives the result, not to pretend that early planning data is exact.
Turn the result into an implementation plan
Bring the scenario to a strategy call and I will pressure-test the workflow, assumptions, failure modes, and delivery path.
Book a strategy callFrequently asked questions
- How accurate is per-function gas?
- This browser estimator is directional. It detects Solidity functions and applies static heuristics. Use forge gas reports, Hardhat, or chain-specific simulation for deployment-grade accuracy.
- Why is Base sometimes cheaper than Arbitrum?
- L2 pricing depends on execution fees, data availability, congestion, and compression. A chain that is cheap for one transaction shape may be less cheap for another.
- Do Cosmos chains use the same model?
- No. Cosmos SDK chains use gas-like metering but fee markets and message costs differ by chain. Treat Cosmos estimates as per-message planning values, not EVM gas equivalents.
- Does this account for EIP-4844?
- The estimator includes L2 discount assumptions but does not fetch live blob fee markets. Verify final deployment cost with the target chain tooling.
- Can I estimate proxy patterns?
- You can approximate proxy patterns by increasing deployment bytecode and adding function overhead. For exact cost, compile the proxy and implementation with your actual tooling.
- How fresh is the gas feed?
- This implementation uses editable default gas values rather than a live feed. Add a cached gas API route before relying on it for same-day deployment decisions.