anvil: problems with estimate gas - max fee per gas less than block base fee about foundry HOT 4 OPEN

just confirming that you are hitting max fee per gas less than block base fee while calling eth_estimateGas on anvil? or it is happening when sending transactions?

from foundry.

@klkvr It happens when i try to send a transaction. I looked around in the code and found that it is due to some automatic gas config that hardhat is taking care of. the source of the difference is in the eth_feeHistory method. Hardhat uses this to calculate the maxFeePerGas value to set. For the following request, i get different results for different versions
cast rpc eth_feeHistory 0x1 latest

On nightly-2cb875799419c907cc3709e586ece2559e6b340e (working for me):
{"gasUsedRatio":[],"oldestBlock":"0x0","reward":[]}

On the most recent version:
{"baseFeePerGas":["0x3b9aca00","0x1dcd6500"],"gasUsedRatio":[0.0],"oldestBlock":"0x0","reward":[]}

In the most recent version, i think its a little odd that there are two entries returned, when no blocks have been mined on the node, but this seems to be the source of the issue. Not sure if this is intended behavior or not.

it seems to be fixed in the most recent version of hardhat, which I can't upgrade to at the moment, but given that other issues in other places arose around the same time (previously mentioned issues), i'm wondering if its intended.

from foundry.

Fee history contains items for genesis block and for the next block (pending) which is correct I believe, not sure why exactly such response makes hardhat to produce an invalid transaction

from foundry.

I see thanks for the explanation. That makes sense, but is it a little odd that the next block value: 0x1dcd6500 is 500,000,000 when the node base fee is 1,000,000,000?

from foundry.