The deploy commands (and associated commands) need changes for the upcoming L2 phase c release. However, it has become a bit bloated and out of control. It could use some refactoring to be more stable and easy to maintain, while we introduce these necessary features.
[x] Protect against the possibility of deploying the wrong compilation artifacts in an OVM/non-OVM network
DONE Test what happens when we deploy ovm artifacts in a fork of mainnet - results are inconclusive: ovm in mainnet reverts with no reason when attempting to deploy any contract, mainnet in ovm deploys some contracts, but fails when doing some mutative function calls.
MERGED Consider checking metadata, or some sort of watermark for OVM bytecode - PR: Deploy
script checks compiled contracts expected compiler version #822 Optimism released alpha 4 of the compiler, which contains "ovm" in the compiler version. This PR can be updated to look for that, instead of hardcoding a version.
[x] (@zyzek) Split Issuer so that it can be compiled for OVM
Rationale
The deploy commands (and associated commands) need changes for the upcoming L2 phase c release. However, it has become a bit bloated and out of control. It could use some refactoring to be more stable and easy to maintain, while we introduce these necessary features.
Changes
ovm-ignored.json.