chore: Modify logs from rollkit-reth to ev-reth

[Manav-Aggarwal]

Description

Simple change to move logs from rollkit-reth to ev-reth

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Performance improvement
• Refactoring

Related Issues

Fixes #(issue)

Checklist

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Testing

Additional Notes

[gemini-code-assist]

Summary of Changes

Hello @Manav-Aggarwal, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is a chore/refactoring change focused on updating log messages within the ev-reth node. The primary purpose is to align the logging output with a new naming convention, transitioning from 'Rollkit-Reth' to 'EV-Reth' and related terms, ensuring consistency in the application's runtime feedback.

Highlights

• Log Message Updates: Updated various informational log messages to replace references from 'Rollkit-Reth' and 'Rollkit' with 'EV-Reth' and 'EV-node' respectively, reflecting a branding or naming change.
• Payload Builder Naming: Adjusted a log message to refer to the 'ev-reth payload builder' instead of the 'rollkit payload builder', aligning with the new naming convention.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to update log messages by replacing 'Rollkit' with 'ev-reth'. While the intent is clear, some of the changes introduce inconsistencies between the log output and the underlying code identifiers (e.g., struct and variable names), which can be misleading. My review provides suggestions to correct these inconsistencies to ensure the logs accurately reflect the system's components, while still achieving the goal of updating the overall branding.

[gemini-code-assist]

This log message is now inconsistent with the code. The mode is determined by RollkitArgs (see line 162), so logging it as 'EV-node mode' is misleading.

To maintain consistency while updating the branding, please keep the component name as 'Rollkit mode'. A more thorough refactoring of all Rollkit identifiers would be ideal, but if that's out of scope for this PR, we should at least keep logs consistent with the code to avoid confusion.

            info!("=== EV-RETH: Rollkit mode enabled ===");