L2 genesis generation w/ predeploy

[LEAFERx]

Goals of PR

Core changes:

• Updated magi to the latest develop branch
• Introduce a new genesis generation tool that can set up predeploys and proxies at the genesis block
  • Adapted from Optimism's op-bindings and op-chain-ops packages
  • ops/bindings: Predeploy and proxy contract bindings generation with deployed bytecode and storage layout
  • ops/cmd/genesis: Introduce a new command which reads a GenesisConfig (see ops/genesis/config.go) and generate a geth genesis file by deploying predeploys on a simulated backend and transform deployment information into genesis file.
• Minor contracts/code clean-up

TODOs:

• Update scripts to use this new tool
• Clean up READMEs, comments and make proper attributions to Optimism
• Fix forge tests due to use of predeploy addresses in contracts

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0523dd5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[MoonShiesty]

looks good. optimism creates the deployment artifacts for the L1 and L2 contracts with solidity, is this a follow-up we'd want to implement?

https://github.com/ethereum-optimism/optimism/blob/98ee7d5dbe82c0199b4e4201d49020a6a3ebf1f0/packages/contracts-bedrock/scripts/Deploy.s.sol

[chalkandpaste]

Lightly reviewed the OP code, but everything else LGTM. Let me know if you want me to look in more detail at the OPs code.

[LEAFERx]

looks good. optimism creates the deployment artifacts for the L1 and L2 contracts with solidity, is this a follow-up we'd want to implement?

https://github.com/ethereum-optimism/optimism/blob/98ee7d5dbe82c0199b4e4201d49020a6a3ebf1f0/packages/contracts-bedrock/scripts/Deploy.s.sol

Yes ideally we want to shift most complex bash scripts to golang/python and consolidate all configurations/deployment in one program

[ujvl]

can we move ops into either services or lib (whichever is more appropriate) -- want to try keeping the root dir minimal

[ujvl]

nit: whats the ! and is this file not covered by the ignored path above