Add arbitrum2 network config

[findolor]

Motivation

Solution

Checks

By submitting this for review, I'm confirming I've done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

Summary by CodeRabbit

• New Features
  • Added support for the "arbitrum2" network, including network configuration, subgraph integration, and orderbook support.

[coderabbitai]

Walkthrough

A new "arbitrum2" network configuration was introduced in the settings, duplicating the existing "arbitrum" network's parameters. Corresponding "arbitrum2" entries were also added to the subgraphs and orderbooks sections, each with unique URLs or addresses, referencing the new or existing networks as appropriate.

Changes

File(s)	Change Summary
settings.json	Added "arbitrum2" entries to "networks", "subgraphs", and "orderbooks" sections with new values.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant NetworksConfig
    participant SubgraphsConfig
    participant OrderbooksConfig

    User->>App: Selects "arbitrum2" network
    App->>NetworksConfig: Fetch "arbitrum2" network settings
    App->>SubgraphsConfig: Fetch "arbitrum2" subgraph URL
    App->>OrderbooksConfig: Fetch "arbitrum2" orderbook address
    App-->>User: Uses arbitrum2 configuration for operations

Loading

Possibly related PRs

• Add new subgraph and orderbook fields for arbitrum #35: Adds "arbitrum-2" subgraph and orderbook entries, closely related to the addition of "arbitrum2" network and associated configurations in this PR.

Suggested reviewers

• dcatki
• hardyjosh

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e741a1b and ff34364.

📒 Files selected for processing (1)

• settings.json (1 hunks)

🔇 Additional comments (2)

settings.json (2)

56-57: Confirm subgraph endpoint for arbitrum2
The arbitrum2 subgraph URL reuses the ob4-arbitrum-one path but with a new deployment timestamp. Please verify this is intentional and that the correct subgraph is targeted for the new network.

---

27-32:

Details

❓ Verification inconclusive

Validate duplication of network parameters
The "arbitrum2" entry duplicates the existing "arbitrum" RPC, chain-id, network-id, and currency settings. Confirm if this is intentional or if a distinct RPC endpoint or chain configuration should be used.

---

🏁 Script executed:

#!/bin/bash
# Locate the settings.json file
settings_file=$(rg --files | grep -i "settings.json" | head -n1)
echo "Using settings file: $settings_file"

# Show all occurrences of "arbitrum" entries with line numbers
rg -n '"arbitrum"' -n "$settings_file"

# Print JSON objects for both keys, sorted for comparison
jq -S '.["arbitrum"], .["arbitrum2"]' "$settings_file"

Length of output: 688

---

🏁 Script executed:

#!/bin/bash
# Display the first 60 lines with line numbers to inspect the "arbitrum" entry
nl -ba settings.json | sed -n '1,60p'

Length of output: 130

---

🏁 Script executed:

#!/bin/bash
# Print the first 200 lines of settings.json with line numbers for context
awk '{printf "%4d %s\n", NR, $0}' settings.json | sed -n '1,200p'

Length of output: 5680

---

Confirm intentional duplication of “arbitrum2” configuration
The networks.arbitrum2 entry in settings.json (lines 27–32) uses the same RPC URL, chain-id, network-id, and currency as networks.arbitrum.
• settings.json, lines 27–32:

"arbitrum2": {
  "rpc": "https://1rpc.io/arb",
  "chain-id": 42161,
  "network-id": 42161,
  "currency": "ETH"
},

Please verify whether this duplicate configuration is intentional (e.g., to point to a separate subgraph or orderbook) or if arbitrum2 should use a distinct RPC endpoint or chain settings.

---

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.