fix: post-euclid block tracing

[omerfirmak]

1. Purpose or design rationale of this PR

...

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:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

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

  • Enhanced tracing operations now provide clear error feedback when unsupported blocks are queried under updated network protocols.

• Refactor

  • Optimized the underlying trace logging behavior to yield more accurate diagnostics across varying chain conditions.

• Chores

  • Incremented the patch version to 9, reflecting the latest improvements and updates in the release.

[coderabbitai]

Walkthrough

This pull request modifies how the system handles tracing and versioning. In the tracing logic (both in the VM logger and the rollup tracer), the code now conditionally determines which hash to use and adds an error branch for post-Euclid blocks. Additionally, the patch version has been incremented in the versioning module. No public API or exported entity modifications were made.

Changes

File(s)	Change Summary
core/vm/logger_trace.go rollup/tracing/tracing.go	Tracing Updates: In logger_trace.go, the function now conditionally uses a Poseidon code hash when chain rules are not Euclid and updates the bytecodes map accordingly. In tracing.go, a new branch checks if the block is post-Euclid and returns an error if tracing is attempted.
params/version.go	Version Update: The VersionPatch constant is updated from 8 to 9, reflecting a new patch version in the release.

Sequence Diagram(s)

sequenceDiagram
    participant VM as LoggerTrace
    participant Env as Environment
    participant DB as StateDB
    participant Map as BytecodesMap

    VM->>Env: Call traceCodeWithAddress(address, keccakCodeHash)
    alt Chain rules not Euclid
        Env->>DB: GetPoseidonCodeHash(address)
        DB-->>Env: Return PoseidonCodeHash
        Env-->>VM: Use PoseidonCodeHash as codeHash
    else
        Env-->>VM: Use keccakCodeHash as codeHash
    end
    VM->>Map: Update bytecodes with codeHash

Loading

sequenceDiagram
    participant Caller as Client
    participant TraceEnv as Trace Environment
    participant Chain as ChainConfig

    Caller->>TraceEnv: Call GetBlockTrace(block)
    TraceEnv->>Chain: IsEuclid(block.Time())
    alt Block is post-Euclid
        Chain-->>TraceEnv: True
        TraceEnv-->>Caller: Return error ("Tracing not possible for post-Euclid blocks")
    else
        Chain-->>TraceEnv: False
        TraceEnv->>Caller: Process tracing normally
    end

Loading

Suggested reviewers

• georgehao
• colinlyguo
• Thegaram
• omerfirmak

Poem

I hopped through lines of updated code,
Where hashes shift and errors now forebode.
A twist in trace, a version's new delight,
My rabbit eyes dance at every byte.
Carrot smiles abound in this coding night!
🐇🥕

---

📜 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 f22d6e6f7107d0ce48ffe52b13d64b9b917e3c03 and 543ed19.

📒 Files selected for processing (2)

• params/version.go (1 hunks)
• rollup/tracing/tracing.go (1 hunks)

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

• params/version.go
• rollup/tracing/tracing.go

---

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>, 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. (Beta)
• @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.