everdred

@neurone it looks like this still isn't passing CI, we'll restart it to see if it's flaky. Otherwise, let us know if we can help resolve the issue.

Thank you for your interest @swisstackle! I plan to look into this a bit next week. Let me know if you've researched it at all, otherwise I'll report back here...

I spiked on this this issue for a some time, but have to leave it as it. In an attempt to capture my findings, I put together this research doc:...

Ah! It looks like we aren't [accounting](https://github.com/trufflesuite/truffle/blob/a6418b7347139eaf2fa4ae0328a824a98d5434be/packages/interface-adapter/lib/adapter/web3/index.ts#L82) for the fact that Arbitrum fees are surfaced differently than mainnet fees: Arbitrum receipt: ```javascript { "blockHash": "0x46b4605bb9c89f3f2c19b74b5c5aa1d77a4af090bba473b4d49396fd6b0cc564", "blockNumber": 7794449, "contractAddress": "0x0EA91c4d350458880BADf654031E1FcA30B3C2Eb", "cumulativeGasUsed":...

It looks like the `feeStats` metadata above is more of a symptom than the specific issue.

 Truffle uses some data from the transaction response and some from the receipt we...

Understood, thanks for the clarification @fredlacs! I just tried adding those 4 `feeStats.paid` values with my example transaction and came up with the accurate cost. To support this from the...

If `effectiveGasPrice` will eventually be updated to fix the inaccuracy, then this^ would definitely simplify things. And as per [the spec](https://github.com/ethereum/execution-specs/pull/251), we should be migrating toward `effectiveGasPrice` regardless as `gasPrice`...

Just chatted with @davidmurdoch: in ganache v7 eth_getTransactionReceipt returns `effectiveGasPrice`, but no `gasPrice`. In v6 we'd only have `gasPrice`. I _think_ ```js const gasPrice = new BN(receipt.effectiveGasPrice ?? tx.gasPrice); ```...

Same issue as well. You mentioned that it was fixed the webkit problem Issue #2. I even went back and found the commit here: http://goo.gl/asDTAC and tried that version in...

I am running into the same issue. Still no fix?