feat(forge script): add flag to output --standard-json-input somewhere

[bxmmm1]

Component

Forge

Describe the feature you would like

When a script deoloys contracts to 2 different chains (Mainnet, Base) Etherscan & BaseScan don't use the same API key, so the contract verification fails with --verify

It would be convenient, to store the standard json output somewhere for all deployed contracts. That way, it is easy to manually drag & drop it on Etherscan,Basescan to verify the contracts.

Additional context

No response

[mattsse]

we have

  --show-standard-json-input
      Prints the standard json compiler input.
      The standard json compiler input can be used to manually submit contract verification in the browser.

on verify-contract, so we should be able to also include this in the script command easily

[bxmmm1]

we have

  --show-standard-json-input
      Prints the standard json compiler input.
      The standard json compiler input can be used to manually submit contract verification in the browser.

on verify-contract, so we should be able to also include this in the script command easily

Yes, but that only works with forge create, right?

[CodeSandwich]

Yes, but that only works with forge create, right?

It seems that no, I was able to run forge verify-contract --show-standard-json-input $(cast address-zero) MyContract and it did nothing but printing the standard input JSON. It didn't even complain that the Etherscan API key wasn't provided, it was like running a completely different command that only prints the standard input JSON. I wish that it actually was a separate command or a forge inspect output, I would have never guessed to look at one of forge verify-contract flags if it wasn't mentioned it in this issue. Thanks!

[grandizzy]

@CodeSandwich we're going to add better documentation for the flag.

[CodeSandwich]

Awesome! IMO making it a separate command or a feature of a more obvious command like forge inspect or forge build would be the actual low discoverability solution, but having one more place where it's documented is certainly a good step 👍

[bxmmm1]

Update: Etherscan V2 started using the same API Key for everything 🥇

https://docs.etherscan.io/etherscan-v2#single-api-key

[grandizzy]

Update: Etherscan V2 started using the same API Key for everything 🥇

Yep, tracking impl in foundry-rs/foundry#9196