`cast run` result is different from the actual transaction

[zzh1996]

Component

Cast

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

• Foundry
• Foundryup

What version of Foundry are you on?

1.4.3-stable

What version of Foundryup are you on?

foundryup: 1.3.0

What command(s) is the bug in?

cast run

Operating System

Linux

Describe the bug

$ cast run 0xae290fe8c89c3e83dff20eeb2b8e3261bcdce0d66441c7056918dfb5fafe6d96
Executing previous transactions from the block.
Traces:
  [14185] 0xB731392c0EB5BF2092f9f7B520DA551f70Ea9131::Claim{value: 46698476594582387}()
    ├─ [2204] 0x000F3df6D732807Ef1319fB7B8bB8522d0Beac02::00000000(00000000000000000000000000000000000000000000000069091d4b) [staticcall]
    │   └─ ← [Revert] EvmError: Revert
    ├─ [0] 0x6e6C36B970f8862bA3F148DEdAB8F98f5ed8b426::fallback{value: 46698476594582387}()
    │   └─ ← [Stop]
    ├─ emit NvStuck(param0: 0x6e6C36B970f8862bA3F148DEdAB8F98f5ed8b426, param1: 46698476594582387 [4.669e16], param2: 1762205003 [1.762e9])
    └─ ← [Stop]


Transaction successfully executed.
Gas used: 35249

The trace and gas used is different from the actual transaction, which does not have the revert and the internal value transfer.

[mattsse]

oh, I see

idk what https://etherscan.io/address/0x000f3df6d732807ef1319fb7b8bb8522d0beac02/ is exactly but this appears to be blob related, so mostlikely due to missing system EIP-4788 pre block system call this is causing the claim to fail.

integrating the systemcalls properly is currently missing

[grandizzy]

oh, I see

idk what https://etherscan.io/address/0x000f3df6d732807ef1319fb7b8bb8522d0beac02/ is exactly but this appears to be blob related, so mostlikely due to missing system EIP-4788 pre block system call this is causing the claim to fail.

integrating the systemcalls properly is currently missing

yeah, looks similar with #7938 the specified address is BEACON_ROOTS_ADDRESS https://eips.ethereum.org/EIPS/eip-4788#specification