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: op stack integration #418

Merged
merged 39 commits into from
Dec 30, 2024
Merged

Conversation

leovct
Copy link
Member

@leovct leovct commented Dec 5, 2024

Status

  • Integrate the OP package into our kurtosis package (not connected to the AggLayer).
  • Test that it works well and implement a new CI check to monitor the state of the OP Stack rollup.
  • Review the PR.
  • Wait for the OP package to release v1.2.0 and migrate to this version to merge the PR.

Description

The goal is to add a new option to deploy an OP stack rollup inside our package.

To deploy the default OP stack rollup, you can use:

deployment_stages:
  deploy_optimism_rollup: true

You can also customize the rollup:

deployment_stages:
  deploy_optimism_rollup: true

optimism_package:
  chains:
    - participants:
      - el_type: op-geth
        cl_type: op-node
      - el_type: op-reth
      - el_type: op-erigon
      - el_type: op-nethermind

References (if applicable)

@leovct leovct changed the title fat: op stack integration feat: op stack integration Dec 5, 2024
@leovct leovct marked this pull request as ready for review December 5, 2024 12:53
@leovct leovct requested a review from a team December 5, 2024 13:05
Copy link
Collaborator

@jhkimqd jhkimqd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can see the finalized_l2 number incrementing when running this setup. It seems like the OP components are working and the op-batcher is correctly sending sequenced batches to L1 for verification.
image

ethereum.star Outdated Show resolved Hide resolved
@leovct
Copy link
Member Author

leovct commented Dec 6, 2024

I can see the finalized_l2 number incrementing when running this setup. It seems like the OP components are working and the op-batcher is correctly sending sequenced batches to L1 for verification. image

Cool, thanks for checking this. By the way, I added a new monitor for OP rollups to check if L2 blocks are finalized after some time.

Screenshot 2024-12-06 at 13 04 54

https://github.com/0xPolygon/kurtosis-cdk/actions/runs/12197982923/job/34028778002?pr=418

main.star Outdated Show resolved Hide resolved
@leovct leovct requested a review from jhkimqd December 17, 2024 16:04
Copy link
Collaborator

@jhkimqd jhkimqd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested the deployment by setting "deploy_optimism_rollup": True, and it seems to be working without issues. But when testing with different combinations of DEFAULT_DEPLOYMENT_STAGES input, there were some combinations which resulted in errors during deployment - this may not be the intended way to use it, so just raising for awareness.

image

main.star Show resolved Hide resolved
@leovct leovct enabled auto-merge (squash) December 30, 2024 08:08
@leovct leovct merged commit 2edcc2f into 0xPolygon:main Dec 30, 2024
26 of 27 checks passed
@leovct leovct deleted the feat/op-stack-integration branch December 30, 2024 08:16
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.

2 participants