Skip to content

Conversation

smartcontracts
Copy link
Contributor

Adds a new script that can be used to check the result of running the interop migration. Script was originally added to OPCM but because there's no dedicated U17 OPCM.

Adds a new script that can be used to check the result of running
the interop migration. Script was originally added to OPCM but
because there's no dedicated U17 OPCM.
@smartcontracts smartcontracts requested review from a team as code owners May 29, 2025 17:34
@smartcontracts smartcontracts requested a review from Inphi May 29, 2025 17:34
'@openzeppelin/contracts/=lib/openzeppelin-contracts/contracts',
'@base-contracts/=lib/base-contracts/',
'@eth-optimism-bedrock/=lib/optimism/packages/contracts-bedrock/',
'@op/=lib/optimism/packages/contracts-bedrock/',
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: an @eth-optimism-bedrock monorepo mapping already exists. Let's use that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I added it because eth-optimism-bedrock is so unnecessarily long lol

/// @notice Checks that the interop migration correctly performed basic migration steps.
/// This script is used to verify that the migration was successful and that the
/// contracts were correctly updated.
contract CheckMigrate is Script {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is the intended use to inherit from this in the template task that calls opcm.migrate and then call the run method? If so, maybe we just scaffold out that task template instead and inline this directly into the validation method

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sort of, the reason it isn't being used like that is so that we can use this script when we run devnets that don't use superchain-ops tasks

Copy link
Contributor

Choose a reason for hiding this comment

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

Got it, a nit, but can we just add some natspec to make the expected usages of this script (devnet vs. superchain-ops task) self-documenting?

jcortejoso pushed a commit to celo-org/superchain-ops that referenced this pull request Jun 11, 2025
…ethereum-optimism#1037)

* Enhance CircleCI configuration with new executor and notification job

- Added a default executor using Ubuntu 22.04 with medium resource class.
- Introduced a new job to notify when chains are added to the registry, including logic to detect new chain configurations and report them.

* Branch from test branch (ethereum-optimism#1038)

* Add arena-z chain configuration

- Introduced a new TOML configuration file for the arena-z chain, including details such as public RPC, sequencer RPC, explorer URL, chain ID, and various parameters related to hard forks, genesis, roles, and addresses.
- This configuration supports the deployment and management of the arena-z chain within the superchain ecosystem.

* Enhance CircleCI configuration to include branch check and updated file detection logic

- Added a step to check if the current branch matches the specified branch before proceeding with notifications.
- Updated the logic to detect newly added TOML files by comparing the most recent commit on the main branch instead of the previous branch.

* Branch from test branch 2 (ethereum-optimism#1039)

* Add arena-z chain configuration

- Introduced a new TOML configuration file for the arena-z chain, including details such as public RPC, sequencer RPC, explorer URL, chain ID, and various parameters related to hard forks, genesis, roles, and addresses.
- This configuration supports the deployment and management of the arena-z chain within the superchain ecosystem.

* Enhance CircleCI configuration to include branch check and updated file detection logic

- Added a step to check if the current branch matches the specified branch before proceeding with notifications.
- Updated the logic to detect newly added TOML files by comparing the most recent commit on the main branch instead of the previous branch.

* Enhance CircleCI configuration for Slack notifications and chain detection

- Added a new parameter for Slack webhook URL to facilitate notifications.
- Updated the branch check to be more generic, allowing notifications for any target branch.
- Improved logic for detecting newly added chains and formatted Slack messages for better clarity.
- Introduced a new job to send notifications when chains are added to the registry.

* Remove arena-z chain configuration file from mainnet configs

* Remove arena-z chain configuration files from mainnet configs

* Fix CircleCI Slack notification command syntax by correcting the webhook URL parameter usage.

* Enhance CircleCI configuration to improve Slack notifications for chain changes. Updated logic to detect added, deleted, and modified chains in the registry, and formatted messages for clarity. Adjusted notification conditions to ensure messages are sent only when changes are detected.

* test

* test

* test

* test

* test

* test

* test

* Update CircleCI configuration to add branch filters for the notify job, restricting notifications to the 'test-branch' only.

* Update CircleCI configuration to change default branch from 'test-branch' to 'main' and adjust notification filters accordingly.
@blmalone
Copy link
Contributor

@smartcontracts is this something we will want to merge? If it's nearly over the line, I'm happy to review.

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.

4 participants