Thanks @Strykar for your detailed comment.
We were able to reproduce the error you’re experiencing. While blocks are correctly handled by the Forge CLI inside tests that we primarily use, there seems to be a bug in the Anvil implementation that doesn’t account for the non-standard Arbitrum EVM implementation (which is supposed to return L1 blocks via block.number).
We reported this issue to Foundry here and they already fixed it via this PR and made a pre-release with the fix. We’ve confirmed that using this pre-release the block numbers are correctly incremented now, and does not cause any round jumps.
That said, to overcome this problem and play with the Reward Caller functionality we introduced, you could’ve also used the Type 5 testnet. We’ve tested that Tenderly doesn’t have this issue: an Arbitrum fork with one simulated transaction still returns the correct block and round number:
-
Newly created Tenderly testnet with one transaction that sets reward caller
-
You can verify the current round number via the following command:
cast call --rpc-url "https://virtual.arbitrum.eu.rpc.tenderly.co/f5e24409-a5bd-474c-b13c-80f746dff2ec" 0xdd6f56DcC28D3F5f27084381fE8Df634985cc39f 'currentRound()(uint256)' -
The command returns
4331round as expected
Please let us know if you still experience any issues. If it’s related to the Foundry tools, we recommend to report those issues directly to their GitHub, so it’s fixed even faster.