Matt Solomon

Thanks for the clarification. So: - The existing `evm_version` should only affect solc configuration, not forge's execution environment. - When forge has an RPC URL (either during tests after selecting...

@Evalir Could you get a bit more concrete on describing the new behavior, e.g. if I use any `target*` does that prohibit new contracts from being added, and if I...

Maybe the simplest solution here is to have a global default for whether or not to add new contracts during a run. This would apply regardless of how you setup...

To that point, on second thought, maybe a better UX here is ditch my config flag idea and just add a new contract getter method, `contractsToAdd`. This would return the...

Another approach to this could be to use the standard JSON RPC batching—not all providers support this, and it also doesn’t result in reduced RPC usage, but it can still...

Another approach: assuming the RPC URL supports state overrides (like geth does), use Dedaub's storage extractor code to batch `eth_getStorageAt`: https://github.com/Dedaub/storage-extractor

Are you specifically referring to [ERC-3770](https://eips.ethereum.org/EIPS/eip-3770)? If so, that's a nice idea—instead of using the `--chain` or `--rpc-url` flag for commands, support ERC-3770 syntax and automatically change the env var...

I think this could be useful and is worth discussing, so going to reopen. For context, a lit of short name prefixes is maintained in https://github.com/ethereum-lists/chains I keep a ton...

That's a really nice idea. Addresses often also need to be chain specific, so we might need to expand that second example to something like `cast config add address dai...

Is the feature request here to have `vm.writeFile` automatically create the directory if it doesn't exist, or to add a `vm.mkdir` cheat to create directories? Both seem reasonable to me,...