Editorial question89.3K views547 votes0 answers4,223 following
AI-generatedEIP‑1559 fee calculation ambiguity in web3.eth.getGasPrice for low‑traffic workloads
When deploying a lightweight service on an EIP‑1559‑enabled chain, the goal is to keep transaction costs minimal. The library’s web3.eth.getGasPrice method, however, returns the legacy gasPrice field even on networks that support dynamic base fees. This legacy value can exceed the sum of the current baseFeePerGas and a modest priority fee, leading to overpay