[devnet] Mainnet fork shouldn't need to always redeploy #7531
Comments
This was referenced Jul 19, 2024
PhilWindle
pushed a commit
that referenced
this issue
Jul 22, 2024
Fixes #7277 Fixes #7477 This PR adds a bootstrapping job to the automatic devnet deployments which: - Creates an account which is used to: - Deploy canonical contracts `AuthRegistry`, `KeyRegistry` & `GasToken` (soon to be fee juice) - Deploy 2 contracts, `TokenContract` (named `DEV`) and an `FPCContract` for DEV. - Updates 2 S3 buckets with the addresses of the deployed contracts (L1 & L2) Other changes: - L1 contracts now re-deploy by default. #7530 - Mainnet fork also deploys by default as I ran into some issues #7531
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While testing CI by pushing on
devnetit seems sometimes deploying contracts failed if the mainnet fork hadn't also re-deployed.This should really be the case since we deploy new L1 contracts before re-deploying nodes, therefore having a clean slate.
The error was
DB has no contract with address 0x05425591680496cbc66f87c6e2a7669f253c205e4487e2046e72a6d8a74aa73bwhen trying to runaztec bootstrapThe text was updated successfully, but these errors were encountered: