chore: added plasma to supported networks

[keenbeen32]

Just ran prebuild to update supported netwroks

Summary by CodeRabbit

• Documentation

  • Added a new Plasma network page under supported networks with chain ID, HyperSync/HyperRPC endpoints, overview, getting started, and configuration example.
  • Updated HyperRPC supported networks to include Plasma with both RPC endpoints.
  • Updated HyperSync supported networks to include Plasma (ID 9745) with endpoint variants and tier indicator.

• Style

  • Reflowed supported-networks.json formatting for readability; no content changes.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
envio-docs	Ready	Preview	Comment	Oct 15, 2025 2:59pm

[coderabbitai]

Walkthrough

Adds Plasma network documentation and entries: a new HyperIndex page for Plasma, Plasma rows in HyperRPC and HyperSync supported networks tables, and a reflow-only formatting change to supported-networks.json. No code logic or exported/public APIs changed.

Changes

Cohort / File(s)	Summary
Plasma docs addition docs/HyperIndex/supported-networks/plasma.md	New Plasma network page with frontmatter, overview, endpoints, Bronze tier note, YAML config example, and links to guides/support.
Supported networks tables update docs/HyperRPC/hyperrpc-supported-networks.md, docs/HyperSync/hypersync-supported-networks.md	Added Plasma (ID 9745) entries with HyperRPC and HyperSync endpoint variants; table rows follow existing format.
JSON formatting reflow supported-networks.json	Reformatted array across lines; no data changes.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• HyperIndex v2.21 #631 — Touches the same supported-networks docs, adjusting network entries; overlaps with this PR’s table modifications.
• add showcase #702 — Adds new network documentation and updates HyperSync/HyperRPC tables, similar in scope and files to this PR.

Suggested reviewers

• DenhamPreen
• DZakh

Poem

In docs I hop with nimble glee,
A Plasma path for all to see.
Tables tweaked, JSON aligned,
Endpoints mapped, neatly defined.
Thump goes my paw—release day cheer!
Hyper trails marked, the way is clear. 🐇✨

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 follows conventional commit style and succinctly summarizes the primary change of adding Plasma to the supported networks list without extraneous details, ensuring clarity for reviewers scanning the history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch kv/plasma-in-supported-networks

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

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

[DenhamPreen]

This should be automated somewhere, but a win is a win

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

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

61-61: Standardize Discord invite URL for consistency.

Other pages use discord.gg; consider aligning:

-Can’t find what you’re looking for or need support? Reach out to us on [Discord](https://discord.com/invite/Q9qt8gZ2fX); we’re always happy to help!
+Can’t find what you’re looking for or need support? Reach out to us on [Discord](https://discord.gg/Q9qt8gZ2fX); we’re always happy to help!

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 06ba5a0 and e780608.

📒 Files selected for processing (4)

• docs/HyperIndex/supported-networks/plasma.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 comments (4)

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

1-17: Well-structured Plasma page; endpoints and chain ID consistent.

Frontmatter + table look solid.

supported-networks.json (1)

5-5: Content change + duplicate detected.

• Plasma entry was added (not just formatting) — contradicts the “reflow-only” summary.
• “supported-networks/crossfi-mainnet” appears twice; please de‑dupe at the source/generator.

To confirm and locate duplicates:

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

84-84: Plasma row confirmed – endpoints reachable
HTTP 405 on GET is expected for POST-only JSON-RPC; no changes needed.

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

92-92: Confirm Plasma endpoints are deployed and chain ID consistency

• Endpoints (https://plasma.hypersync.xyz, https://9745.hypersync.xyz) returned 404—confirm they’re deployed and accessible.
• Verify chain ID 9745 is used consistently across docs/HyperSync (e.g., grep -n '9745' docs/HyperSync).