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

new chain: camp network testnet #899

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

anirudhmakhana
Copy link
Contributor

Adding a New Chain

This PR adds Camp network testnet to the registry.

Checklist

  • [x ] I have declared the chain at the appropriate Superchain Level.
  • [ x] I have run just codegen to ensure that all generated files are created.
  • [x ] I have run just codegen to ensure that the chainlist and other generated files are up-to-date and include my chain.
  • [ x] I have checked Allow edits from maintainers on this PR.

@anirudhmakhana anirudhmakhana requested a review from a team as a code owner February 15, 2025 13:17
@Wazabie Wazabie self-assigned this Feb 18, 2025
@Wazabie Wazabie added M-new-chain-request Meta: New Chain Request F-do-not-merge Flag: Do Not Merge labels Feb 18, 2025
@mslipper
Copy link
Contributor

After fixing some minor issues with your chain config and reviewing the contract deployment transactions, it appears like you used the legacy deployment script rather than OP Deployer. If this is the case, you will have to use an alternative means to verify your chain before adding it to the registry. If you did use OP Deployer, can you please correct the deployment_tx_hash value in your config to point to the correct transaction?

@Wazabie
Copy link
Collaborator

Wazabie commented Feb 27, 2025

After fixing some minor issues with your chain config and reviewing the contract deployment transactions, it appears like you used the legacy deployment script rather than OP Deployer. If this is the case, you will have to use an alternative means to verify your chain before adding it to the registry. If you did use OP Deployer, can you please correct the deployment_tx_hash value in your config to point to the correct transaction?

I don't think this was deployed with op-deployer actually, there is this other PR for Camp . Can we use this one to validate or we need @anirudhmakhana to open another?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F-do-not-merge Flag: Do Not Merge M-new-chain-request Meta: New Chain Request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants