Diagnosing Gas Estimation and Insufficient Funds Errors in Hardhat
Learn how to distinguish between actual funding shortages and masked Solidity reverts when encountering 'Insufficient funds' and 'Gas estimation failed' errors in Hardhat.
Loading…
ReadMeFeed / Community knowledge
Hardhat
Real questions. Useful conversations. Find the people who know your stack.
Hardhat
Developer tools · #hardhat
solidityHardhat Network Forking: Architecture Note for Isolated Mainnet‑Like Testing
An architecture note covering Hardhat's network forking: requirements, minimal design, trust boundaries, operational checks, failure modes, and triggers for redesign.
Debugging Solidity Contracts with Hardhat's console.log
Learn how to use Hardhat's built‑in console.log to debug Solidity contracts directly from the terminal, with a minimal setup, example contract and test, and notes on gas overhead and network limits.
Why don’t Hardhat named accounts resolve correctly in production when using environment variable overrides?
When deploying a contract locally with Hardhat, named accounts (e.g., deployer ) resolve to the expected address and the deployment succeeds. In the production environment, which connects to the Goerli testnet via an Infura endpoint, the same deployment script fails with an “address not found” error, even though the namedAccounts section in hardhat.config.js
Intermittent connection pool exhaustion in Hardhat Network under concurrent JSON‑RPC load
Goal: Identify the concurrency level at which Hardhat Network’s built‑in connection pool begins to reject or delay JSON‑RPC requests, producing intermittent timeouts or 'connection pool exhausted' messages. Constraints: The pool size is not documented or configurable in hardhat.config.js, and its effective limit changes depending on whether the network is fo
Type is not a constructor during hardhat-gas-reporter initialization
When utilizing the @nomicfoundation/gas-reporter plugin alongside the @nomicfoundation/toolbox, the task initialization frequently fails with a 'Type is not a constructor' error. This typically occurs when the Hardhat environment attempts to resolve dependencies during a contract deployment or test task run.\n The issue seems linked to a version mismatch bet
Hardhat CLI and Solc Compiler: Default Version Selection
Goal: Identify the Solidity compiler version that Hardhat employs when no explicit `solidity` field is present in `hardhat.config.js`, and understand how this implicit choice influences plugins that rely on matching compiler versions for TypeChain artifact generation. Constraints: Hardhat ships with a bundled solc version that may differ between releases, an
Hardhat Network state persistence limits during node restarts
The Hardhat Network provides a volatile local environment designed for rapid development and testing. By default, the internal state—including deployed contracts and account balances—is stored in memory and resets whenever the npx hardhat node process is terminated. While the framework supports snapshots for reverting state during test execution, there is a
Hardhat artifact cache serves stale ABI after Solidity version update
When the Solidity version specified in hardhat.config.js is changed, developers expect Hardhat to recompile contracts using the new compiler version. However, the built‑in artifact cache may continue to return previously compiled ABI and bytecode that were generated with the old compiler, leading to deployment failures or runtime reverts. The cache key inclu