feat: reject txs with max l1 data fee in worker

[Thegaram]

1. Purpose or design rationale of this PR

Reject txs with overly large data fee in worker.

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

• New Features

  • Transactions with excessively high L1 data fees are now automatically rejected, ensuring better validation and fee control.

• Chores

  • Updated the patch version number to 56.

[coderabbitai]

Walkthrough

This update introduces a new validation step in the transaction processing workflow of the miner's worker, ensuring transactions with excessive L1 data fees are rejected. Additionally, the patch version in the version constants is incremented from 55 to 56.

Changes

Files / Areas	Change Summary
miner/scroll_worker.go	Added L1 data fee validation in processTxn to reject transactions exceeding the maximum allowed.
params/version.go	Incremented VersionPatch constant from 55 to 56.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Worker
    participant Fees

    User->>Worker: Submit Transaction
    Worker->>Worker: Validate size and block size
    Worker->>Fees: CalculateL1DataFee(tx, state, config, blockNum)
    Fees-->>Worker: Return L1 data fee or error
    alt Fee calculation error
        Worker-->>User: Reject transaction (error)
    else Fee >= MaxL1DataFee
        Worker-->>User: Reject transaction (invalid L1 data fee)
    else Fee < MaxL1DataFee
        Worker->>Worker: Continue with transaction execution
    end

Loading

Possibly related PRs

• feat: reject txs with max l1 data fee #1203: Adds similar L1 data fee validation but in the transaction pool's validateTx method, addressing the same logic in a different component.

Suggested reviewers

• colinlyguo
• georgehao

Poem

A patch hops in, not too grand,
With fee checks firm and wisely planned.
L1 too high? The gate is closed—
Only fair transactions posed!
A version bump, a tidy fix,
🐇 approves these clever tricks!

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cf3d22e and f08fb8f.

📒 Files selected for processing (2)

• miner/scroll_worker.go (1 hunks)
• params/version.go (1 hunks)

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

• GitHub Check: check
• GitHub Check: test
• GitHub Check: Analyze (go)

🔇 Additional comments (1)

params/version.go (1)

24-29: Patch bump looks good

The version patch is incremented from 55 → 56 in line 27 to reflect the new feature. No further action required.

[colinlyguo]

lgtm.