chore: ran update-endpoints to update supported networks

[keenbeen32]

Only ran update-endpoints.js to update the list of supported networks.

Summary by CodeRabbit

• New Features

  • Added support for Gnosistemp (ID 100101) and Gnosis Traces (ID 100) across HyperSync and HyperRPC.
  • Updated Hyperliquid network ID to 999.

• Documentation

  • New Gnosistemp network page with endpoints, quickstart, and sample config.
  • Updated HyperSync/HyperRPC supported networks tables to include Gnosistemp and Gnosis Traces and reflect Hyperliquid changes.

• Chores

  • Refreshed supported networks list, adding and reorganizing many networks (e.g., Arbitrum Nova, Aurora, Merlin, Manta, Mantle, Ink) for broader coverage.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
envio-docs	Error			Aug 27, 2025 8:34am

[coderabbitai]

Walkthrough

Adds a new Gnosistemp network docs page, updates HyperRPC and HyperSync supported network tables (including Gnosis Traces additions and Hyperliquid ID change), and replaces the supported-networks.json array with a revised, expanded set of networks.

Changes

Cohort / File(s)	Summary of changes
New Gnosistemp docs page docs/HyperIndex/supported-networks/gnosistemp.md	Introduces a dedicated Gnosistemp page with front matter, HyperSync/HyperRPC endpoints, chain ID 100101, tier, quickstart, and sample YAML config.
Supported networks docs tables docs/HyperSync/HyperRPC/hyperrpc-supported-networks.md, docs/HyperSync/hypersync-supported-networks.md	Adds Gnosis Traces (ID 100) and Gnosistemp (ID 100101); updates Hyperliquid from ID 645749 to 999 and corresponding endpoint hostnames; keeps other entries unchanged.
Networks registry overhaul supported-networks.json	Replaces the supportedNetworks array with a reconfigured, expanded list (adds multiple networks; reorders/updates entries); structure unchanged.

Sequence Diagram(s)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• llm docs revamp #673 — Also updates supported-networks docs and JSON; overlaps on the same files.
• Developer update may 2025 blog #646 — Revises supported-networks.json array contents; similar data changes.
• HyperIndex v2.21 #631 — Modifies HyperSync/HyperRPC supported network tables; potential table conflicts.

Suggested reviewers

• DenhamPreen
• moose-code

Poem

Hoppity hooray, new nets to index I see,
Gnosistemp’s a carrot, fresh for Envio’s tea. 🥕
Traces on the breeze, Hyperliquid shifts its key,
Tables tidied, lists renewed—so networked we shall be.
Boop-boop, nose-twitch, docs ship with glee! 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch kv/celo

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[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)

supported-networks.json (1)

1-5: Remove duplicate network entry & harden CI guard

The supported-networks.json list currently contains a duplicate entry for supported-networks/crossfi-mainnet, which will cause inconsistencies and should be removed. Additionally, the CI validation script needs to be adjusted to:

• Properly detect duplicates and fail fast
• Avoid process-substitution errors (e.g. /dev/fd/63 issues) by piping into the while read loop
• Check for missing docs and fail when any are absent

Affected file:
• supported-networks.json – remove the second occurrence of "supported-networks/crossfi-mainnet"

Suggested CI guard (e.g. in .github/workflows/validate-js.yml or similar):

#!/usr/bin/env bash
set -euo pipefail

echo "▶️ Validating supported-networks.json syntax"
jq . supported-networks.json >/dev/null

echo "▶️ Checking for duplicate slugs"
duplicates=$(jq -r '.supportedNetworks[]' supported-networks.json \
  | sort \
  | uniq -d)
if [[ -n "$duplicates" ]]; then
  echo "❌ Duplicate network slugs found:"
  echo "$duplicates"
  exit 1
fi

echo "▶️ Verifying corresponding docs exist"
jq -r '.supportedNetworks[]' supported-networks.json \
  | while read -r slug; do
      name=${slug#supported-networks/}
      doc="docs/HyperIndex/supported-networks/${name}.md"
      if [[ ! -f "$doc" ]]; then
        echo "❌ Missing doc for network: $slug -> $doc"
        exit 1
      fi
    done

echo "✅ supported-networks.json is valid"

Please:

• Remove the duplicate entry for crossfi-mainnet in supported-networks.json.
• Add or update the CI step with the script above to catch duplicates or missing docs automatically.

🧹 Nitpick comments (3)

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

57-61: Fix markdownlint MD034 by wrapping bare URLs.

Convert the new/updated rows’ plain URLs to autolinks to satisfy MD034.

-| Gnosis Traces        | 100        | https://gnosis-traces.rpc.hypersync.xyz or https://100-traces.rpc.hypersync.xyz     |                 |
-| Gnosistemp           | 100101     | https://gnosistemp.rpc.hypersync.xyz or https://100101.rpc.hypersync.xyz            |                 |
-| Hyperliquid          | 999        | https://hyperliquid.rpc.hypersync.xyz or https://999.rpc.hypersync.xyz              |                 |
+| Gnosis Traces        | 100        | <https://gnosis-traces.rpc.hypersync.xyz> or <https://100-traces.rpc.hypersync.xyz> |                 |
+| Gnosistemp           | 100101     | <https://gnosistemp.rpc.hypersync.xyz> or <https://100101.rpc.hypersync.xyz>        |                 |
+| Hyperliquid          | 999        | <https://hyperliquid.rpc.hypersync.xyz> or <https://999.rpc.hypersync.xyz>          |                 |

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

26-31: Word choice nit: prefer “high-performance” over “hyper-performant.”

Minor clarity/style tweak.

-Envio is a modular hyper-performant data indexing solution for Gnosistemp, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data.
+Envio is a modular high-performance data indexing solution for Gnosistemp, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data.

---

61-61: Standardize Discord link format.

Other pages use discord.gg; align for consistency.

-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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 29cfc49 and 28c971d.

⛔ Files ignored due to path filters (2)

• package-lock.json is excluded by !**/package-lock.json
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (4)

• docs/HyperIndex/supported-networks/gnosistemp.md (1 hunks)
• docs/HyperSync/HyperRPC/hyperrpc-supported-networks.md (1 hunks)
• docs/HyperSync/hypersync-supported-networks.md (1 hunks)
• supported-networks.json (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/HyperIndex/supported-networks/gnosistemp.md

[grammar] ~22-~22: There might be a mistake here.
Context: ...hypersync.xyz) | --- ### Tier GOLD 🏅 ### Overview Envio is a modular hyper-perfo...

(QB_NEW_EN)

🪛 markdownlint-cli2 (0.17.2)

docs/HyperSync/HyperRPC/hyperrpc-supported-networks.md

57-57: Bare URL used

(MD034, no-bare-urls)

---

57-57: Bare URL used

(MD034, no-bare-urls)

---

58-58: Bare URL used

(MD034, no-bare-urls)

---

58-58: Bare URL used

(MD034, no-bare-urls)

---

59-59: Bare URL used

(MD034, no-bare-urls)

---

59-59: Bare URL used

(MD034, no-bare-urls)

---

60-60: Bare URL used

(MD034, no-bare-urls)

---

60-60: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

---

61-61: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (6)

docs/HyperSync/HyperRPC/hyperrpc-supported-networks.md (2)

57-58: Additions look correct (IDs and endpoints match patterns).

Gnosis Traces (100) and Gnosistemp (100101) entries are consistent with naming and endpoint conventions.

---

57-61: Cross-file consistency verified. All network entries in docs/HyperSync/HyperRPC/hyperrpc-supported-networks.md match the entries in supported-networks.json, and the docs/HyperIndex/supported-networks/gnosistemp.md page exists. No further changes needed.

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

65-66: New network rows look good.

Gnosis Traces (100) and Gnosistemp (100101) added with correct endpoints and tiers.

---

69-69: Hyperliquid ID update confirmed.

ID changed to 999 with consistent endpoints; matches HyperRPC page.

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

12-17: Endpoints/table content LGTM.

Chain ID and endpoints match other docs; good addition.

---

8-10: Ignore duplicate H1 suggestion: consistent with project convention

The top-level heading in docs/HyperIndex/supported-networks/gnosistemp.md matches every other supported-networks page (all include an H1 on line 8). Removing it would diverge from the established pattern.

Likely an incorrect or invalid review comment.

[coderabbitai]

⚠️ Potential issue

Duplicate entry and a likely typo in slugs.

• "supported-networks/crossfi-mainnet" appears twice.
• "supported-networks/now-chaint" looks like a typo (probably "now-chain").

Please dedupe and fix the slug to avoid broken links and sidebar generation issues.

- ..."supported-networks/crossfi-mainnet","supported-networks/crossfi-mainnet","supported-networks/crossfi-testnet",...
+ ..."supported-networks/crossfi-mainnet","supported-networks/crossfi-testnet",...
- ...,"supported-networks/now-chaint",...
+ ...,"supported-networks/now-chain",...

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"supported-networks/0g-newton-testnet","supported-networks/abstract","supported-networks/aleph-zero-evm","supported-networks/altlayer-op-demo-testnet","supported-networks/ancient8","supported-networks/arbitrum","supported-networks/arbitrum-blueberry","supported-networks/arbitrum-nova","supported-networks/arbitrum-sepolia","supported-networks/artela-testnet","supported-networks/arthera-mainnet","supported-networks/asset-chain-mainnet","supported-networks/astar-zkevm","supported-networks/astar-zkyoto","supported-networks/aurora","supported-networks/aurora-turbo","supported-networks/avalanche","supported-networks/b2-hub-testnet","supported-networks/b3","supported-networks/b3-sepolia-testnet","supported-networks/base","supported-networks/base-sepolia","supported-networks/beam","supported-networks/berachain","supported-networks/berachain-artio-testnet","supported-networks/berachain-bartio","supported-networks/bevm-mainnet","supported-networks/bevm-testnet","supported-networks/bitfinity-mainnet","supported-networks/bitfinity-testnet","supported-networks/bitgert-mainnet","supported-networks/bitlayer","supported-networks/blast","supported-networks/blast-sepolia","supported-networks/bob-mainnet","supported-networks/boba","supported-networks/boba-bnb-mainnet","supported-networks/botanix-testnet","supported-networks/bsc","supported-networks/bsc-testnet","supported-networks/canto","supported-networks/canto-testnet","supported-networks/celo","supported-networks/celo-alfajores-testnet","supported-networks/chainweb-testnet-20","supported-networks/chainweb-testnet-21","supported-networks/chiliz","supported-networks/chiliz-testnet-spicy","supported-networks/citrea-devnet","supported-networks/citrea-testnet","supported-networks/core","supported-networks/creator-testnet","supported-networks/cronos-zkevm","supported-networks/cronos-zkevm-testnet","supported-networks/crossfi-mainnet","supported-networks/crossfi-mainnet","supported-networks/crossfi-testnet","supported-networks/curtis","supported-networks/cyber","supported-networks/degen-chain","supported-networks/dfk-chain","supported-networks/dogechain-mainnet","supported-networks/dogechain-testnet","supported-networks/dos-chain","supported-networks/energy-web","supported-networks/eos","supported-networks/eth","supported-networks/etherlink-testnet","supported-networks/exosama","supported-networks/fantom","supported-networks/fantom-testnet","supported-networks/flare","supported-networks/flare-songbird","supported-networks/flow","supported-networks/flow-testnet","supported-networks/fraxtal","supported-networks/fuel-mainnet","supported-networks/fuel-testnet","supported-networks/fuji","supported-networks/galadriel-devnet","supported-networks/gnosis","supported-networks/gnosis-chiado","supported-networks/gnosistemp","supported-networks/gravity-alpha-mainnet","supported-networks/harmony-shard-0","supported-networks/heco-chain","supported-networks/holesky","supported-networks/hyperliquid","supported-networks/immutable-zkevm","supported-networks/immutable-zkevm-testnet","supported-networks/ink","supported-networks/iotex-network","supported-networks/japan-open-chain","supported-networks/kaia","supported-networks/kakarot-starknet-sepolia","supported-networks/kroma","supported-networks/layeredge-testnet","supported-networks/lightlink-pegasus-testnet","supported-networks/lightlink-phoenix","supported-networks/linea","supported-networks/lisk","supported-networks/lukso","supported-networks/lukso-testnet","supported-networks/manta","supported-networks/manta-pacific-sepolia","supported-networks/mantle","supported-networks/megaeth-testnet","supported-networks/merlin","supported-networks/metall2","supported-networks/meter-mainnet","supported-networks/meter-testnet","supported-networks/mev-commit","supported-networks/mint-mainnet","supported-networks/mode","supported-networks/monad-testnet","supported-networks/moonbase-alpha","supported-networks/moonbeam","supported-networks/morph","supported-networks/nautilus","supported-networks/neo-x-testnet","supported-networks/nibiru-testnet","supported-networks/now-chaint","supported-networks/oasis-emerald","supported-networks/oasis-sapphire","supported-networks/onigiri-subnet","supported-networks/onigiri-test-subnet","supported-networks/ontology-mainnet","supported-networks/ontology-testnet","supported-networks/op-celestia-raspberry","supported-networks/opbnb","supported-networks/optimism","supported-networks/optimism-sepolia","supported-networks/optopia","supported-networks/peaq","supported-networks/plume","supported-networks/polygon","supported-networks/polygon-amoy","supported-networks/polygon-zkevm","supported-networks/polygon-zkevm-cardona-testnet","supported-networks/public-goods-network","supported-networks/pulsechain","supported-networks/puppynet-shibarium","supported-networks/ronin","supported-networks/rootstock","supported-networks/saakuru","supported-networks/satoshivm","supported-networks/scroll","supported-networks/scroll-sepolia","supported-networks/sepolia","supported-networks/shibarium","supported-networks/shimmer-evm","supported-networks/skale-europa","supported-networks/soneium","supported-networks/sonic","supported-networks/sophon","supported-networks/sophon-testnet","supported-networks/stratovm-testnet","supported-networks/superseed","supported-networks/superseed-sepolia-testnet","supported-networks/swell","supported-networks/taiko","supported-networks/tangle","supported-networks/tanssi-demo","supported-networks/taraxa","supported-networks/telos-evm-mainnet","supported-networks/telos-evm-testnet","supported-networks/torus-mainnet","supported-networks/torus-testnet","supported-networks/unichain","supported-networks/unichain-sepolia","supported-networks/unicorn-ultra-nebulas-testnet","supported-networks/velas-mainnet","supported-networks/viction","supported-networks/worldchain","supported-networks/x-layer-mainnet","supported-networks/x-layer-testnet","supported-networks/xdc","supported-networks/xdc-testnet","supported-networks/zeta","supported-networks/zeta-testnet","supported-networks/zircuit","supported-networks/zklink-nova-mainnet","supported-networks/zksync","supported-networks/zksync-sepolia-testnet","supported-networks/zora","supported-networks/zora-sepolia"]}
	// … other entries before …
	"supported-networks/crossfi-mainnet",
	"supported-networks/crossfi-testnet",
	// … other entries between …
	"supported-networks/now-chain",
	// … other entries after …

🤖 Prompt for AI Agents

In supported-networks.json around line 5, there is a duplicate slug
"supported-networks/crossfi-mainnet" and a likely typo
"supported-networks/now-chaint"; remove the duplicate entry so each slug appears
once and rename "now-chaint" to "supported-networks/now-chain" (then run a
uniqueness check/JSON lint to ensure no other duplicates or syntax issues).

[keenbeen32]

Fixing thi