Update network

[JasoonS]

Summary by CodeRabbit

• Documentation

  • Added comprehensive Citrea network documentation, including setup guidance and configuration examples for HyperIndex, HyperRPC, and HyperSync.

• Chores

  • Updated supported networks configuration to include Citrea network.

_{✏️ 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	Review	Updated (UTC)
envio-docs	Ready	Preview, Comment	Dec 15, 2025 0:49am

[coderabbitai]

Walkthrough

The PR adds documentation and registry entries for the Citrea network (Chain ID 4114) across HyperIndex, HyperRPC, and HyperSync support catalogs, including configuration examples and endpoint information.

Changes

Cohort / File(s)	Summary
New Citrea Documentation docs/HyperIndex/supported-networks/citrea.md	New documentation page for Citrea network with BRONZE tier designation, metadata (Chain ID 4114, HyperSync/HyperRPC endpoints), YAML configuration examples, and quickstart guidance
Network Catalog Updates docs/HyperRPC/hyperrpc-supported-networks.md, docs/HyperSync/hypersync-supported-networks.md	Added Citrea network row to supported networks tables in both HyperRPC and HyperSync documentation with corresponding network details and tier emoji
Registry Entry supported-networks.json	Added "supported-networks/citrea" entry to the supportedNetworks array

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify Citrea network ID (4114) accuracy and consistency across all three documentation files
• Confirm endpoint URLs and formats match expected HyperRPC/HyperSync patterns
• Validate YAML configuration example in the Citrea documentation page for correctness
• Check for table formatting consistency with existing network entries in HyperRPC and HyperSync docs

Possibly related PRs

• enviodev/docs#697 — Modifies supported-networks.json and adds new network documentation entries
• enviodev/docs#748 — Updates same HyperRPC/HyperSync supported-networks tables and supported-networks.json registry
• enviodev/docs#755 — Edits HyperSync/HyperRPC table structure; potential formatting conflicts with this PR

Suggested reviewers

• DenhamPreen
• Jordy-Baby

Poem

🐰 A chain named Citrea hops into view,
With ID 4114 shining through,
From index to sync to RPC so bright,
We document networks—our docs take flight! 🚀

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 clearly and concisely describes the main change: adding Citrea mainnet to the supported networks documentation across multiple 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 citrea

---

📜 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 6afabc2 and 0d1bde7.

📒 Files selected for processing (4)

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

• supported-networks.json
• docs/HyperRPC/hyperrpc-supported-networks.md
• docs/HyperSync/hypersync-supported-networks.md

🪛 markdownlint-cli2 (0.18.1)

docs/HyperRPC/hyperrpc-supported-networks.md

58-58: Bare URL used

(MD034, no-bare-urls)

---

58-58: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (5)

supported-networks.json (1)

53-53: Entry positioned correctly in alphabetical order.

The addition of "supported-networks/citrea" is properly positioned between "chiliz-testnet-spicy" and "citrea-devnet", maintaining the array's alphabetical ordering.

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

66-66: Citrea entry properly formatted and positioned.

The Citrea mainnet entry (Chain ID 4114) is correctly added with consistent tier designation (🥉), proper URL variants, and correct alphabetical positioning between Chiliz and Curtis.

---

57-57: Verify Base Traces tier change.

Line 57 shows Base Traces tier changed from 🏅 to 🪨. This appears to be a separate change from the Citrea addition. Please confirm this tier adjustment is intentional and documented in the PR scope.

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

1-62: Comprehensive and well-structured Citrea documentation.

The new documentation page is properly formatted with correct metadata, consistent chain ID (4114), accurate endpoint information, clear tier designation (BRONZE 🥉), and a practical YAML configuration example. All internal links and support references follow the established pattern.

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

58-58: Citrea RPC entry correctly formatted and positioned.

The Citrea mainnet entry (Chain ID 4114) is properly added to the HyperRPC supported networks table with correct endpoint variants and alphabetical positioning. Format and structure are consistent with existing entries.

---

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.}

[JasoonS]

We changed this to stone, but maybe we want to increase to bronze 🤔