meta: multi-chain deployment experience

[0xrusowsky]

List of issues related to the multi-chain (or single chain) deployment dev-ex:

• Cumbersome to manage deployment vars with ffi + json/toml cheatcodes
• Manual management of fork ids (which don't match the chain ids)
• tracking: default to CreateX for CREATE2/3 factory for new scripts #2638
• feat(config): add chain dependent solc config and support in multichain scripts #9840
• tracking: add asynchronous runtime to forge script cheatcodes #10986

Ongoing work:

• will tackle the first 2 items: feat: config helper contract forge-std#715

[mablr]

Maybe related ? #11067

[aviggiano]

This is also a bottleneck to safe scripting with Ledger: #10281

[0xrusowsky]

This is also a bottleneck to safe scripting with Ledger: #10281

yes, we have that in mind! but that will require its own dedicated workstream (planned for v1.5): #10986

will also link it, thanks for bringing it up here

[sakulstra]

Just so it does not get forgotten:

• solc setting dependent caching
• inability to switch evm_version, dependent on chain / within a script

are still big issues for multichain scripting.