vm.nonce is not updated in contract calls.

[ivan-onchain]

Based on this issue in the foundry repo looks like the nonce of an address is only updated if that address is used to deploy a contract but not for calling functions

foundry-rs/foundry#8584

Therefore challenges like ThePuppet can't be finished as the player doesn't deploy any contract but the required nonce has to be one.

[matiasanaya]

See also foundry-rs/foundry#8811

[tinchoabbate]

Thanks for reporting. Yes I'm aware of this behavior, it's being discussed here: #57. I don't seem to be able to do anything about it from my side, we've gotta wait for the Foundry folks to fix.

[CanonicalJP]

The workaround proposed by Foundry is to use the --isolated option to make each tx be executed in a separate EVM context. It looks like that option was not working properly either, solved in foundry-rs/foundry#8878

On the other hand, I created #77 so that the option is included in the Usage section of the README

[tinchoabbate]

will include in the next minor release the change in the README. Thanks everyone.