Skip to content

Update Network List#757

Closed
nikbhintade wants to merge 1 commit intomainfrom
nb/update-network
Closed

Update Network List#757
nikbhintade wants to merge 1 commit intomainfrom
nb/update-network

Conversation

@nikbhintade
Copy link
Member

@nikbhintade nikbhintade commented Dec 10, 2025

Summary by CodeRabbit

  • Documentation

    • Substantially expanded HyperSync supported networks list with dozens of new entries including Arbitrum, Base, Optimism, Polygon, and Scroll.
    • Updated Citrea Testnet tier classification.
    • Removed Mev Commit from HyperRPC supported networks.
  • Style

    • Reformatted network configuration JSON for improved readability.

✏️ Tip: You can customize this high-level summary in your review settings.

@vercel
Copy link

vercel bot commented Dec 10, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
envio-docs Error Error Dec 10, 2025 6:10am

@nikbhintade nikbhintade self-assigned this Dec 10, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 10, 2025

Walkthrough

Documentation updates across multiple files to reflect network support changes: Citrea Testnet tier updated from STONE to BRONZE, Mev Commit removed from HyperRPC supported networks, HyperSync networks table expanded with numerous new network entries, and supported-networks.json reformatted for readability.

Changes

Cohort / File(s) Summary
Citrea Testnet tier update
docs/HyperIndex/supported-networks/citrea-testnet.md
Updated Citrea Testnet tier label from STONE 🪨 to BRONZE 🥉
Network removals
docs/HyperRPC/hyperrpc-supported-networks.md
Removed Mev Commit row from supported networks table; stray blank line added before header (cosmetic)
Network expansion and updates
docs/HyperSync/hypersync-supported-networks.md
Expanded networks table with ~70 new network entries (Ab, Abstract, Arbitrum, Aurora, Avalanche, Base, Berachain, Blast, Boba, Celo, Ethereum, Fantom, Gnosis, Harmony, Linea, Mantle, Moonbeam, Optimism, Polygon, Scroll, Sepolia, ZKsync, Zora, and many others); updated Citrea Testnet tier from STONE to BRONZE; removed Mev Commit entry
JSON formatting
supported-networks.json
Reformatted JSON array from single-line to multi-line format; no semantic changes to data or network entries

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

  • Straightforward documentation maintenance: Primarily tier label updates, network list additions/removals, and formatting changes with consistent patterns across files
  • Areas requiring extra attention:
    • Verify Citrea Testnet tier update is consistent across all three modified documentation files
    • Confirm Mev Commit removal is intentional and complete across HyperRPC and HyperSync tables
    • Validate new network entries in HyperSync table are correctly formatted and match supported-networks.json structure

Possibly related issues

Possibly related PRs

Suggested reviewers

  • moose-code
  • DenhamPreen
  • DZakh

Poem

🐰 Our networks now shine, both old and new,
Citrea's bronze badge gleams with brilliant hue,
Seventy chains joined our HyperSync fold,
In JSON's clean lines, our network's retold,
From stone to bronze, we hop ahead true! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Update Network List' is generic and vague. While it relates to the changeset (which updates documentation about supported networks), it lacks specificity about what changed or why. Consider a more descriptive title such as 'Add HyperSync networks and update tier labels' or 'Expand network support documentation and standardize tiers'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch nb/update-network

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/HyperSync/hypersync-supported-networks.md (1)

57-57: Address bare URL markdown linting in table context.

Static analysis flags bare URLs on line 57 (and likely throughout the table per MD034). While this appears to be a pre-existing documentation pattern in table cells, consider wrapping URLs in angle brackets (e.g., <https://citrea-testnet.hypersync.xyz>) for strict markdown compliance if your docs pipeline enforces it.

Verify whether your documentation pipeline enforces MD034 compliance and whether this should be addressed in this PR or as a separate formatting cleanup.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 528a16e and c2743a6.

📒 Files selected for processing (4)
  • docs/HyperIndex/supported-networks/citrea-testnet.md (1 hunks)
  • docs/HyperRPC/hyperrpc-supported-networks.md (1 hunks)
  • docs/HyperSync/hypersync-supported-networks.md (2 hunks)
  • supported-networks.json (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: DenhamPreen
Repo: enviodev/docs PR: 673
File: docs/HyperIndex/supported-networks/chainweb-testnet-21.md:14-16
Timestamp: 2025-07-29T14:30:03.677Z
Learning: Chainweb Testnet 20 (ID: 5920) and Chainweb Testnet 21 (ID: 5921) have non-functional HyperSync endpoints that return HTTP 404, indicating these networks are not properly supported and should be removed from documentation.
📚 Learning: 2025-07-29T14:30:03.677Z
Learnt from: DenhamPreen
Repo: enviodev/docs PR: 673
File: docs/HyperIndex/supported-networks/chainweb-testnet-21.md:14-16
Timestamp: 2025-07-29T14:30:03.677Z
Learning: Chainweb Testnet 20 (ID: 5920) and Chainweb Testnet 21 (ID: 5921) have non-functional HyperSync endpoints that return HTTP 404, indicating these networks are not properly supported and should be removed from documentation.

Applied to files:

  • docs/HyperRPC/hyperrpc-supported-networks.md
  • docs/HyperSync/hypersync-supported-networks.md
  • supported-networks.json
🪛 markdownlint-cli2 (0.18.1)
docs/HyperSync/hypersync-supported-networks.md

57-57: Bare URL used

(MD034, no-bare-urls)


57-57: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (4)
docs/HyperRPC/hyperrpc-supported-networks.md (1)

23-112: Mev Commit removal and formatting look good.

The removal of Mev Commit from the supported networks table and the added blank lines for visual spacing are appropriate. The remaining network entries are consistent in formatting and structure.

supported-networks.json (1)

1-5: JSON reformatting for readability is appropriate.

The conversion from a single long line to formatted output improves maintainability without altering the data structure or sequence.

docs/HyperSync/hypersync-supported-networks.md (1)

34-120: Network table expansion and Citrea tier update look good.

The Citrea Testnet tier has been correctly updated to BRONZE 🥉 (consistent with the citrea-testnet.md file), and Mev Commit has been appropriately removed. The expanded network list is well-formatted and maintains consistency across all entries.

docs/HyperIndex/supported-networks/citrea-testnet.md (1)

22-22: Citrea Testnet tier update is consistent across documentation.

The tier has been correctly updated from STONE 🪨 to BRONZE 🥉, matching the corresponding update in hypersync-supported-networks.md. This change reflects the updated service support level for Citrea Testnet.

@nikbhintade
Copy link
Member Author

PR not needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant