feat: mainnet Euclid params

[Thegaram]

1. Purpose or design rationale of this PR

Embed Euclid parameters for the upcoming Euclid upgrade on Scroll mainnet.

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• feat: A new feature

3. Deployment tag versioning

Has the version in params/version.go been updated?

• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change

Summary by CodeRabbit

• New Features

  • Enhanced blockchain configuration with new timing parameters and system contract settings for optimized network performance.

• Chores

  • Incremented the patch version to mark the latest release.

[coderabbitai]

Walkthrough

This pull request updates the blockchain configuration files by adding new configuration parameters and refining existing ones. In params/config.go, it introduces new time-based settings (EuclidTime, EuclidV2Time), a SystemContract configuration structure, and additional fields in L1Config. In params/version.go, the VersionPatch constant is incremented from 30 to 31.

Changes

File(s)	Change Summary
params/config.go	Added new parameters in ScrollMainnetChainConfig and ScrollSepoliaChainConfig (i.e., EuclidTime, EuclidV2Time, SystemContract) and new fields in L1Config for message queue settings.
params/version.go	Incremented the VersionPatch constant from 30 to 31.

Possibly related PRs

• feat: address system contract consensus issues and comments #1126: The changes in the main PR are related to the introduction of new configuration parameters for the SystemContract, which aligns with the modifications in the retrieved PR that also involve the SystemContract structure and its methods.
• fix: correctly select consensus engine during EuclidV2 transition #1130: The changes in the main PR are related to the introduction of new configuration parameters that include timestamp handling, which aligns with the modifications in the retrieved PR that also focus on timestamp management during the consensus engine transition.
• fix: print Euclid genesis config on startup #1118: The changes in the main PR are related to the modifications of the EuclidTime and EuclidV2Time variables in the ScrollMainnetChainConfig and ScrollSepoliaChainConfig, which are also addressed in the retrieved PR that adds these fields to the ChainConfig struct.

Suggested reviewers

• colinlyguo
• omerfirmak

Poem

Hopping through bytes with a joyful beat,
I nibbled on changes crisp and neat.
New time fields and contracts in sight,
A version bump shines oh so bright.
Code carrots fuel my digital delight!
🐇💻

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 77683dd and 112c35e.

📒 Files selected for processing (1)

• params/version.go (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• params/version.go

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (go)

---

🪧 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>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Thegaram]

This will be ~1 month earlier than the upgrade time. This means that if they restart their node, it will always first resync from this block. It's a nuisance but I think syncing a few week's worth of L1 messages shouldn't take long.