Ethereum

Does any Foundry Chad know why msg.sender sometimes is the DefaultSender and sometimes the default anvil address when not passing a private key or using cast wallet?

Would have saved me 2 days to just use cast wallet for all transactions instead of figuring out the defaults when testing.

Would love for that to be in the foundry docs and never see raw commands without --account or the default accounts private key as --private-key

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

⭐️ Product @ethereum

📊 AI Engineer | 🇮🇱🇺🇸
/marissa

dang, yeah that's what tripped me up. Thank you!

forge script and cast have different defaults for who sends a transaction if you don’t explicitly specify a sender. 

If you don't set --private-key or use cast wallet, cast defaults to the first Anvil account, while forge script often uses a placeholder called DefaultSender unless you manually prank a sender. That mismatch can cause msg.sender to behave unexpectedly, especially in scripts.

Building /veil - ZK Privacy Protocol for Base

this was script related. I had msg.sender everywhere to account for what I do on the CLI but it still mixed that up somehow with 2 different ones in there. passing the flag explicitly got it to run consistenly

When testing just Prank as the default wallet when you have a msg.sender check. 

Your script can handle wallets. You don’t need to input them into the CLI.