fixed blog path to match tweet

[nikbhintade]

Summary by CodeRabbit

• New Features

  • Added support for Hoodi (testnet tier) and Injective (bronze tier) networks.
  • Both networks are now available on HyperRPC and HyperSync services.

• Documentation

  • Added comprehensive guides for setting up and configuring Hoodi and Injective networks.
  • Guides include configuration examples, endpoint references, and setup instructions.

_{✏️ 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 31, 2025 2:13pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR adds comprehensive documentation for two new supported networks (Hoodi and Injective), including dedicated network configuration pages, updates to supported networks tables in HyperRPC and HyperSync documentation, and configuration manifest entries. Additionally, it updates a blog post slug for consistency.

Changes

Cohort / File(s)	Summary
New Network Documentation docs/HyperIndex/supported-networks/hoodi.md, docs/HyperIndex/supported-networks/injective.md	Added new markdown documentation pages for Hoodi (TESTNET tier) and Injective (BRONZE tier) networks, each including frontmatter, network overview, YAML configuration examples, setup guidance, and Discord support links.
HyperRPC Network Support docs/HyperRPC/hyperrpc-supported-networks.md	Added two new network entries to the supported networks table: Hoodi (ID 560048, endpoints: hoodi.rpc.hypersync.xyz / 560048.rpc.hypersync.xyz) and Injective (ID 1776, endpoints: injective.rpc.hypersync.xyz / 1776.rpc.hypersync.xyz).
HyperSync Network Support docs/HyperSync/hypersync-supported-networks.md	Added two new network entries to the supported networks table: Hoodi (ID 560048, URLs: hoodi.hypersync.xyz / 560048.hypersync.xyz) and Injective (ID 1776, URLs: injective.hypersync.xyz / 1776.hypersync.xyz).
Configuration Manifest supported-networks.json	Added two entries to the supportedNetworks array: "supported-networks/hoodi" and "supported-networks/injective".
Blog Post Update blog/2025-12-16-dev-update-december-2025.md	Updated page slug from /blog/dev-update-december-2025 to /blog/envio-developer-update-december-2025.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• #765: Directly updates the same December 2025 developer update blog post entry that this PR modifies the slug for.
• #672: Modifies supported-networks.json and adds new supported network documentation pages in the same structure.
• #748: Updates docs/HyperRPC/hyperrpc-supported-networks.md with network row changes.

Suggested reviewers

• moose-code
• DZakh

Poem

🐰 Hop, hop, two networks join the fray,
Hoodi and Injective come to play!
Docs aligned and tables bright,
Configuration set just right! ✨
A slug renamed for dev updates so grand,
New networks blooming across the land! 🌱

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title 'fixed blog path to match tweet' is misleading. While the changeset includes a blog path update, it primarily adds support for two new networks (Hoodi and Injective) across multiple documentation files.	Update the title to reflect the main changes, such as 'Add Hoodi and Injective network support' or 'Add documentation for Hoodi and Injective networks'.

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

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3a017ca and 1bce45c.

📒 Files selected for processing (6)

• blog/2025-12-16-dev-update-december-2025.md
• docs/HyperIndex/supported-networks/hoodi.md
• docs/HyperIndex/supported-networks/injective.md
• docs/HyperRPC/hyperrpc-supported-networks.md
• docs/HyperSync/hypersync-supported-networks.md
• supported-networks.json

🧰 Additional context used

🧠 Learnings (1)

📚 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

🪛 LanguageTool

docs/HyperIndex/supported-networks/hoodi.md

[grammar] ~8-~8: Ensure spelling is correct
Context: ...idebar_label: Hoodi slug: /hoodi --- # Hoodi ## Indexing Hoodi Data with Envio | **Fiel...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🪛 markdownlint-cli2 (0.18.1)

docs/HyperRPC/hyperrpc-supported-networks.md

81-81: Bare URL used

(MD034, no-bare-urls)

---

81-81: Bare URL used

(MD034, no-bare-urls)

---

82-82: Bare URL used

(MD034, no-bare-urls)

---

82-82: Bare URL used

(MD034, no-bare-urls)

---

83-83: Bare URL used

(MD034, no-bare-urls)

---

83-83: Bare URL used

(MD034, no-bare-urls)

docs/HyperSync/hypersync-supported-networks.md

89-89: Bare URL used

(MD034, no-bare-urls)

---

89-89: Bare URL used

(MD034, no-bare-urls)

---

90-90: Bare URL used

(MD034, no-bare-urls)

---

90-90: Bare URL used

(MD034, no-bare-urls)

---

91-91: Bare URL used

(MD034, no-bare-urls)

---

91-91: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (6)

blog/2025-12-16-dev-update-december-2025.md (1)

4-4: LGTM! Verify external references if needed.

The slug update aligns with the PR objective to match a tweet. Consider verifying that any external references or social media posts are updated to use the new URL path if this post has already been shared.

supported-networks.json (1)

89-93: LGTM! Network entries added correctly.

The additions of Hoodi and Injective are properly formatted and placed in alphabetical order within the supportedNetworks array.

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

1-63: LGTM! Comprehensive network documentation.

The Hoodi network documentation is well-structured and consistent with the pattern used for other supported networks. All technical details (chain ID, endpoints, tier) match the entries in the HyperSync and HyperRPC tables. The YAML configuration example is clear and follows standard conventions.

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

1-63: LGTM! Comprehensive network documentation.

The Injective network documentation is well-structured and consistent with the pattern used for other supported networks. All technical details (chain ID, endpoints, tier) match the entries in the HyperSync and HyperRPC tables. The YAML configuration example is clear and follows standard conventions.

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

81-83: Formatting and alphabetical ordering are correct.

The entries are properly positioned in alphabetical order (Holesky → Hoodi → Hyperliquid → Injective), use consistent URL patterns with existing entries, and follow the documented format.

Note: RPC endpoints return HTTP 403 (Forbidden) status, which indicates they exist and are responding but require authentication. This aligns with the document's statement that API tokens are required starting June 2025.

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

89-91: Verify endpoint accessibility—these endpoints return HTTP 403 (Forbidden).

The Hoodi and Injective entries are correctly formatted, properly positioned in alphabetical order, and have appropriate tier assignments (TESTNET 🎒 and BRONZE 🥉). However, all tested endpoints (Hoodi, Injective, and Hyperliquid) return HTTP 403 responses rather than 200, indicating access is denied. Combined with the prior learnings about non-functional HyperSync endpoints, these endpoints should be confirmed as operational and accessible to users before release.

---

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