Add a way to peer-validate deployment results #100
Description
Assuming that deployer engineer's machine was compromised, and modified the deployment routine/code which resulted in a malicious version being put onchain, another engineer should be able to independently run a simulation deployment (even without the access to a private key) that will confirm that onchain state is correct.
Implementation details
My initial idea is to add an env flag similar to that of dry run, that will perform everything on a fork, collect the state changes in the process, then compare final state with the chain. To not rely on archive state on the RPC, peer could do the simulation before the actual deployment, then deployer can do their simulation, and if everything matches proceed to the actual deployment.
Check if there are ready-made tools for this scenario.