feat(validator): implement validator client and fix actions test

[sm-stack]

Description

Implemented handling logics at kroma-validator client, and fixed the relevant actions test at op-e2e. Adding the commands for validators and system test for the new validator client will be handled with the following PRs.

For proper testing, GovernanceToken is changed. Ownable at GovernanceToken is temporarily removed to allow minting the tokens inside the test code and check the behavior of validator client, after the successful transition to new validator system. This must be fixed after PR #269 is merged.

Also, this PR includes an addition of flags that is needed to run devnet.

This PR must be merged after PR #269 and #277 are merged into dev.

[coderabbitai]

Important

Auto Review Skipped

Auto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The recent updates focus on enhancing the functionality and interaction of validator contracts within the Kroma ecosystem. Key changes include the introduction of new initialization functions, modifications to contract deployment and management, and updates to testing and configuration settings. Notably, the governance token's structure was altered by removing inheritance traits and updating permissions, which aligns with broader changes in contract management and challenge creation capabilities.

Changes

File Path	Changes
kroma-bindings/bindings/...	Added init() functions and new variables across multiple bindings for better initialization and data handling.
kroma-chain-ops/genesis/config.go	Removed _owner field for GovernanceToken in configuration function.
kroma-validator/...	Enhanced validator functionalities with new fields, updated contract interactions, and added logic for challenge management.
op-e2e/actions/...	Updated validator and challenger actions and tests to align with new contract functionalities.
packages/contracts/contracts/governance/GovernanceToken.sol packages/contracts/contracts/test/GovernanceToken.t.sol	Updated governance token functionalities and test assertions; removed Ownable inheritance.
packages/contracts/deploy/L1/...	Updated deployment scripts for GovernanceToken and related proxies, reflecting new contract structures and address handling.
packages/contracts/.gas-snapshot	Optimized gas costs for contract tests.

This table summarizes the extensive updates made across different components of the Kroma platform, focusing on improving contract interactions, testing, and deployment strategies.

---

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 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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.
• 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.

[coderabbitai]

Actionable comments posted: 5

[sm-stack]

Added a commit that updates isValManagerEnabled flag in a real-time manner by subscribing to output submission event.

[seolaoh]

LGTM

[0xHansLee]

LGTM

[sm-stack]

@0xHansLee I restored two of changes regarding your feedbacks (link 1 & 2), since I think they are duplicates for the below return statements at L#332 & L#654.

[Pangssu]

LGTM