Add fetch block witness data

[Akagi201]

Summary by CodeRabbit

• New Features

  • Introduced a new RPC client for interacting with Ethereum blocks and execution witnesses.
  • Added a caching mechanism for sender addresses to optimize transaction signing.
  • New JSON file added for testing, representing a blockchain block in the optimism layer.

• Bug Fixes

  • Improved error handling for environment variable checks in block fetching.

• Refactor

  • Overhauled block fetching logic to streamline interactions with the Ethereum client.
  • Simplified function signatures in tests for clarity.
  • Removed outdated schema definitions no longer in use.

[coderabbitai[bot]]

Walkthrough

The changes in this pull request involve a comprehensive overhaul of the block fetching logic within the Ethereum client interaction. The EthRPC struct and its associated methods have been removed, leading to a new RawRpcClient struct introduced in a new file. This new structure simplifies the connection to Ethereum nodes and modifies how block data is fetched and handled. Additionally, a new sender type for caching transaction signers is introduced, while an unused parameter in a test function is updated for clarity. A new JSON file for testing purposes is also added.

Changes

File Path	Change Summary
cmd/fetch-block/main.go	Removed EthRPC struct and methods; modified fetchMainnetBlocks to use rpcClient for block fetching.
cmd/fetch-block/rpc.go	Introduced RawRpcClient struct with methods for connecting to Ethereum nodes and fetching block data.
cmd/fetch-block/schema.go	Deleted file containing BlockInfo, TransactionInfo, and LogInfo structures.
cmd/fetch-block/sender.go	Added senderFromServer type for caching sender addresses; includes methods for checking equality and retrieving addresses.
stateless_executor_test.go	Updated function signature in generateMergeChain to indicate unused parameter.
tests/data/optimism/127609270/block.json	Added new JSON file representing a blockchain block for testing purposes.

Possibly related PRs

• #4: The main PR's changes to the block fetching logic and the introduction of a new rpcClient are related to the modifications in the stateless_executor.go file from PR #4, which also involves processing blocks in a new manner.
• #12: The updates in the stateless_executor.go file in PR #12 reflect changes in how blocks are processed, which aligns with the main PR's overhaul of the block fetching logic and interaction with the Ethereum client.

🐇 In the code where the blocks do flow,
A new RPC client helps us know,
With caching senders, swift and bright,
We fetch the data, day and night.
JSON files for tests, all in a row,
Hopping along, our changes in tow! 🐇✨

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.