bug(`cast`): `cast run` does not work sometimes with weird errors (lack of funds, nonce too low, etc.)

[0xDEnYO]

Component

Forge, Cast

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

• Foundry
• Foundryup

What version of Foundry are you on?

forge Version: 1.2.3-stable

What version of Foundryup are you on?

foundryup: 0.3.3

What command(s) is the bug in?

Cast run

Operating System

macOS (Apple Silicon)

Describe the bug

Sometimes when I run cast run I do not get any stack trace.
Here is one example:

Case 1:
cast run 0xe5dff9c3f5ec5b1af5f641f1c1f1829b38713641b4401b2affeaf794d7b48e0b --rpc-url https://zksync2-mainnet.zksync.io -vvv

Explorer URL 1:
https://era.zksync.network/tx/0xe5dff9c3f5ec5b1af5f641f1c1f1829b38713641b4401b2affeaf794d7b48e0b
Explorer URL 2:
https://explorer.zksync.io/tx/0xe5dff9c3f5ec5b1af5f641f1c1f1829b38713641b4401b2affeaf794d7b48e0b
(in this explorer we get some data back that helps to extract the revert reason)
Also Phalcon is able to produce a full stack trace:
https://app.blocksec.com/explorer/tx/zksync-era/0xe5dff9c3f5ec5b1af5f641f1c1f1829b38713641b4401b2affeaf794d7b48e0b

This transaction uses a precompile which in Telegram was pointed out could be an issue. Is there a way this could be improved so that also those stack traces are shown?

---

Case 2:
Here is a second transaction that does not work:

cast run 0x715e633fc1ae98bfda07a52b11758acb9bd5bf73cd4c386708e694ec42da5924 --rpc-url https://rpc.hyperliquid.xyz/evm -vvv

Explorer URL:
https://www.hyperscan.com/tx/0x715e633fc1ae98bfda07a52b11758acb9bd5bf73cd4c386708e694ec42da5924

This one is more difficult to debug since HyperEVM is not supported by Tenderly or Phalcon which is why I would love to see a full stack trace for it.
But using cast run we get a nonce too low error (that i've seen a few times before):

adding the flag --trace-printer also does not yield any more output.

Is this a bug? Can this be improved somehow?

[0xDEnYO]

I have another funny one:

cast run "0x6f23146056354c0b2a3b982e2f03bbadf8eece0364c5b8be4db1a0ec987f7af4" --rpc-url 'https://1rpc.io/cro' -vvv

This one prints a stack trace that shows no error while both block explorers show that an error occurred:
Block Explorer 1:
https://cronoscan.com/tx/0x6f23146056354c0b2a3b982e2f03bbadf8eece0364c5b8be4db1a0ec987f7af4
Block Explorer 2:
https://explorer.cronos.org/tx/0x6f23146056354c0b2a3b982e2f03bbadf8eece0364c5b8be4db1a0ec987f7af4

[DeadmanXXXII]

Testing this out on Android ATM using a headless nethunter.
So far so good it built ran and executed flawlessly:

https://youtube.com/shorts/v_j01heevio?si=Su-qEw04aY2AQt7j

I'll let you know if anything needs patched specifically for Android.
Tbf I have only ran one cute wee test with a small smart contract fuzz but got good results.

[mattsse]

most likely this has something to do with different evm implementations and rewards etc.

maybe we should disable balance checks for certain networks

[grandizzy]

confirming the hyperliquid one works OK in nightly builds
cast run 0x715e633fc1ae98bfda07a52b11758acb9bd5bf73cd4c386708e694ec42da5924 --rpc-url https://rpc.hyperliquid.xyz/evm -vvv

[grandizzy]

@0xDEnYO would you be able to provide tenderly links for
cast run 0xe5dff9c3f5ec5b1af5f641f1c1f1829b38713641b4401b2affeaf794d7b48e0b --rpc-url https://zksync2-mainnet.zksync.io -vvv
and
cast run "0x6f23146056354c0b2a3b982e2f03bbadf8eece0364c5b8be4db1a0ec987f7af4" --rpc-url 'https://1rpc.io/cro' -vvv
to check the differences? Pretty sure due to precompiles as in #7514 but needs confirmation

[0xDEnYO]

@grandizzy

1. zksync: https://www.tdly.co/tx/0xe5dff9c3f5ec5b1af5f641f1c1f1829b38713641b4401b2affeaf794d7b48e0b
2. Tenderly does not find that transaction :/

edit: tenderly doesnt support cronos at all