Mark Tyneway

> 2. add bespoke logic for each L2, determined by chainId, this will need to be fork-aware when #1715 is merged For accurate fee estimation on Optimism, the L2 (execution)...

There is a pending `StateDB` in geth that transactions from the mempool are applied against, it prevents transactions with the same nonce from entering the mempool unless its a replace...

I feel like `mineSalt` could be a library that wraps `cast` with this functionality

I think that this would be very useful for parsing addresses out of deployment artifacts for chainops. A network could be configured and then the corresponding addresses could be read...

I was thinking of implementing this as part of https://github.com/foundry-rs/hardhat A hardhat task that wraps `forge script` and then it would generate the hardhat deploy style artifacts. The idea is...

> SGTM re: Checksumming. You may also be interested in forge fmt which will auto-checksum everything for you. Would like to try out `forge fmt` but we currently use `prettier`...

Definitely +1 for @mds1 `cast storage ` proposal, I think it would also be cool to have a `--blocknumber` param that lets you do historical queries so that you can...

I have a slight preference of this being implemented in `cast` and then writing a simple solidity library that wraps `cast` with `ffi` instead of adding an additional cheatcode here

I have observed hardhat not requiring the content type header, are you sure that geth works without it? I've observed geth not working without `Content-Type: application/json`. It seems like bad...

This PR is very useful, anything that I can do to help get it over the line?