add monad mainnet to docs

[nikbhintade]

Summary by CodeRabbit

• New Features

  • Added support for Monad network (Network ID 143) across HyperIndex, HyperRPC, and HyperSync services, enabling indexing, synchronization, and RPC access for Monad-based data.

• Documentation

  • Updated supported networks documentation with Monad configuration details and integration guidance.

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

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
envio-docs	Ready	Preview	Comment	Nov 26, 2025 1:52pm

[coderabbitai]

Walkthrough

Adds support for Monad network (Network ID 143) across documentation and configuration by creating a dedicated HyperIndex page, adding entries to HyperRPC and HyperSync supported networks tables, and updating the supported-networks.json configuration file.

Changes

Cohort / File(s)	Summary
HyperIndex Documentation docs/HyperIndex/supported-networks/monad.md	New documentation file for Monad network with frontmatter, Envio overview, YAML configuration example, and links to further resources.
Network Tables docs/HyperRPC/hyperrpc-supported-networks.md, docs/HyperSync/hypersync-supported-networks.md	Added Monad (Network ID 143) entries to both HyperRPC and HyperSync supported networks tables, positioned between Mode and Monad Testnet rows.
Configuration supported-networks.json	Added "supported-networks/monad" entry to the supportedNetworks array.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Straightforward documentation additions with homogeneous changes (same network added across multiple consistent locations)
• No logic modifications, control flow changes, or complex interactions
• Minor verification needed for consistency of Network ID 143 across all files and table formatting

Possibly related PRs

• fix: remove duplicate from sidebar #743: Edits the same supported networks lists and HyperRPC/HyperSync documentation tables.
• Update supported networks documentation and configuration. Removed Be… #730: Adds a new network entry to supported networks documentation and updates HyperRPC/HyperSync docs and supported-networks.json.
• Update supported chains #672: Modifies supported-networks listings and adds new per-network documentation across HyperIndex, HyperSync, and HyperRPC.

Suggested reviewers

• DenhamPreen
• moose-code

Poem

🐰 A hopping hop to Monad's land,
Where 143 now joins the band,
Through tables, docs, and JSON bright,
The network shines in sync's delight! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'add monad mainnet to docs' accurately describes the main change: adding documentation for Monad mainnet across multiple documentation files.
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/add-monad-mainnet

---

📜 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 aeec4ec and 010be2f.

📒 Files selected for processing (4)

• docs/HyperIndex/supported-networks/monad.md (1 hunks)
• docs/HyperRPC/hyperrpc-supported-networks.md (1 hunks)
• docs/HyperSync/hypersync-supported-networks.md (1 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/HyperRPC/hyperrpc-supported-networks.md

74-74: Bare URL used

(MD034, no-bare-urls)

---

74-74: Bare URL used

(MD034, no-bare-urls)

docs/HyperSync/hypersync-supported-networks.md

82-82: Bare URL used

(MD034, no-bare-urls)

---

82-82: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (5)

docs/HyperRPC/hyperrpc-supported-networks.md (1)

74-74: Verify markdown linting configuration for bare URLs in tables.

The markdown linter (MD034) flags bare URLs on this line, yet identical URL formatting exists in other rows (e.g., Mode on line 73) without flagging. If the linter should be enforcing this rule, consider wrapping URLs in angle brackets (<url>) or using markdown link syntax across the entire table for consistency. Otherwise, the linter configuration may need adjustment to exempt URLs within table cells.

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

82-82: Verify markdown linting configuration for bare URLs in tables.

The markdown linter (MD034) flags bare URLs on this line, yet identical URL formatting exists throughout the table without flagging (e.g., Mode on line 81). If the linter should be enforcing this rule, consider wrapping URLs in angle brackets (<url>) or using markdown link syntax. Otherwise, clarify whether the linting rule should be adjusted to exempt URLs within table cells or applied globally across the documentation.

supported-networks.json (1)

5-5: Entry correctly positioned in alphabetical order.

The "supported-networks/monad" entry is properly inserted between "supported-networks/mode" and "supported-networks/monad-testnet" in the supportedNetworks array, maintaining correct alphabetical ordering.

docs/HyperIndex/supported-networks/monad.md (2)

1-63: Well-structured documentation with proper consistency across files.

The new Monad documentation page is comprehensive and follows established patterns. Network ID 143 is consistent with entries in HyperRPC and HyperSync tables, tier information (GOLD 🏅) aligns across files, and the YAML configuration example is clear and practical. The page properly references related services (HyperIndex, HyperSync, HyperRPC) and provides clear support channels.

---

14-16: Verify Monad network endpoints are operational.

Given the prior experience with non-functional network endpoints (e.g., Chainweb Testnet HTTP 404 failures noted in PR 673), ensure that the Monad HyperSync and HyperRPC endpoints (https://monad.hypersync.xyz and https://monad.rpc.hypersync.xyz) have been validated as functional before this documentation goes live. This will prevent users from encountering dead endpoints.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

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