`cast run` produces incorrect simulation of Arbitrum transaction (succeeds where it should fail)

[impactdni2]

Component

Cast

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

forge 0.2.0 (9881e7d 2024-03-28T00:18:02.827635071Z)

What command(s) is the bug in?

cast run 0x1d66909d9039e5937406357449fad064edbb6d9c81944a8001ebfc4f0ba6d0b9 --rpc-url "https://arb1.arbitrum.io/rpc"

Operating System

Linux

Describe the bug

Transaction should run out of gas according to block explorers (ex: https://arbiscan.io/tx/0x1d66909d9039e5937406357449fad064edbb6d9c81944a8001ebfc4f0ba6d0b9), however when simulating in cast it succeeds:

cast run 0x1d66909d9039e5937406357449fad064edbb6d9c81944a8001ebfc4f0ba6d0b9 --rpc-url "https://arb1.arbitrum.io/rpc"
...
Transaction successfully executed.
Gas used: 611728

[zerosnacks]

Thanks @impactdni2, confirming that this is indeed the case

For future reference: https://dashboard.tenderly.co/tx/arbitrum/0x1d66909d9039e5937406357449fad064edbb6d9c81944a8001ebfc4f0ba6d0b9

[zerosnacks]

For future reference: could be related to precompiles, should be investigated further

Possibly related: #2997

[grandizzy]

Problem here looks to be the way gas limit is calculated for Arbitrum chain, according to https://medium.com/offchainlabs/understanding-arbitrum-2-dimensional-fees-fd1d582596c9 it is L2 gas used + ( L1 calldata price * L1 calldata size) / (L2 gas price). In cast run we set block gas limit to what we get back from provider (in this case is 1,125,899,906,842,624 which is not right either as the effective execution gas limit is capped at 32 million: https://docs.arbitrum.io/build-decentralized-apps/arbitrum-vs-ethereum/block-numbers-and-time#block-gas-limit) hence this tx passes when simulate

[mattsse]

I think we need so helpers to modify these fields based on the chainid like

fn apply_chain_specific_cfg(&mut BlockEnv, chainId, &rpc::Header) or something