feat: enable Canyon for Kroma mainnet

[0xHansLee]

Enables Canyon upgrade for Kroma mainnet.

• Canyon activation time: 1708502400 (Wed Feb 21 2024 08:00:00 UTC).

Summary by CodeRabbit

• Refactor
  • Updated the CanyonTime field within the blockchain configuration to have specific values for mainnet and testnet environments, enhancing network specificity and reliability.

[coderabbitai]

Walkthrough

This update focuses on the superchain.go file, specifically refining the KromaChainConfig struct. The modification entails assigning concrete uint64 values to the CanyonTime field for both KromaMainnetChainID and KromaSepoliaChainID, moving away from the previous nil assignments. This change ensures more precise and defined configurations for these chain IDs within the system.

Changes

File(s)	Change Summary
.../superchain.go	Updated CanyonTime in KromaChainConfig with specific uint64 values for KromaMainnetChainID and KromaSepoliaChainID.

🐰✨

In the code where bits and bytes play,

A rabbit hopped, making changes today.

No more nil, clarity's the plan,

For KromaMainnet and Sepolia's span.

Through the digital fields, it leaps and bounds,

In superchain.go, progress resounds. 🎉

🌟🐇

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between f1ffda2 and bec52d5.

Files selected for processing (1)

• params/superchain.go (1 hunks)

Additional comments: 4

params/superchain.go (4)

• 21-21: The assignment to CanyonTime uses uint64ptr(1708502400), which is correct but ensure uint64ptr function handles potential overflow or underflow scenarios gracefully.
• 21-21: Verify the necessity and safety of using pointers for CanyonTime to avoid potential null pointer dereferences.
• 21-21: The logic in LoadKromaChainConfig correctly uses CanyonTime for both ShanghaiTime and CanyonTime in ChainConfig, aligning with the PR objectives.
• 21-21: The PR mentions updates to CanyonTime for KromaMainnetChainID and KromaSepoliaChainID, but the code also updates KromaDevnetChainID. Verify if this change is intentional.

[seolaoh]

LGTM