Rolling fork to specific transaction fails with validation error: priority fee is greater than max fee

[nuntax]

Component

Forge

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

• Foundry
• Foundryup

What version of Foundry are you on?

forge Version: 1.2.2-nightly Commit SHA: b42d512 Build Timestamp: 2025-06-03T06:02:38.785261834Z (1748930558) Build Profile: maxperf

What version of Foundryup are you on?

foundryup: 1.1.0

What command(s) is the bug in?

forge test

Operating System

Linux

Describe the bug

Rolling an arbitrum fork to a specific transaction fails with the following error:
vm.rollFork: backend: failed committing transaction; transaction validation error: priority fee is greater than max fee
This only happens with one specific transaction.
Further than that arbitrum doesn't support eip1559 style fees, neither is the transaction itself a eip1559 transaction. (arbitrum supports them for compatibility reasons, just ignores the priority fee parameter).
Minimal example to reproduce:

//SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.20;
import {Test} from "forge-std/Test.sol";


contract IssueTest is Test {
        uint256 arbFork;

    function setUp() public {
        string memory rpcUrl = vm.envString("ARB_RPC_URL");
        arbFork = vm.createSelectFork(
            rpcUrl
        );
    }
    function testIssue() public {
        bytes32 txHash = 0x2e43e9ececcbb9cd08ce061edc3b4d39ca2b0ba480034e5f4650ba0065bf6b62;
        vm.rollFork(txHash);
        assertTrue(true, "This is a placeholder test that always passes.");
    }
}```
Specify the ARB_RPC_URL and run with ```forge test --mt testIssue```

[nuntax]

Forgot to mention that I tested this on nightly and stable

[grandizzy]

replaying tx with cast results in

Error: Failed to execute transaction: 0xf7ca20b00441b6277b0ed25ae3f8520be299cfdcdc6cd1420babc31643a4922e in block 22614117

Context:
- Error #0: EVM error
- Error #1: transaction validation error: priority fee is greater than max fee

likely same reason as in #7514

[nuntax]

I don't know if this is helpful in anyway but i did some testing myself and the issue in this case seems to be that arbitrum doesn't enforce any restrictions on the eip1559 fees. its possible to set the max priority fee above the max fee which causes the error i encountered while testing.
Heres a test tx: 0xb5e8b1cd23b8c07dd422b90002cb237afd4140e5d931a419ffbbb966bb31832e
as expected cast run 0xb5e8b1cd23b8c07dd422b90002cb237afd4140e5d931a419ffbbb966bb31832e --rpc-url $RPC
fails with Error: EVM error; transaction validation error: priority fee is greater than max fee

[mattsse]

this is directly enforced by the eip, there is currently no setting to disable this, but this seems useful, opening an issue for this on revm