Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add support for op-deployer, fix multiple L2s #74

Merged
merged 24 commits into from
Sep 25, 2024

Conversation

mslipper
Copy link
Collaborator

@mslipper mslipper commented Sep 20, 2024

@mslipper mslipper force-pushed the feat/op-deployer-support branch from 56c9895 to d5ce592 Compare September 20, 2024 21:18
@mslipper mslipper changed the title Add support for op-deployer, fix multiple L2s feat: Add support for op-deployer, fix multiple L2s Sep 20, 2024
@mslipper mslipper marked this pull request as ready for review September 21, 2024 05:05
@barnabasbusa
Copy link
Contributor

From a very quick look, it seems like "manual deployment" of the contract is no longer possible.
I might presume incorrectly but don't you ever wanna check that the manual contract deployment still working as expected? I understand that you would default to a contract being part of the genesis file, but feel like if you disable the functionality on contract deployment altogether then it's also going to be one more thing to test in case there is a change on L1.

@mslipper
Copy link
Collaborator Author

mslipper commented Sep 23, 2024

Hey! I'm not sure what you mean by manual deployment of the contracts. The contracts are deployed using regular transactions to the L1 in the enclave, they're just all deployed upfront before spinning up the L2s. They're not injected into the L1's genesis file.

src/package_io/input_parser.star Outdated Show resolved Hide resolved
src/wait/wait_for_sync.star Outdated Show resolved Hide resolved
src/package_io/sanity_check.star Show resolved Hide resolved
src/participant_network.star Show resolved Hide resolved
@barnabasbusa barnabasbusa enabled auto-merge (squash) September 25, 2024 19:15
@barnabasbusa barnabasbusa linked an issue Sep 25, 2024 that may be closed by this pull request
@mslipper mslipper force-pushed the feat/op-deployer-support branch from dadcda6 to f44e404 Compare September 25, 2024 19:24
@barnabasbusa barnabasbusa merged commit eb59380 into main Sep 25, 2024
5 checks passed
@barnabasbusa barnabasbusa deleted the feat/op-deployer-support branch September 25, 2024 19:28
barnabasbusa added a commit that referenced this pull request Nov 22, 2024
🤖 I have created a release *beep* *boop*
---


##
[1.1.0](1.0.0...1.1.0)
(2024-11-21)


### Features

* add additional configuration options for participants
([#81](#81))
([05d0fe9](05d0fe9))
* add custom configurable forks
([#59](#59))
([878906a](878906a))
* add hildr
([#42](#42))
([e1ce08e](e1ce08e))
* add k8s tests
([#45](#45))
([168f062](168f062))
* add op_contract_deployer_params/image
([#63](#63))
([9416a86](9416a86))
* add op-besu
([#58](#58))
([08e7548](08e7548))
* add op-erigon - mininny
([#38](#38))
([c69bf34](c69bf34))
* add sanity check
([#50](#50))
([ceaa9a9](ceaa9a9))
* Add support for op-deployer, fix multiple L2s
([#74](#74))
([eb59380](eb59380))
* add version.txt
([#36](#36))
([1d10311](1d10311))
* add wait for sync for non kurtosis chains
([#49](#49))
([0452e11](0452e11))
* Adding op-nethermind
([#46](#46))
([fba71dd](fba71dd))
* op-deployer upgrade, fix fork support
([#88](#88))
([f8d9089](f8d9089))
* Output Admin Private Key
([#71](#71))
([95abc10](95abc10))


### Bug Fixes

* ci jobs only notify if discord secret available
([#48](#48))
([9473f89](9473f89))
* contract string
([#82](#82))
([c062de0](c062de0))
* count for participant was not calculated with
([#89](#89))
([f511988](f511988))
* DNS-1035 label
([#44](#44))
([1bf8541](1bf8541))
* erigon perms issue
([#76](#76))
([0328314](0328314))
* explicitly set client contexts0
([30017f2](30017f2))
* force offset time to be int
([#64](#64))
([74b6417](74b6417))
* github action should fail if any jobs fail
([#78](#78))
([577ca3b](577ca3b))
* grammar in docs
([#33](#33))
([d6fb36f](d6fb36f))
* handling of config options
([#85](#85))
([5b085c8](5b085c8))
* image label name too long, truncate at 63 chars
([#90](#90))
([5bd687c](5bd687c))
* l2 contract deployment
([#35](#35))
([3f2b16d](3f2b16d))
* Provide default participants
([#77](#77))
([a7d72da](a7d72da))
* Remove wait for finalization for create2 factory deployment
([#60](#60))
([d4c37f0](d4c37f0))
* test k8s
([#47](#47))
([ac17e89](ac17e89))
* trust l1 rpc in op-node
([#41](#41))
([05dcd2e](05dcd2e))
* Update neth image; improve genesis tool
([#73](#73))
([71e61c8](71e61c8))
* update op-geth hash based storage
([#61](#61))
([f0b5b23](f0b5b23))
* Validate root params
([#79](#79))
([914a808](914a808))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: Barnabas Busa <barnabas.busa@ethereum.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deploying L2 contracts is super slow and makes for bad devex
2 participants