feat: schedule Galileo on Scroll Sepolia

[Thegaram]

1. Purpose or design rationale of this PR

Schedule the Galileo upgrade on Scroll Sepolia at Unix timestamp 1764054000 (see here for time zone conversions).

Release notes draft: https://gist.github.com/Thegaram/df724b248c56c65b779440a8faa1dc55

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?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change
• Yes

Summary by CodeRabbit

• Chores
  • Product patch version bumped (12 → 13), updating the reported product version strings and archives.
  • Scroll Sepolia chain configuration augmented with a new fork-time field to influence Sepolia network behavior.

[coderabbitai]

Walkthrough

Adds a Galileo fork activation timestamp to the ScrollSepoliaChainConfig literal and increments the package patch version from 12 to 13 in params.

Changes

Cohort / File(s)	Summary
Configuration update params/config.go	Added GalileoTime field initialization to the ScrollSepoliaChainConfig composite literal to specify Galileo fork activation.
Version bump params/version.go	Incremented VersionPatch from 12 to 13, updating computed version strings and derived constants.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer (PR)
    participant Params as params package
    participant ChainRules as Chain rules at runtime

    Note over Dev,Params `#D6EAF8`: Code change
    Dev->>Params: Add `GalileoTime` to `ScrollSepoliaChainConfig`
    Dev->>Params: Bump `VersionPatch` to 13

    Note over Params,ChainRules `#F9E79F`: Runtime effect
    Params->>ChainRules: Provide chain config (includes GalileoTime)
    ChainRules->>ChainRules: Evaluate IsGalileo(currentTime) using GalileoTime
    alt Galileo active
        ChainRules->>ChainRules: Enable Galileo-specific behavior (precompile/features)
    else Galileo inactive
        ChainRules->>ChainRules: Keep pre-Galileo behavior
    end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Focus review: verify correct placement/format of GalileoTime in params/config.go and consistency of version-derived strings/paths in params/version.go.

Possibly related PRs

• feat: schedule Feynman upgrade on Scroll Sepolia #1222 — Also modifies ScrollSepoliaChainConfig to set a fork activation time and touches similar config fields.
• feat: Galileo rollup fee #1251 — Also bumps VersionPatch in params/version.go.
• feat: schedule Feynman upgrade on Scroll mainnet #1230 — Adds activation timestamps to chain config literals and increments VersionPatch.

Suggested labels

bump-version

Suggested reviewers

• roynalnaruto
• georgehao
• jonastheis

Poem

🐰 I hopped through code with tiny paws,
A timestamp placed without a pause.
Galileo set to wake and play,
Patch bumped up to mark the day.
Sniff, nibble, build — hooray! 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'feat: schedule Galileo on Scroll Sepolia' directly aligns with the main changes: adding GalileoTime initialization to ScrollSepoliaChainConfig and bumping the version for deployment.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The pull request description follows the required template with all main sections completed: purpose/design rationale is clear, PR title type (feat) is selected, version update is confirmed, and breaking change status is specified.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat-galileo-sepolia

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}