chore: updated supported networks

[keenbeen32]

Rebuilt to update supported networks (needed to include celo).

Summary by CodeRabbit

• New Features

  • Added Gnosis Traces and Gnosistemp to HyperSync and HyperRPC supported networks.
  • Updated Hyperliquid to new network ID (999) with refreshed endpoints.

• Documentation

  • Added a Gnosistemp docs page (overview, tier, endpoints, config example, links, support).

• Chores

  • Expanded and reordered the supported-networks catalog (supported-networks.json) to include many additional networks.

[coderabbitai]

Walkthrough

Adds a new Gnosistemp network doc page, updates HyperRPC and HyperSync supported-networks docs (adds Gnosis Traces, adjusts Hyperliquid IDs/endpoints), and replaces/reorders entries in supported-networks.json. All changes are documentation/data-only; no code or public API changes.

Changes

Cohort / File(s)	Summary
New network doc page docs/HyperIndex/supported-networks/gnosistemp.md	Adds Gnosistemp documentation with front matter, HyperSync/HyperRPC endpoints, Tier, overview (HyperIndex/HyperSync/HyperRPC), YAML config example, links, and support contact.
HyperRPC/HyperSync docs updates docs/HyperSync/HyperRPC/hyperrpc-supported-networks.md, docs/HyperSync/hypersync-supported-networks.md	Adds Gnosis Traces (ID 100) entries and Gnosistemp references; updates Hyperliquid network ID from 645749 to 999 and adjusts alternate endpoints; other table rows unchanged.
Registry data refresh supported-networks.json	Replaces and reorders the supportedNetworks array, adding many network identifiers and reordering entries; JSON schema unchanged (data-only update).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• Config schema #687 — Overlapping edits to HyperRPC/HyperSync docs and Gnosis Traces/Gnosistemp entries.
• Developer update may 2025 blog #646 — Related modifications to supported-networks registry and documentation.
• llm docs revamp #673 — Parallel updates to supported-networks docs and the JSON registry.

Suggested reviewers

• moose-code
• DenhamPreen

Poem

I hop through docs with eager paws,
New traces logged and concise new laws;
Gnosistemp arrives, Hyperliquid shifts ID,
JSON rows reordered for all to see.
A tiny thump — the changelog sings! 🐇✨

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

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
envio-docs	Ready	Preview	Comment	Aug 27, 2025 10:31am

[DZakh]

This shouldn't be added

[DZakh]

Gnosis temp shouldn't be in the list

[DZakh]

Filter it out on the client, or ask Kelvin how to change the chain status to internal, so it's automatically skipped. the second option is better.

[coderabbitai]

Actionable comments posted: 3

Caution

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

⚠️ Outside diff range comments (3)

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

35-35: Typo: “Berachain Bartio” → “Berachain Artio”

Network name is “Artio”. Align with slugs used elsewhere.

-| Berachain Bartio     | 80084      | https://berachain-bartio.rpc.hypersync.xyz or https://80084.rpc.hypersync.xyz       |                 |
+| Berachain Artio      | 80084      | https://berachain-artio.rpc.hypersync.xyz or https://80084.rpc.hypersync.xyz        |                 |

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

43-43: Typo: “Berachain Bartio” → “Berachain Artio”

Fix name to the canonical “Artio”.

-| Berachain Bartio     | 80084      | https://berachain-bartio.hypersync.xyz or https://80084.hypersync.xyz               | 🎒   |                 |
+| Berachain Artio      | 80084      | https://berachain-artio.hypersync.xyz or https://80084.hypersync.xyz                | 🎒   |                 |

---

50-51: Remove unsupported Chainweb Testnet 20 & 21 entries

Verified that all four URLs—https://chainweb-testnet-20.hypersync.xyz, https://5920.hypersync.xyz, https://chainweb-testnet-21.hypersync.xyz, and https://5921.hypersync.xyz—return HTTP 404, confirming these networks aren’t actually supported. Please remove them from the supported-networks table.

• File: docs/HyperSync/hypersync-supported-networks.md
• Lines: 50–51

-| Chainweb Testnet 20  | 5920       | https://chainweb-testnet-20.hypersync.xyz or https://5920.hypersync.xyz             | 🪨   |                 |
-| Chainweb Testnet 21  | 5921       | https://chainweb-testnet-21.hypersync.xyz or https://5921.hypersync.xyz             | 🪨   |                 |

🧹 Nitpick comments (3)

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

12-18: Stale “starting June 2025” phrasing

It’s now after June 2025; rephrase to present tense to avoid confusion.

-:::caution API Tokens Recommended
-Requests without an API token will be rate limited starting **June 2025** (following the same schedule as [HyperSync](/docs/HyperSync/api-tokens)). Append your token to the endpoint URL to maintain full speed:
+:::caution API Tokens Recommended
+Requests without an API token are rate limited (same schedule as [HyperSync](/docs/HyperSync/api-tokens)). Append your token to the endpoint URL to maintain full speed:

---

57-58: Wrap RPC endpoints in angle brackets (MD034) & confirmed health
We verified each new endpoint by issuing a minimal JSON-RPC POST (web3_clientVersion) and all returned HTTP 200 (the 405 on HEAD is expected for JSON-RPC-only services). To satisfy markdownlint’s MD034 rule and keep the table style consistent, please wrap the bare URLs in angle brackets:

• File: docs/HyperSync/HyperRPC/hyperrpc-supported-networks.md (lines 57–58)
• Endpoints tested:

• https://gnosis-traces.rpc.hypersync.xyz → 200
• https://100-traces.rpc.hypersync.xyz → 200
• https://gnosistemp.rpc.hypersync.xyz → 200
• https://100101.rpc.hypersync.xyz → 200

Suggested diff:

-| Gnosis Traces        | 100        | https://gnosis-traces.rpc.hypersync.xyz or https://100-traces.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            |                 |
+| Gnosistemp           | 100101     | <https://gnosistemp.rpc.hypersync.xyz> or <https://100101.rpc.hypersync.xyz>        |                 |

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

22-22: Minor wording nit

Consider “Tier: GOLD 🏅” for consistency with other pages.

-GOLD 🏅
+Tier: GOLD 🏅

📜 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 483d6be.

📒 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

🧠 Learnings (1)

📚 Learning: 2025-07-29T14:30:03.677Z

Learnt from: DenhamPreen
PR: enviodev/docs#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:

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

🪛 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 (4)

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

61-61: Approve Hyperliquid ID update; wrap URLs to satisfy MD034

Verified that both endpoints respond with HTTP 405 to HEAD requests (indicating they exist), so wrapping the bare URLs in angle brackets will satisfy markdownlint’s MD034 rule.

• File: docs/HyperSync/HyperRPC/hyperrpc-supported-networks.md, line 61

-| Hyperliquid          | 999        | https://hyperliquid.rpc.hypersync.xyz or https://999.rpc.hypersync.xyz              |                 |
+| Hyperliquid          | 999        | <https://hyperliquid.rpc.hypersync.xyz> or <https://999.rpc.hypersync.xyz>          |                 |

---

42-43: Endpoints are live (405), not missing (404)

HEAD requests to the Chainweb Testnet 20/21 RPC URLs return HTTP 405 (Method Not Allowed), confirming the servers exist and correctly expect JSON-RPC POSTs rather than indicating a 404 Not Found. Therefore, these networks should remain in the “supported” table.

• https://chainweb-testnet-20.rpc.hypersync.xyz → 405
• https://5920.rpc.hypersync.xyz → 405
• https://chainweb-testnet-21.rpc.hypersync.xyz → 405
• https://5921.rpc.hypersync.xyz → 405

No removal needed.

Likely an incorrect or invalid review comment.

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

65-66: LGTM: New networks (Gnosis Traces, Gnosistemp)

Entries and endpoints align with HyperRPC doc and supported-networks.json.

---

69-69: LGTM: Hyperliquid ID updated to 999

Consistent with HyperRPC doc and endpoint aliasing.

[coderabbitai]

⚠️ Potential issue

Route mismatch: slug should include /supported-networks/

supported-networks.json references "supported-networks/gnosistemp". To avoid broken links, align the slug.

-slug: /gnosistemp
+slug: /supported-networks/gnosistemp

📝 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

	slug: /gnosistemp
	slug: /supported-networks/gnosistemp

🤖 Prompt for AI Agents

In docs/HyperIndex/supported-networks/gnosistemp.md around line 5, the
frontmatter slug is set to "/gnosistemp" but supported-networks.json expects
"supported-networks/gnosistemp"; update the slug to include the
supported-networks prefix (e.g., "/supported-networks/gnosistemp") so the route
matches the JSON reference and prevents broken links.

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Verify endpoints resolve

Quick check the two HyperSync and two HyperRPC endpoints return 200/3xx.

---

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail
for u in \
  https://gnosistemp.hypersync.xyz \
  https://100101.hypersync.xyz \
  https://gnosistemp.rpc.hypersync.xyz \
  https://100101.rpc.hypersync.xyz
do
  printf '%-45s %s\n' "$u" "$(curl -s -o /dev/null -w '%{http_code}' -I "$u")"
done

Length of output: 1339

---

Broken HyperSync/HyperRPC Endpoints in Docs

The HEAD checks for all four listed URLs fail to return any 2xx/3xx status:

• https://gnosistemp.hypersync.xyz → 000 (no response)
• https://100101.hypersync.xyz → 000 (no response)
• https://gnosistemp.rpc.hypersync.xyz → 405 (Method Not Allowed)
• https://100101.rpc.hypersync.xyz → 405 (Method Not Allowed)

Steps to resolve:

• Verify DNS and SSL configuration for the two HyperSync domains so they respond to requests.
• Ensure the HyperRPC endpoints accept at least HEAD (or fall back to GET) requests, or update the docs to link to working endpoints.
• Once endpoints are live and returning 2xx/3xx codes, re-run the check and update the documentation accordingly.

🤖 Prompt for AI Agents

docs/HyperIndex/supported-networks/gnosistemp.md lines 15-16: the documented
HyperSync and HyperRPC URLs are currently unreachable or returning non-2xx/3xx
responses; verify and fix the live endpoints or update the docs. Check DNS and
TLS for https://gnosistemp.hypersync.xyz and https://100101.hypersync.xyz so
they resolve and respond, and ensure the RPC hosts accept HEAD (or at least GET)
requests instead of returning 405; if the services are intentionally
unavailable, replace or remove the links and add working endpoints (or note
their deprecation) and then re-run the HEAD checks to confirm 2xx/3xx responses
before committing the doc change.

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Data issues: duplicate and inconsistent slugs; remove unsupported Chainweb testnets

• Duplicate entry: "supported-networks/crossfi-mainnet" appears twice.
• Inconsistent/typo: "supported-networks/berachain-bartio" (should be Artio; you already have "berachain-artio-testnet").
• Potential typo: "supported-networks/now-chaint" (please confirm correct slug exists).
• Unsupported per prior learning: "chainweb-testnet-20" and "chainweb-testnet-21" should be removed.

Minimal patch (subject to verification):

-..."supported-networks/crossfi-mainnet","supported-networks/crossfi-mainnet",...
+..."supported-networks/crossfi-mainnet",...
-...,"supported-networks/berachain-bartio",...
+...,
-...,"supported-networks/chainweb-testnet-20","supported-networks/chainweb-testnet-21",...
+...,
-...,"supported-networks/now-chaint",...
+...,"supported-networks/now-chain",...

---

🏁 Script executed:

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

# 1) Detect duplicates
echo "Duplicates in supported-networks.json:"
python - <<'PY'
import json,sys
data=json.load(open("supported-networks.json"))
arr=data["supportedNetworks"]
seen=set(); dups=set()
for x in arr:
    if x in seen: dups.add(x)
    seen.add(x)
print("\n".join(sorted(dups)) or "None")
PY

# 2) Ensure each slug has a corresponding doc page
echo -e "\nMissing doc pages for slugs:"
python - <<'PY'
import json,os
data=json.load(open("supported-networks.json"))
missing=[]
for slug in data["supportedNetworks"]:
    fname=os.path.join("docs","HyperIndex", slug + ".md")
    if not os.path.exists(fname):
        missing.append(slug)
print("\n".join(missing) or "None")
PY

Length of output: 241

---

Fix duplicate and slugs in supported-networks.json

The verification scripts confirm:

• A duplicate entry for supported-networks/crossfi-mainnet must be collapsed to a single occurrence.
• Every slug in supported-networks.json has a matching doc page, so renaming slugs will require corresponding updates in docs/HyperIndex.

Action items:

• Remove the extra "supported-networks/crossfi-mainnet".
• Rename the typo’d slugs to match their real network names:
  • Change supported-networks/berachain-bartio → supported-networks/berachain-artio
  • Change supported-networks/now-chaint → supported-networks/now-chain
• Drop the unsupported Chainweb testnets:
  • Remove supported-networks/chainweb-testnet-20
  • Remove supported-networks/chainweb-testnet-21

Minimal patch (apply alongside corresponding renames in docs/HyperIndex/supported-networks/*.md):

-..."supported-networks/crossfi-mainnet","supported-networks/crossfi-mainnet",...
+..."supported-networks/crossfi-mainnet",...
-...,"supported-networks/berachain-bartio",...
+...,"supported-networks/berachain-artio",...
-...,"supported-networks/chainweb-testnet-20","supported-networks/chainweb-testnet-21",...
+...,
-...,"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 in between … */
	"supported-networks/berachain-artio",
	/* … other entries in between … */
	"supported-networks/celo-alfajores-testnet",
	"supported-networks/chiliz",
	/* … other entries in between … */
	"supported-networks/now-chain",
	/* … other entries after … */
	]

🤖 Prompt for AI Agents

In supported-networks.json around line 5, the list contains a duplicate
"supported-networks/crossfi-mainnet", two typo’d slugs
("supported-networks/berachain-bartio" should be
"supported-networks/berachain-artio" and "supported-networks/now-chaint" should
be "supported-networks/now-chain"), and two unsupported Chainweb testnets
("supported-networks/chainweb-testnet-20" and
"supported-networks/chainweb-testnet-21") that must be removed; update the JSON
by deleting the extra "supported-networks/crossfi-mainnet" entry, replace the
two typo’d slugs with the corrected slugs, and remove both Chainweb testnet
entries, and then ensure corresponding renames (berachain-artio and now-chain)
are applied to docs/HyperIndex/supported-networks/*.md to keep slugs in sync.

[coderabbitai]

Actionable comments posted: 0

♻️ Duplicate comments (1)

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

57-57: Revisit adding “Gnosis Traces” (prefer marking chain as internal) + fix MD034 bare-URLs

Prior feedback said this shouldn’t be added. If the intent is to hide it, remove the row; if it’s ready for public, keep it but wrap URLs in angle brackets to satisfy markdownlint.

Option A — remove:

-| Gnosis Traces        | 100        | https://gnosis-traces.rpc.hypersync.xyz or https://100-traces.rpc.hypersync.xyz     |                 |

Option B — keep and fix lint:

-| Gnosis Traces        | 100        | https://gnosis-traces.rpc.hypersync.xyz or https://100-traces.rpc.hypersync.xyz     |                 |
+| Gnosis Traces        | 100        | <https://gnosis-traces.rpc.hypersync.xyz> or <https://100-traces.rpc.hypersync.xyz> |                 |

🧹 Nitpick comments (2)

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

60-60: Verify Hyperliquid chain ID change (645749 → 999) and fix MD034

Confirm 999 is the correct network ID across docs/data. Also wrap URLs to appease markdownlint.

-| Hyperliquid          | 999        | https://hyperliquid.rpc.hypersync.xyz or https://999.rpc.hypersync.xyz              |                 |
+| Hyperliquid          | 999        | <https://hyperliquid.rpc.hypersync.xyz> or <https://999.rpc.hypersync.xyz>          |                 |

---

12-18: Update time phrasing: rate limiting date is in the past

It’s now after June 2025. Adjust wording to avoid “starting …”.

-Requests without an API token will be rate limited starting **June 2025** (following the same schedule as [HyperSync](/docs/HyperSync/api-tokens)). Append your token to the endpoint URL to maintain full speed:
+Requests without an API token are rate limited since **June 2025** (following the same schedule as [HyperSync](/docs/HyperSync/api-tokens)). Append your token to the endpoint URL to maintain full speed:

📜 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 483d6be and d5fb761.

📒 Files selected for processing (3)

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

🚧 Files skipped from review as they are similar to previous changes (2)

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

🧰 Additional context used

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

[keenbeen32]

@DZakh Shot, I changed the tier to hidden and removed the md file.