Add support Hyperliquid

[imperator-co]

Description

• Added support for Hyperliquid network (chain ID 999) in the EVM network configuration
• Added common token contract addresses for Hyperliquid mainnet
• Configured start block and network name for Hyperliquid

Issues Resolved

• N/A

Summary by CodeRabbit

• New Features
  • Introduced support for a new blockchain network configuration, "hyperliquid-mainnet". This update enables the application to recognize and interact with the additional network, enhancing its connectivity options with preset operational parameters.

[coderabbitai]

Walkthrough

This change updates the EvmNetwork class in chainbench/test_data/evm.py by adding a new network configuration. A new entry for chain ID 999 with the name "hyperliquid-mainnet" is introduced. The entry specifies a start_block of 1 and provides a list of five Ethereum contract addresses. The application can now recognize and utilize this additional network configuration alongside the existing ones.

Changes

File	Summary of Changes
chainbench/.../evm.py	Added a new entry in the DATA mapping within the EvmNetwork class for chain ID 999 with name "hyperliquid-mainnet", start_block of 1, and specified contract addresses.

Sequence Diagram(s)

sequenceDiagram
    participant U as User/Caller
    participant E as EvmNetwork
    participant D as DATA Mapping
    U->>E: Request network configuration (e.g., chain 999)
    E->>D: Look up configuration for chain ID 999
    D-->>E: Return "hyperliquid-mainnet" configuration details
    E-->>U: Provide network configuration

Loading

Poem

In a burrow of code, I leap with glee,
A chain new and shiny, for all to see.
"hyperliquid-mainnet" hops into play,
Fresh configurations brighten the day! 🐰✨
My floppy ears dance as features abide!

---

📜 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 8967008 and 23e39c5.

📒 Files selected for processing (1)

• chainbench/test_data/evm.py (1 hunks)

🔇 Additional comments (1)

chainbench/test_data/evm.py (1)

400-410: Addition of Hyperliquid Network looks good!

The implementation correctly adds chain ID 999 for "hyperliquid-mainnet" with a start block of 1 and five contract addresses. This successfully fulfills the PR objective of incorporating support for the Hyperliquid network.

For even better consistency with some other mainnet entries like Ethereum, BSC, and Polygon, consider using checksummed addresses instead of lowercase. This isn't critical but would maintain format consistency across networks.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[erwin-wee]

Hi @imperator-co! Thanks for making this PR. I just have some questions regarding the addresses you're adding which I checked on https://hyperliquid.cloud.blockscout.com/.

• "0x2df1c51e09aecf9cacb7bc98cb1742757f163df7" - This one doesn't seem to be a contract, and has no transactions
• "0x3333333333333333333333333333333333333333" - This one doesn't seem to be a contract
• "0x2222222222222222222222222222222222222222" - This is a contract. Looks good.
• "0x5555555555555555555555555555555555555555" - This is an erc20 token, also looks good.
• "0x510100d5143e011db24e2aa38abe85d73d5b2177" - This one doesn't seem to exist

For the ones in bold, may I know where you got them from or why did you choose these addresses to add here?