Conflicting contract addresses across networks

[jsoares]

Issue type

Bug

Have you reproduced the bug with the latest dev version?

Yes

Version

main

Custom code

No

OS platform and distribution

No response

Describe the issue

From Julian Gruber:

I don't know if this is a signal, but I just had an address conflict. I deployed a contract to alpha (which worked 🎉 ) and got an address that also exists on calibration (https://explorer.glif.io/address/0x0ce8d6d1c617fb0a3581d1767d205f40c57d4def/?network=calibrationnet). I deployed again and the new address doesn't exist there (https://explorer.glif.io/address/0x11ae382474ae9b57806df2e84f422ff4ebfbe8fa/?network=calibrationnet)

Repro steps

From Julian Gruber:

I've basically pointed a foundry project to the alpha RPC endpoint, and ran its deployment script. The project is https://github.com/Meridian-IE/impact-evaluator, the IPC PR https://github.com/Meridian-IE/impact-evaluator/pull/31/files.
@aminoacid
do you know how we can get the commands issued during deploy?

I hope it's not accidentally using the calibration endpoint somehow. Whenever I deploy now I get an actor already existing in calibration (eg https://explorer.glif.io/address/0x74e188de6696cb5d1ba31a50fee8cf5dcfb7e975/?network=calibrationnet)

Relevant log output

No response