chore: moved wss page to advanced

[keenbeen32]

Summary by CodeRabbit

• Documentation
  • Reorganized WebSockets documentation, moving it from the Tutorials section to the Advanced section for better categorization and improved discoverability.

_{✏️ 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	Jan 21, 2026 2:43pm

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request reorganizes the WebSockets documentation by relocating it from the Tutorials section to the Advanced section in the sidebar navigation configuration file.

Changes

Cohort / File(s)	Summary
Sidebar Navigation Configuration sidebarsHyperIndex.js	Removed "Tutorials/websockets" entry from Tutorials category and added "Advanced/websockets" entry to Advanced category; net change of +2 lines, -1 line

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Hops through the docs with glee,
Moving websockets up the tree,
From Tutorials to Advanced we go,
A sidebar shuffle, neat and pro! ✨

🚥 Pre-merge checks | ✅ 3

✅ 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: moving the WebSocket documentation from the Tutorials category to the Advanced category.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

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

13-17: Verify or source the "2000x faster" performance claim; consider alternative wording if unsourced.

The Sei Chain ID 1329 is correct per Sei's official documentation. The HyperSync and HyperRPC endpoints exist (the 403 responses in our check are expected due to sandbox restrictions, not invalid endpoints). However, the "2000x faster than traditional RPC methods" statement appears unsubstantiated in publicly available sources. Either provide a published benchmark or use softer language like "dramatically accelerates synchronization" to avoid overstating performance improvements.

This applies to lines 29, and references in lines 23 and other documentation sections.

✏️ Example alternative wording

-HyperSync accelerates the synchronization of historical data on Sei, enabling what usually takes hours to sync millions of events to be completed in under a minute—up to 2000x faster than traditional RPC methods.
+HyperSync accelerates the synchronization of historical data on Sei, significantly reducing sync times compared to traditional RPC methods.

🤖 Fix all issues with AI agents

In `@docs/HyperIndex/supported-networks/sei-testnet.md`:
- Around line 13-17: Replace the unsupported numeric performance claim "up to
2000x faster" (and similar "2000x faster") in
docs/HyperIndex/supported-networks/sei-testnet.md with neutral, verifiable
language; locate the occurrences by searching for the exact phrase "2000x
faster" or "up to 2000x faster" and update them to wording such as "provides
significant performance improvements over traditional RPC methods" or "offers
improved performance compared to traditional RPC methods," and if a benchmark or
source exists, replace with a brief cited statement like "as measured in
[source]" linking to that evidence.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

cat -n docs/HyperIndex/supported-networks/sei-testnet.md

Repository: enviodev/docs

Length of output: 3590

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== Testing Endpoint Accessibility ==="
for url in \
  "https://sei-testnet.hypersync.xyz" \
  "https://1328.hypersync.xyz" \
  "https://sei-testnet.rpc.hypersync.xyz" \
  "https://1328.rpc.hypersync.xyz"
do
  echo -n "$url: "
  curl -sS -o /dev/null -I -w "%{http_code}\n" "$url" 2>&1 || echo "FAILED"
done

Repository: enviodev/docs

Length of output: 245

---

🌐 Web query:

Sei Testnet chain ID official documentation

💡 Result:

Sei Testnet chain IDs:

• Cosmos SDK chain-id: atlantic-2. [1]
• EVM chain-id (for MetaMask/RPC): 1328 (0x530). [2]

Sources: Sei docs — Chains / Testnet and Sei EVM Networks. [1] [2]

---

🌐 Web query:

Sei Network testnet chain ID 1328

💡 Result:

Yes — Sei Network testnet (atlantic-2) uses EVM chain ID 1328 (hex 0x530). Example RPC: https://evm-rpc-testnet.sei-apis.com. [1][2]

Sources:
[1] Sei docs — EVM networks / testnet (chainId 1328, 0x530).
[2] Sei support — Testnet / MetaMask instructions (testnet Chain ID 1328).

---

🌐 Web query:

HyperSync performance 2000x faster benchmark

💡 Result:

Do you mean a specific product, library, or article claiming "HyperSync" is 2000× faster? If so, please paste the link or tell me where you saw the claim (paper, blog, vendor page, GitHub, benchmark). I’ll search and verify the benchmark and sources.

---

Soften the unsourced "2000x faster" performance claim on line 29 (and similar statements on lines 23, 29, 43).

The chain ID 1328 is correct for Sei Testnet. However, the claim that HyperSync is "up to 2000x faster than traditional RPC methods" lacks public documentation or published benchmarks to support it. Replace with neutral language:

Suggested revision

-HyperSync accelerates the synchronization of historical data on Sei Testnet, enabling what usually takes hours to sync millions of events to be completed in under a minute—up to 2000x faster than traditional RPC methods.
+HyperSync accelerates the synchronization of historical data on Sei Testnet, reducing sync times significantly compared to traditional RPC methods.

🤖 Prompt for AI Agents

In `@docs/HyperIndex/supported-networks/sei-testnet.md` around lines 13 - 17,
Replace the unsupported numeric performance claim "up to 2000x faster" (and
similar "2000x faster") in docs/HyperIndex/supported-networks/sei-testnet.md
with neutral, verifiable language; locate the occurrences by searching for the
exact phrase "2000x faster" or "up to 2000x faster" and update them to wording
such as "provides significant performance improvements over traditional RPC
methods" or "offers improved performance compared to traditional RPC methods,"
and if a benchmark or source exists, replace with a brief cited statement like
"as measured in [source]" linking to that evidence.