Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded@keenbeen32 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 59 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (26)
WalkthroughAdds consolidated HyperRPC documentation and LLM-friendly MDX, integrates HyperRPC into Docusaurus (plugins, navbar, sidebars, homepage), extends the consolidation script to produce HyperRPC LLM output, updates supported-networks tables (remove Chainweb Testnet 21, add/update HyperSync entries), and adjusts endpoint update paths. Changes are docs/config/scripts-only. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant CLI as consolidate-hyperindex-docs.js
participant FS as Filesystem
participant SB as Sidebar Parser
participant OUT as docs/HyperRPC-LLM
Note over CLI,OUT: Consolidation flow extended for HyperRPC
CLI->>CLI: Parse args (--hyperrpc | --all)
alt process HyperRPC
CLI->>FS: Read docs/HyperRPC sourceDir
CLI->>SB: Parse sidebarsHyperRPC.js for order
SB-->>CLI: Return file order (or fail -> fallback to alpha)
CLI->>CLI: Build combined MDX (set id/title/sidebar_label/slug)
CLI->>OUT: Write hyperrpc-complete.mdx
OUT-->>CLI: Confirm write
else other product flows
CLI->>CLI: Run existing HyperIndex/HyperSync consolidation
end
Note over CLI: Exports include consolidateHyperRPCDocs()
sequenceDiagram
autonumber
participant Script as scripts/update-endpoints.js
participant MD as docs/HyperRPC/hyperrpc-supported-networks.md
Note over Script,MD: Update path references for HyperRPC networks
Script->>MD: Replace HyperRPC paths from /docs/HyperSync/... to /docs/HyperRPC/...
MD-->>Script: Save updated file
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
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. 🧪 Early access (Sonnet 4.5): enabledWe are currently testing the Sonnet 4.5 model, which is expected to improve code review quality. However, this model may lead to increased noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience. Note:
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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)
docusaurus.config.js (1)
228-230: Update redirect target to HyperRPC section
In docusaurus.config.js at line 229, changeto: "/docs/HyperSync/overview-hyperrpc",to
to: "/docs/HyperRPC/overview-hyperrpc",
🧹 Nitpick comments (3)
supported-networks.json (1)
5-5: Network list update verified; reformat JSON for clarity– Removed
chainweb-testnet-21; addedany-evm-with-rpc,local-anvil,local-hardhat(total networks: 192).
– Suggest reformattingsupported-networks.jsonto list each network on its own line (sorted) for better readability and diff clarity.scripts/consolidate-hyperindex-docs.js (1)
244-283: Consider refactoring nested ternaries for better readability.The HyperRPC integration correctly extends the existing pattern, but the nested ternary operators (lines 250-278) are becoming difficult to read with three conditions. Consider refactoring to use a lookup object or switch statement:
-id: ${isHyperIndex ? "hyperindex-complete" : isHyperSync ? "hypersync-complete" : "hyperrpc-complete"} +id: ${getDocId(isHyperIndex, isHyperSync, isHyperRPC)}Where
getDocIdreturns the appropriate ID based on a cleaner conditional structure.sidebarsHyperRPC.js (1)
10-14: Remove leftover commented code.The commented block references HyperSync-LLM documentation, which appears to be leftover code from copy-pasting another sidebar configuration. This should be removed to avoid confusion.
Apply this diff to remove the incorrect commented code:
- // { - // type: "link", - // label: "LLM Documentation", - // href: "/docs/HyperSync-LLM/hypersync-complete", - // },
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (14)
docs/HyperIndex-LLM/hyperindex-complete.mdx(13 hunks)docs/HyperRPC-LLM/hyperrpc-complete.mdx(1 hunks)docs/HyperRPC/hyperrpc-supported-networks.md(0 hunks)docs/HyperSync-LLM/hypersync-complete.mdx(3 hunks)docs/HyperSync/hypersync-supported-networks.md(0 hunks)docusaurus.config.js(3 hunks)docusaurus.config.llm.js(2 hunks)scripts/consolidate-hyperindex-docs.js(3 hunks)scripts/update-endpoints.js(1 hunks)sidebarsHyperRPC.js(1 hunks)sidebarsHyperRPCLLM.js(1 hunks)sidebarsHyperSync.js(1 hunks)src/pages/index.js(2 hunks)supported-networks.json(1 hunks)
💤 Files with no reviewable changes (2)
- docs/HyperSync/hypersync-supported-networks.md
- docs/HyperRPC/hyperrpc-supported-networks.md
🧰 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-LLM/hypersync-complete.mdx
🧬 Code graph analysis (1)
scripts/consolidate-hyperindex-docs.js (1)
scripts/update-endpoints.js (3)
path(2-2)outputDir(355-358)fs(1-1)
🔇 Additional comments (17)
scripts/update-endpoints.js (1)
172-172: Approve path updateVerified that
docs/HyperRPC/hyperrpc-supported-networks.mdexists at the new location and the olddocs/HyperSync/HyperRPC/hyperrpc-supported-networks.mdhas been removed.sidebarsHyperSync.js (1)
18-26: HyperRPC navigation verified: sidebarsHyperRPC.js, docs/HyperRPC, and the corresponding plugin entries in docusaurus.config.js are all correctly configured.docs/HyperSync-LLM/hypersync-complete.mdx (1)
2046-2094: Verify the Hyperliquid network ID change (645749 → 999).The network table updates look good overall, including:
- Addition of Chainweb Testnet 22, 23, 24
- Addition of Damon network
- Addition of Sentient Testnet
- Removal of Chainweb Testnet 21 (correct per learnings)
However, the Hyperliquid network ID change from
645749to999on line 2066 is a significant breaking change. Please confirm this is intentional and that any dependent systems or users have been notified of this change.Based on learnings (regarding Chainweb Testnet 21 removal).
docs/HyperRPC-LLM/hyperrpc-complete.mdx (3)
1-140: LGTM! Clear and comprehensive overview.The documentation effectively:
- Distinguishes HyperRPC from HyperSync with clear guidance on when to use each
- Provides performance context (5x improvement)
- Lists supported methods clearly
- Includes practical getting started steps with code example
- Appropriately warns about development status and limitations
161-249: Network table is consistent with HyperSync.The supported networks table correctly mirrors the HyperSync network list with appropriate RPC endpoints. Notable entries include:
- Hyperliquid with ID 999 (matching HyperSync)
- New Chainweb Testnet networks (22, 23, 24)
- Damon and Sentient Testnet additions
- Correct exclusion of Chainweb Testnet 21
The URL pattern
[network].rpc.hypersync.xyzis consistent throughout.
94-128: Code example looks good, verify rate limiting timeline.The JavaScript fetch example is well-structured and demonstrates proper HyperRPC usage with
eth_getLogs. The API token guidance is clear.However, verify that the "June 2025" rate limiting timeline at line 96 is still accurate, as the current date context shows September 2025.
scripts/consolidate-hyperindex-docs.js (2)
405-438: LGTM! Consistent implementation following established patterns.The
consolidateHyperRPCDocs()function correctly:
- Mirrors the structure of
consolidateHyperSyncDocs()- Creates the output directory if it doesn't exist
- Parses the HyperRPC sidebar for file ordering
- Falls back to alphabetical order if parsing fails
- Reuses
parseHyperSyncSidebarOrder()with a clear explanatory commentThe implementation is clean and consistent with the existing codebase.
454-471: LGTM! Complete CLI integration.The HyperRPC consolidation is properly integrated:
- New
--hyperrpcflag follows the same pattern as existing flags- Included in the
--allconsolidation workflow- Exported in
module.exportsfor external usageThe implementation is complete and consistent with existing functionality.
src/pages/index.js (1)
32-34: LGTM! Clean integration of HyperRPC navigation.The new HyperRPC documentation links follow the established pattern for HyperIndex and HyperSync, maintaining consistency across the homepage navigation.
Also applies to: 57-62
sidebarsHyperRPCLLM.js (1)
1-5: LGTM! Sidebar configuration matches established pattern.The HyperRPC-LLM sidebar configuration is consistent with the existing HyperIndex-LLM and HyperSync-LLM sidebar structures.
docusaurus.config.llm.js (2)
72-76: LGTM! Navbar configuration is correct.The HyperRPC Docs navbar item follows the established pattern and correctly links to the HyperRPC-LLM documentation.
162-173: LGTM! Plugin configuration is consistent.The HyperRPC-LLM plugin block is properly configured with the correct path, route base path, and sidebar reference, matching the pattern of existing LLM documentation plugins.
sidebarsHyperRPC.js (1)
1-9: LGTM! Active sidebar configuration is correct.The HyperRPC sidebar properly includes the overview, supported networks page, and a link to the LLM documentation.
docusaurus.config.js (4)
326-330: LGTM! Navbar correctly updated for HyperRPC.The HyperRPC Docs navbar item is properly configured and follows the established pattern.
430-436: Commented versions block appears unrelated to PR objective.The HyperIndex versions configuration has been commented out, but this change doesn't seem related to separating HyperRPC documentation. Verify whether this change was intentional for this PR.
438-456: LGTM! HyperRPC plugin properly configured.The HyperRPC documentation plugin is correctly set up with appropriate paths and sidebar references. The commented
disableVersioningflag at line 448 appears to be a placeholder for future versioning configuration, which is acceptable.
481-492: LGTM! HyperRPC-LLM plugin configuration is correct.The HyperRPC-LLM documentation plugin mirrors the structure of existing LLM documentation plugins and is properly configured.
|
|
||
| To ensure continued access to HyperSync, set an Envio API token in your environment. | ||
|
|
||
| - Use `ENVIO_API_TOKEN` to provide your token at runtime | ||
| - See the API Tokens guide for how to generate a token: API Tokens | ||
|
|
||
| ## Envio-specific environment variables | ||
|
|
||
| The following variables are used by HyperIndex: | ||
|
|
||
| - `ENVIO_API_TOKEN`: API token for HyperSync access (required for continued access in self-hosted deployments) | ||
| - `ENVIO_HASURA`: Set to `false` to disable Hasura integration for self-hosted indexers | ||
|
|
||
| - `MAX_BATCH_SIZE`: Size of the in-memory batch before writing to the database. Default: `5000`. Set to `1` to help isolate which event or data save is causing Postgres write errors. | ||
|
|
||
| - `ENVIO_PG_PORT`: Port for the Postgres service used by HyperIndex during local development | ||
| - `ENVIO_PG_PASSWORD`: Postgres password (self-hosted) | ||
| - `ENVIO_PG_USER`: Postgres username (self-hosted) | ||
| - `ENVIO_PG_DATABASE`: Postgres database name (self-hosted) | ||
| - `ENVIO_PG_PUBLIC_SCHEMA`: Postgres schema name override for the generated/public schema |
There was a problem hiding this comment.
Clarify env-var naming to avoid direct contradiction
Right above this list we tell readers “All environment variables used by Envio must be prefixed with ENVIO_,” but then we introduce MAX_BATCH_SIZE (and show it later in the example) without that prefix. That leaves users not knowing whether the real variable is ENVIO_MAX_BATCH_SIZE, MAX_BATCH_SIZE, or if it’s an intentional exception. Please update either the naming or the wording so the rule and the example match. citeturn0commentary0
🤖 Prompt for AI Agents
docs/HyperIndex-LLM/hyperindex-complete.mdx around lines 1755 to 1774: the doc
contradicts the earlier statement that all Envio env vars are prefixed with
ENVIO_ by listing MAX_BATCH_SIZE without the prefix; either make it consistent
by renaming the variable everywhere to ENVIO_MAX_BATCH_SIZE (update the list,
descriptions, and any later examples to show ENVIO_MAX_BATCH_SIZE with Default:
5000 and usage guidance) or explicitly call out that MAX_BATCH_SIZE is a
documented exception (add one sentence clarifying the exception and why it
exists) so the rule and examples no longer conflict.
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docusaurus.config.js(4 hunks)
🔇 Additional comments (4)
docusaurus.config.js (4)
220-221: LGTM! Redirects correctly migrate HyperRPC URLs.The redirects properly handle the migration of HyperRPC documentation from the HyperSync section to its own dedicated section, ensuring backward compatibility for old URLs.
Also applies to: 228-229
326-330: LGTM! Navbar item follows established pattern.The new HyperRPC Docs navbar item is correctly configured and consistent with the existing HyperIndex and HyperSync items.
430-436: LGTM! Comment reorganization has no functional impact.The reorganization of the commented-out versions block is a harmless refactor that maintains the placeholder for future versioning configuration.
481-492: Approve plugin configurationHyperRPC-LLM plugin block matches existing LLM plugin patterns and sidebar file
sidebarsHyperRPCLLM.jswas confirmed to exist.
| [ | ||
| "@docusaurus/plugin-content-docs", | ||
| { | ||
| id: "HyperRPC", | ||
| path: "docs/HyperRPC", | ||
| routeBasePath: "docs/HyperRPC", | ||
| sidebarPath: require.resolve("./sidebarsHyperRPC.js"), | ||
| editUrl: "https://github.com/enviodev/docs/edit/main/", | ||
| showLastUpdateAuthor: false, | ||
| showLastUpdateTime: false, | ||
| //disableVersioning: true, | ||
| // versions: { | ||
| // current: { | ||
| // label: "v2", | ||
| // path: "", | ||
| // }, | ||
| // }, | ||
| }, | ||
| ], |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
🧩 Analysis chain
Verify versioning configuration for HyperRPC.
The HyperRPC plugin configuration follows the established pattern correctly. However, note that disableVersioning is commented out (line 448), whereas the HyperIndex plugin has it explicitly enabled (line 429). Please confirm whether versioning should be disabled for HyperRPC to maintain consistency.
Run the following script to check if the referenced sidebar file exists:
🏁 Script executed:
#!/bin/bash
# Verify sidebarsHyperRPC.js exists
fd -t f "^sidebarsHyperRPC\.js$"Length of output: 19
Enable disableVersioning for HyperRPC plugin.
Add disableVersioning: true to the HyperRPC plugin configuration to match the HyperIndex plugin and ensure consistent versioning behavior across your documentation plugins.
🤖 Prompt for AI Agents
In docusaurus.config.js around lines 438 to 456, the HyperRPC plugin config is
missing disableVersioning: true which causes inconsistent versioning behavior
compared to HyperIndex; update the plugin options by adding disableVersioning:
true (uncommenting or inserting it within the options object for the
"@docusaurus/plugin-content-docs" entry with id "HyperRPC") so both
documentation plugins use consistent versioning settings.
There was a problem hiding this comment.
Actionable comments posted: 15
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
docs/HyperIndex/supported-networks/bsc.md (1)
55-57: Update configuration file documentation link
In docs/HyperIndex/supported-networks/bsc.md (line 57), change/docs/HyperIndex/configuration-fileto/docs/HyperIndex/Guides/configuration-fileto match the actual file location.docs/HyperIndex/supported-networks/chainweb-testnet-20.md (1)
1-64: Remove unsupported Chainweb Testnet 20 & 21 documentation.Both Testnet 20’s HyperSync endpoint returns HTTP 404 (and its HyperRPC HEAD returns 405), and Testnet 21’s HyperSync endpoint is likewise non-functional. Remove the files docs/HyperIndex/supported-networks/chainweb-testnet-20.md and docs/HyperIndex/supported-networks/chainweb-testnet-21.md.
🧹 Nitpick comments (3)
docs/HyperIndex/supported-networks/fuel-testnet.md (1)
14-16: Consider replacing "undefined" placeholders with actual values.The Chain ID and fallback URLs contain "undefined" as placeholder values. While these are pre-existing issues not introduced by this PR, consider updating them with the actual Fuel Testnet chain ID to improve documentation accuracy.
docs/HyperIndex/supported-networks/bsc.md (1)
42-42: Minor: Inconsistent capitalization in comment.The comment uses "Bsc" while other parts of the document use "BSC" (line 8 title) and "Bsc" (line 3-4 metadata, line 10 heading). Consider standardizing to "BSC" for the chain name throughout the document for consistency.
- - id: 56 # Bsc + - id: 56 # BSCdocs/HyperIndex/supported-networks/zeta.md (1)
30-30: Ensure the Envio design paragraph is consistently present across all network documentation.
It appears in only 109 of 220 files; please add it to the remaining docs or clarify any intentional omissions.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (87)
docs/HyperIndex/supported-networks/abstract.md(1 hunks)docs/HyperIndex/supported-networks/arbitrum-nova.md(1 hunks)docs/HyperIndex/supported-networks/arbitrum-sepolia.md(1 hunks)docs/HyperIndex/supported-networks/arbitrum.md(1 hunks)docs/HyperIndex/supported-networks/aurora-turbo.md(1 hunks)docs/HyperIndex/supported-networks/aurora.md(1 hunks)docs/HyperIndex/supported-networks/avalanche.md(1 hunks)docs/HyperIndex/supported-networks/base-sepolia.md(1 hunks)docs/HyperIndex/supported-networks/base.md(1 hunks)docs/HyperIndex/supported-networks/berachain-bartio.md(1 hunks)docs/HyperIndex/supported-networks/berachain.md(1 hunks)docs/HyperIndex/supported-networks/blast-sepolia.md(1 hunks)docs/HyperIndex/supported-networks/blast.md(1 hunks)docs/HyperIndex/supported-networks/boba.md(1 hunks)docs/HyperIndex/supported-networks/bsc-testnet.md(1 hunks)docs/HyperIndex/supported-networks/bsc.md(1 hunks)docs/HyperIndex/supported-networks/celo.md(1 hunks)docs/HyperIndex/supported-networks/chainweb-testnet-20.md(1 hunks)docs/HyperIndex/supported-networks/chainweb-testnet-22.md(1 hunks)docs/HyperIndex/supported-networks/chainweb-testnet-23.md(1 hunks)docs/HyperIndex/supported-networks/chainweb-testnet-24.md(1 hunks)docs/HyperIndex/supported-networks/chiliz.md(1 hunks)docs/HyperIndex/supported-networks/citrea-testnet.md(1 hunks)docs/HyperIndex/supported-networks/curtis.md(1 hunks)docs/HyperIndex/supported-networks/cyber.md(1 hunks)docs/HyperIndex/supported-networks/damon.md(1 hunks)docs/HyperIndex/supported-networks/eth.md(1 hunks)docs/HyperIndex/supported-networks/fantom.md(1 hunks)docs/HyperIndex/supported-networks/flare.md(1 hunks)docs/HyperIndex/supported-networks/fraxtal.md(1 hunks)docs/HyperIndex/supported-networks/fuel-mainnet.md(1 hunks)docs/HyperIndex/supported-networks/fuel-testnet.md(1 hunks)docs/HyperIndex/supported-networks/fuji.md(1 hunks)docs/HyperIndex/supported-networks/galadriel-devnet.md(1 hunks)docs/HyperIndex/supported-networks/gnosis-chiado.md(1 hunks)docs/HyperIndex/supported-networks/gnosis.md(1 hunks)docs/HyperIndex/supported-networks/harmony-shard-0.md(1 hunks)docs/HyperIndex/supported-networks/holesky.md(1 hunks)docs/HyperIndex/supported-networks/hyperliquid.md(1 hunks)docs/HyperIndex/supported-networks/ink.md(1 hunks)docs/HyperIndex/supported-networks/kroma.md(1 hunks)docs/HyperIndex/supported-networks/linea.md(1 hunks)docs/HyperIndex/supported-networks/lisk.md(1 hunks)docs/HyperIndex/supported-networks/lukso-testnet.md(1 hunks)docs/HyperIndex/supported-networks/lukso.md(1 hunks)docs/HyperIndex/supported-networks/manta.md(1 hunks)docs/HyperIndex/supported-networks/mantle.md(1 hunks)docs/HyperIndex/supported-networks/megaeth-testnet.md(1 hunks)docs/HyperIndex/supported-networks/merlin.md(1 hunks)docs/HyperIndex/supported-networks/metall2.md(1 hunks)docs/HyperIndex/supported-networks/mev-commit.md(1 hunks)docs/HyperIndex/supported-networks/mode.md(1 hunks)docs/HyperIndex/supported-networks/monad-testnet.md(1 hunks)docs/HyperIndex/supported-networks/moonbase-alpha.md(1 hunks)docs/HyperIndex/supported-networks/moonbeam.md(1 hunks)docs/HyperIndex/supported-networks/morph.md(1 hunks)docs/HyperIndex/supported-networks/opbnb.md(1 hunks)docs/HyperIndex/supported-networks/optimism-sepolia.md(1 hunks)docs/HyperIndex/supported-networks/optimism.md(1 hunks)docs/HyperIndex/supported-networks/plume.md(1 hunks)docs/HyperIndex/supported-networks/polygon-amoy.md(1 hunks)docs/HyperIndex/supported-networks/polygon-zkevm.md(1 hunks)docs/HyperIndex/supported-networks/polygon.md(1 hunks)docs/HyperIndex/supported-networks/rootstock.md(1 hunks)docs/HyperIndex/supported-networks/saakuru.md(1 hunks)docs/HyperIndex/supported-networks/scroll.md(1 hunks)docs/HyperIndex/supported-networks/sentient-testnet.md(1 hunks)docs/HyperIndex/supported-networks/sepolia.md(1 hunks)docs/HyperIndex/supported-networks/shimmer-evm.md(1 hunks)docs/HyperIndex/supported-networks/soneium.md(1 hunks)docs/HyperIndex/supported-networks/sonic.md(1 hunks)docs/HyperIndex/supported-networks/sophon-testnet.md(1 hunks)docs/HyperIndex/supported-networks/sophon.md(1 hunks)docs/HyperIndex/supported-networks/superseed.md(1 hunks)docs/HyperIndex/supported-networks/swell.md(1 hunks)docs/HyperIndex/supported-networks/tangle.md(1 hunks)docs/HyperIndex/supported-networks/taraxa.md(1 hunks)docs/HyperIndex/supported-networks/unichain-sepolia.md(1 hunks)docs/HyperIndex/supported-networks/unichain.md(1 hunks)docs/HyperIndex/supported-networks/worldchain.md(1 hunks)docs/HyperIndex/supported-networks/xdc-testnet.md(1 hunks)docs/HyperIndex/supported-networks/xdc.md(1 hunks)docs/HyperIndex/supported-networks/zeta.md(1 hunks)docs/HyperIndex/supported-networks/zircuit.md(1 hunks)docs/HyperIndex/supported-networks/zksync.md(1 hunks)docs/HyperIndex/supported-networks/zora.md(1 hunks)scripts/update-endpoints.js(2 hunks)
✅ Files skipped from review due to trivial changes (25)
- docs/HyperIndex/supported-networks/merlin.md
- docs/HyperIndex/supported-networks/xdc.md
- docs/HyperIndex/supported-networks/galadriel-devnet.md
- docs/HyperIndex/supported-networks/monad-testnet.md
- docs/HyperIndex/supported-networks/arbitrum-nova.md
- docs/HyperIndex/supported-networks/gnosis.md
- docs/HyperIndex/supported-networks/sepolia.md
- docs/HyperIndex/supported-networks/blast-sepolia.md
- docs/HyperIndex/supported-networks/polygon.md
- docs/HyperIndex/supported-networks/plume.md
- docs/HyperIndex/supported-networks/fraxtal.md
- docs/HyperIndex/supported-networks/chainweb-testnet-24.md
- docs/HyperIndex/supported-networks/berachain-bartio.md
- docs/HyperIndex/supported-networks/chiliz.md
- docs/HyperIndex/supported-networks/gnosis-chiado.md
- docs/HyperIndex/supported-networks/xdc-testnet.md
- docs/HyperIndex/supported-networks/flare.md
- docs/HyperIndex/supported-networks/cyber.md
- docs/HyperIndex/supported-networks/swell.md
- scripts/update-endpoints.js
- docs/HyperIndex/supported-networks/sonic.md
- docs/HyperIndex/supported-networks/superseed.md
- docs/HyperIndex/supported-networks/base.md
- docs/HyperIndex/supported-networks/polygon-zkevm.md
- docs/HyperIndex/supported-networks/hyperliquid.md
🧰 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/HyperIndex/supported-networks/chainweb-testnet-22.mddocs/HyperIndex/supported-networks/chainweb-testnet-20.mddocs/HyperIndex/supported-networks/chainweb-testnet-23.md
🔇 Additional comments (54)
docs/HyperIndex/supported-networks/linea.md (1)
26-26: LGTM!The HyperRPC documentation link has been correctly updated to point to its new dedicated section, consistent with the PR's objective to separate HyperRPC documentation from HyperSync.
docs/HyperIndex/supported-networks/unichain-sepolia.md (1)
26-26: LGTM! Documentation link correctly updated.The HyperRPC documentation link has been properly updated to reflect the new dedicated HyperRPC section, aligning with the PR objective to separate HyperRPC from HyperSync documentation.
docs/HyperIndex/supported-networks/moonbase-alpha.md (1)
26-26: LGTM! Link correctly updated to reflect new HyperRPC section.The documentation link has been properly updated to point to the new HyperRPC documentation section, aligning with the PR's objective of making HyperRPC its own standalone section.
docs/HyperIndex/supported-networks/zksync.md (1)
26-26: LGTM! Link update correctly reflects the new HyperRPC documentation structure.The HyperRPC link has been properly updated to point to its new dedicated section at
/docs/HyperRPC/overview-hyperrpc, which aligns with the PR objective of making HyperRPC its own documentation section alongside HyperIndex and HyperSync.docs/HyperIndex/supported-networks/mantle.md (1)
26-26: LGTM! Link correctly updated to new HyperRPC section.The HyperRPC link path has been appropriately updated to reflect the new documentation structure where HyperRPC is its own section, consistent with HyperIndex and HyperSync.
docs/HyperIndex/supported-networks/ink.md (1)
26-26: LGTM! Link update aligns with new HyperRPC documentation structure.The hyperlink has been correctly updated to reflect HyperRPC's new position as an independent documentation section, matching the same pattern as HyperIndex and HyperSync links.
docs/HyperIndex/supported-networks/morph.md (1)
26-26: LGTM!The HyperRPC documentation link has been correctly updated to reflect its new location as a standalone section, maintaining consistency with the HyperIndex and HyperSync link patterns.
docs/HyperIndex/supported-networks/rootstock.md (1)
26-26: LGTM!The HyperRPC link has been correctly updated to point to its new dedicated section at
/docs/HyperRPC/overview-hyperrpc, which aligns with the PR objective of making HyperRPC its own documentation section alongside HyperSync and HyperIndex.docs/HyperIndex/supported-networks/blast.md (1)
26-26: LGTM! Documentation link correctly updated.The HyperRPC documentation link has been properly updated to reflect the new structure where HyperRPC is its own section, aligning with the PR objective.
docs/HyperIndex/supported-networks/citrea-testnet.md (1)
26-26: LGTM! Link correctly updated to new HyperRPC section.The documentation link has been properly updated to reflect the new HyperRPC documentation structure, aligning with the PR's objective to make HyperRPC its own section.
docs/HyperIndex/supported-networks/boba.md (1)
26-26: LGTM! Link correctly updated to reflect HyperRPC's new section.The documentation link has been properly updated from
/docs/HyperSync/overview-hyperrpcto/docs/HyperRPC/overview-hyperrpc, aligning with the PR's objective of making HyperRPC its own documentation section.docs/HyperIndex/supported-networks/bsc-testnet.md (1)
26-26: LGTM! Link correctly updated to new HyperRPC documentation path.The documentation link has been properly updated to reflect HyperRPC's new dedicated section structure, aligning with the PR's objective of separating HyperRPC documentation from HyperSync.
docs/HyperIndex/supported-networks/fuel-mainnet.md (1)
26-26: LGTM! Link correctly updated to point to HyperRPC docs.The HyperRPC documentation link now correctly points to its own section (
/docs/HyperRPC/overview-hyperrpc), aligning with the PR's objective of establishing HyperRPC as a standalone documentation section.docs/HyperIndex/supported-networks/metall2.md (1)
26-26: LGTM! Documentation link correctly updated.The HyperRPC documentation link has been properly updated to reflect the new standalone HyperRPC section, aligning with the PR's objective to separate HyperRPC from HyperSync documentation.
docs/HyperIndex/supported-networks/kroma.md (1)
26-26: LGTM! Documentation link correctly updated.The HyperRPC documentation link has been properly updated to reflect the new structure where HyperRPC is its own section rather than being nested under HyperSync. This aligns well with the PR objective and maintains consistency with how HyperIndex and HyperSync are referenced.
docs/HyperIndex/supported-networks/holesky.md (1)
26-26: LGTM! Link correctly updated to reflect HyperRPC's new section.The HyperRPC documentation link has been properly updated from the HyperSync section to its own dedicated section, aligning with the PR's objective to make HyperRPC a standalone documentation area.
docs/HyperIndex/supported-networks/chainweb-testnet-22.md (1)
26-26: LGTM! Documentation link correctly updated.The HyperRPC documentation link has been properly updated to reflect the new standalone section structure, consistent with the PR objective.
docs/HyperIndex/supported-networks/opbnb.md (1)
26-26: LGTM! Link correction aligns with HyperRPC restructuring.The update from the malformed
/docs/HyperHTTP?link to/docs/HyperRPC/overview-hyperrpccorrectly establishes HyperRPC as its own documentation section, maintaining consistency with the HyperIndex and HyperSync link patterns on the same line.docs/HyperIndex/supported-networks/harmony-shard-0.md (1)
26-26: LGTM! HyperRPC link is correctly structured.The link to HyperRPC documentation (
/docs/HyperRPC/overview-hyperrpc) is consistent with the PR objective of making HyperRPC its own section and aligns with the new documentation structure.docs/HyperIndex/supported-networks/moonbeam.md (1)
26-26: LGTM! Link update aligns with HyperRPC documentation restructuring.The HyperRPC link now correctly points to its own dedicated documentation section (
/docs/HyperRPC/overview-hyperrpc), consistent with how HyperIndex and HyperSync are organized. This improves documentation clarity and navigation.docs/HyperIndex/supported-networks/shimmer-evm.md (2)
26-26: LGTM! Link correctly updated to new HyperRPC section.The HyperRPC link has been properly updated to reflect the new documentation structure where HyperRPC is now its own section rather than being nested under HyperSync.
30-30: LGTM! Good addition of feature highlights.The new sentence effectively summarizes Envio's key capabilities and is well-placed in the documentation flow.
docs/HyperIndex/supported-networks/aurora.md (1)
26-26: LGTM! Link update aligns with new documentation structure.The HyperRPC documentation link has been correctly updated to reflect the new standalone HyperRPC section, maintaining consistency with the other product documentation links.
docs/HyperIndex/supported-networks/fuji.md (1)
26-26: LGTM! Documentation link correctly updated.The HyperRPC link has been properly updated to reflect its new location as an independent documentation section, maintaining consistency with the HyperIndex and HyperSync link patterns.
docs/HyperIndex/supported-networks/megaeth-testnet.md (1)
26-26: LGTM! Documentation link correctly updated.The HyperRPC documentation link has been properly updated to reflect the new documentation structure where HyperRPC is its own section. The link now correctly points to
/docs/HyperRPC/overview-hyperrpcinstead of the previous/docs/HyperSync/overview-hyperrpc, aligning with the PR's objective to make HyperRPC independent from HyperSync documentation.docs/HyperIndex/supported-networks/avalanche.md (1)
26-26: LGTM! HyperRPC link correctly updated to its new section.The documentation link has been properly updated to point to the new dedicated HyperRPC section, which aligns with the PR's objective of separating HyperRPC documentation from HyperSync.
docs/HyperIndex/supported-networks/berachain.md (2)
26-26: LGTM! Link correctly updated to reflect HyperRPC's new documentation section.The HyperRPC documentation link now properly points to
/docs/HyperRPC/overview-hyperrpc, aligning with the PR's objective to make HyperRPC its own section and maintaining consistency with the HyperIndex and HyperSync link patterns.
30-30: LGTM! Helpful feature description added.The new sentence effectively highlights key Envio features (automatic code generation, flexible language support, multi-chain data aggregation, and hosted service) that are relevant to developers evaluating the platform. The placement flows naturally within the Overview section.
docs/HyperIndex/supported-networks/fuel-testnet.md (1)
26-26: LGTM! Link correctly updated to reflect new HyperRPC section.The HyperRPC documentation link has been properly updated to point to the new dedicated HyperRPC section, aligning with the PR's objective of making HyperRPC its own documentation section.
docs/HyperIndex/supported-networks/manta.md (1)
26-26: HyperRPC documentation link is valid Verified that docs/HyperRPC/overview-hyperrpc.md exists.docs/HyperIndex/supported-networks/scroll.md (1)
26-26: Approve link update; target file exists.docs/HyperIndex/supported-networks/optimism-sepolia.md (2)
30-32: LGTM! Clear and helpful additions.The new paragraphs effectively communicate Envio's design goals and provide clear guidance for users to get started. The content is well-written and adds value to the documentation.
26-26: LGTM — HyperRPC link verified.
The updated link correctly points to the existing HyperRPC overview file, aligning with the PR objectives.docs/HyperIndex/supported-networks/taraxa.md (1)
26-26: Approve HyperRPC link updateThe updated link correctly points to
docs/HyperRPC/overview-hyperrpc.md, which exists.docs/HyperIndex/supported-networks/mode.md (1)
26-26: Approve HyperRPC link update
The link now correctly points to the newdocs/HyperRPC/overview-hyperrpc.mdfile, which exists.docs/HyperIndex/supported-networks/mev-commit.md (1)
26-26: Approve HyperRPC link update
The link/docs/HyperRPC/overview-hyperrpcexists (docs/HyperRPC/overview-hyperrpc.md). No further changes needed.docs/HyperIndex/supported-networks/lukso.md (1)
26-26: HyperRPC link validated
The/docs/HyperRPC/overview-hyperrpctarget exists (docs/HyperRPC/overview-hyperrpc.md) and aligns with the PR’s restructuring. No further changes needed.docs/HyperIndex/supported-networks/zircuit.md (2)
30-30: LGTM!The added sentence effectively highlights Envio's key benefits and fits well within the documentation flow.
26-26: HyperRPC overview link is correctThe link to
/docs/HyperRPC/overview-hyperrpcmatches the actualoverview-hyperrpc.mdfile in thedocs/HyperRPC/directory.docs/HyperIndex/supported-networks/chainweb-testnet-23.md (2)
26-26: LGTM! Link update aligns with the new HyperRPC section structure.The documentation link has been correctly updated to reflect HyperRPC as its own section, consistent with the PR objectives.
16-16: HyperRPC endpoint functionality verified for Chainweb Testnet 23: Both URLs returned HTTP 200 for an eth_blockNumber JSON-RPC request; ready to merge.docs/HyperIndex/supported-networks/celo.md (1)
26-26: LGTM! HyperRPC link correctly updated.The documentation link has been properly updated to reflect HyperRPC's new location as its own section, aligning with the PR objectives.
docs/HyperIndex/supported-networks/soneium.md (1)
26-26: LGTM! HyperRPC link correctly updated.The documentation link update is consistent with the broader restructuring effort to make HyperRPC its own documentation section.
docs/HyperIndex/supported-networks/base-sepolia.md (1)
26-26: LGTM! HyperRPC link correctly updated.The documentation link has been properly updated to point to HyperRPC's new dedicated section.
docs/HyperIndex/supported-networks/arbitrum-sepolia.md (1)
26-26: LGTM! HyperRPC link correctly updated.The documentation link update aligns with the PR's objective to establish HyperRPC as a standalone documentation section.
docs/HyperIndex/supported-networks/abstract.md (1)
26-26: LGTM! HyperRPC link correctly updated.The documentation link has been properly updated, maintaining consistency with the other network documentation pages in this PR.
docs/HyperIndex/supported-networks/arbitrum.md (1)
26-26: LGTM! HyperRPC link updated correctly.The HyperRPC documentation link has been properly updated to point to the new dedicated HyperRPC section, aligning with the PR's objective of making HyperRPC its own documentation section.
docs/HyperIndex/supported-networks/eth.md (1)
26-26: LGTM! Consistent HyperRPC link update.The HyperRPC documentation link has been updated consistently with other network documentation files, maintaining uniformity across the supported networks documentation.
docs/HyperIndex/supported-networks/damon.md (1)
26-26: LGTM! HyperRPC documentation link migration complete.The HyperRPC documentation link has been successfully updated across all reviewed network documentation files. The changes are consistent and align with the PR's objective of establishing HyperRPC as its own documentation section alongside HyperSync and HyperIndex.
docs/HyperIndex/supported-networks/sophon.md (1)
26-26: Link path verified The filedocs/HyperRPC/overview-hyperrpc.mdexists, so the link/docs/HyperRPC/overview-hyperrpcis correct.docs/HyperIndex/supported-networks/bsc.md (2)
26-26: LGTM! HyperRPC link correctly updated.The HyperRPC link has been properly updated to point to the new dedicated HyperRPC documentation section, consistent with the PR's objective to separate HyperRPC from HyperSync documentation.
28-32: Performance claim and quickstart link verified
Quickstart guide at/docs/HyperIndex/contract-importexists and the “up to 1000x faster” claim is consistently used throughout the documentation.docs/HyperIndex/supported-networks/chainweb-testnet-20.md (1)
26-26: Link update is correct for HyperRPC restructuring.The documentation link update from
/docs/HyperSync/overview-hyperrpcto/docs/HyperRPC/overview-hyperrpccorrectly reflects the new HyperRPC section structure.docs/HyperIndex/supported-networks/zeta.md (1)
32-32: Quickstart guidance paragraph is present in all supported-network docs as expected.
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Aurora Turbo, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Aurora Turbo, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🧩 Analysis chain
LGTM! Verify link target exists and check consistency across other network files.
The link update correctly aligns HyperRPC documentation with its new dedicated section, making the documentation structure more logical and consistent.
Please verify that:
- The new link target
/docs/HyperRPC/overview-hyperrpcexists and is accessible - Similar link updates have been applied consistently across all other supported-networks documentation files
Run the following script to verify:
🏁 Script executed:
#!/bin/bash
# Description: Verify the HyperRPC overview file exists and check for any remaining old HyperRPC links
# Check if the new HyperRPC overview file exists
echo "=== Checking if new HyperRPC overview file exists ==="
fd -t f "overview-hyperrpc.md" docs/HyperRPC/
# Search for any remaining old HyperRPC links under HyperSync path
echo -e "\n=== Searching for any remaining old HyperRPC links ==="
rg -n "/docs/HyperSync/overview-hyperrpc" docs/
# Search for all HyperRPC links to ensure consistency
echo -e "\n=== All HyperRPC documentation links ==="
rg -n "/docs/HyperRPC/overview-hyperrpc" docs/Length of output: 65471
Critical: bulk update remaining HyperRPC links
The HyperRPC overview file (docs/HyperRPC/overview-hyperrpc.md) exists, but many files under docs/HyperIndex/supported-networks/ still reference the old /docs/HyperSync/overview-hyperrpc path. Replace all occurrences of [HyperRPC](/docs/HyperSync/overview-hyperrpc) with [HyperRPC](/docs/HyperRPC/overview-hyperrpc) to ensure consistent, working links across the documentation.
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/aurora-turbo.md around line 26, the
HyperRPC link incorrectly points to /docs/HyperSync/overview-hyperrpc; update
the link target to /docs/HyperRPC/overview-hyperrpc so it matches the actual
file path. Search other files under docs/HyperIndex/supported-networks/ for
occurrences of [HyperRPC](/docs/HyperSync/overview-hyperrpc) and replace each
with [HyperRPC](/docs/HyperRPC/overview-hyperrpc) to ensure all references are
consistent and resolve to the correct overview file.
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Curtis, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Curtis, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🧩 Analysis chain
LGTM! Link update aligns with PR objectives.
The HyperRPC link now correctly points to /docs/HyperRPC/overview-hyperrpc, consistent with making HyperRPC its own documentation section.
Please verify:
- The new link target (
/docs/HyperRPC/overview-hyperrpc) exists and is accessible. - All other network documentation files have been updated with the same link change for consistency.
🏁 Script executed:
#!/bin/bash
# Verify the new HyperRPC overview page exists
fd -t f "overview-hyperrpc" docs/
# Check for any remaining references to the old HyperSync path for HyperRPC
rg -n "/docs/HyperSync/overview-hyperrpc" docs/
# Find all network documentation files to ensure consistency
fd -t f -e md . docs/HyperIndex/supported-networks/Length of output: 28699
Update HyperRPC links across all supported-network docs
Multiple files under docs/HyperIndex/supported-networks/ still reference HyperRPC as /docs/HyperSync/overview-hyperrpc. Change every occurrence to /docs/HyperRPC/overview-hyperrpc to match the new documentation structure. Verified docs/HyperRPC/overview-hyperrpc.md exists.
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/curtis.md around line 26, the HyperRPC
link is incorrectly pointing to /docs/HyperSync/overview-hyperrpc; update this
occurrence to /docs/HyperRPC/overview-hyperrpc so it matches the new doc path;
apply the same replacement for any other occurrences in this file and confirm no
other links in docs/HyperIndex/supported-networks/* use the old
/docs/HyperSync/overview-hyperrpc path.
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Fantom, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Fantom, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
🧩 Analysis chain
LGTM! Verify that the new documentation path exists.
The link update correctly reflects HyperRPC's promotion to its own documentation section, maintaining consistency with HyperIndex and HyperSync. The markdown syntax is correct.
Run the following script to verify that:
- The new HyperRPC documentation path exists
- All old path references have been updated across the codebase
🏁 Script executed:
#!/bin/bash
# Description: Verify HyperRPC documentation path exists and no old references remain
echo "=== Checking if new HyperRPC overview document exists ==="
fd -t f "overview-hyperrpc" docs/HyperRPC/
echo -e "\n=== Searching for any remaining old path references ==="
rg -n "/docs/HyperSync/overview-hyperrpc" --type md
echo -e "\n=== Verifying new path references ==="
rg -n "/docs/HyperRPC/overview-hyperrpc" --type mdLength of output: 65869
Update all remaining HyperRPC links to the new path
The file docs/HyperRPC/overview-hyperrpc.md exists, but there are dozens of links still pointing to /docs/HyperSync/overview-hyperrpc in blog posts and docs/HyperIndex/supported-networks/*. Please replace every occurrence of /docs/HyperSync/overview-hyperrpc with /docs/HyperRPC/overview-hyperrpc.
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/fantom.md around line 26, the HyperRPC
link incorrectly points to /docs/HyperSync/overview-hyperrpc; update this link
to the new path /docs/HyperRPC/overview-hyperrpc and review the rest of the file
for any other occurrences of /docs/HyperSync/overview-hyperrpc, replacing each
with /docs/HyperRPC/overview-hyperrpc to ensure all references use the correct
documentation path.
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Lisk, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Lisk, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🧩 Analysis chain
LGTM! Verify the new path exists and all network docs are updated consistently.
The HyperRPC link update correctly reflects the new documentation structure where HyperRPC is its own section.
Run the following script to verify the changes are complete and consistent:
🏁 Script executed:
#!/bin/bash
# Description: Verify HyperRPC documentation refactoring is complete
echo "=== 1. Check if the new HyperRPC overview page exists ==="
fd -t f "overview-hyperrpc" docs/HyperRPC/
echo -e "\n=== 2. Find any remaining references to old HyperSync/overview-hyperrpc path ==="
rg -n "HyperSync/overview-hyperrpc" docs/
echo -e "\n=== 3. Verify all supported-networks files use the new HyperRPC path ==="
rg -n "HyperRPC/overview-hyperrpc" docs/HyperIndex/supported-networks/ | head -20
echo -e "\n=== 4. Check for any inconsistent HyperRPC references ==="
rg -n "docs/HyperRPC" docs/HyperIndex/supported-networks/ | rg -v "overview-hyperrpc" | head -10Length of output: 28896
Replace all stale HyperRPC links
Search for /docs/HyperSync/overview-hyperrpc and update to /docs/HyperRPC/overview-hyperrpc across docs/HyperIndex/supported-networks/* (including others.md).
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/lisk.md around line 26 the HyperRPC link
points to /docs/HyperSync/overview-hyperrpc which is stale; update this link to
/docs/HyperRPC/overview-hyperrpc. Also search the entire
docs/HyperIndex/supported-networks/ directory (including others.md) for any
occurrences of /docs/HyperSync/overview-hyperrpc and replace them with
/docs/HyperRPC/overview-hyperrpc to ensure all references are consistent.
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Lukso Testnet, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Lukso Testnet, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🧩 Analysis chain
LGTM! Verify consistent link updates across all network documentation.
The HyperRPC link update correctly reflects the new documentation structure where HyperRPC has its own section.
Run the following script to verify that all HyperRPC links have been consistently updated across the supported-networks documentation:
🏁 Script executed:
#!/bin/bash
# Description: Check for any remaining references to the old HyperRPC path and verify consistency of the new path.
echo "=== Checking for old HyperRPC path references ==="
rg -n "HyperSync/overview-hyperrpc" docs/HyperIndex/supported-networks/
echo -e "\n=== Verifying new HyperRPC path usage ==="
rg -n "HyperRPC/overview-hyperrpc" docs/HyperIndex/supported-networks/
echo -e "\n=== Checking if target document exists ==="
fd -t f "overview-hyperrpc" docs/HyperRPC/Length of output: 65456
Update all HyperRPC links to the new documentation path
Replace every remaining [HyperRPC](/docs/HyperSync/overview-hyperrpc) with [HyperRPC](/docs/HyperRPC/overview-hyperrpc) in all files under docs/HyperIndex/supported-networks/—the script shows dozens still pointing to the old path.
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/lukso-testnet.md around line 26, the
HyperRPC link uses the old path (/docs/HyperSync/overview-hyperrpc); replace
that link with the new path (/docs/HyperRPC/overview-hyperrpc). Also scan all
files under docs/HyperIndex/supported-networks/ and replace any occurrences of
[HyperRPC](/docs/HyperSync/overview-hyperrpc) with
[HyperRPC](/docs/HyperRPC/overview-hyperrpc), committing the updated files.
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Tangle, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Tangle, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🧩 Analysis chain
LGTM! Verify all HyperRPC links have been updated consistently.
The link update correctly reflects HyperRPC's new position as its own documentation section. Ensure all similar references across the codebase have been updated.
Run the following script to verify all HyperRPC documentation links have been migrated from the HyperSync path:
🏁 Script executed:
#!/bin/bash
# Description: Search for any remaining old HyperRPC links under HyperSync path
# Search for old HyperRPC links that should have been updated
rg -n --type=md '/docs/HyperSync/.*hyperrpc' docs/Length of output: 65284
Update all HyperRPC links in supported-networks docs
Replace every occurrence of /docs/HyperSync/overview-hyperrpc with /docs/HyperRPC/overview-hyperrpc in the docs/HyperIndex/supported-networks/ directory to ensure documentation consistency.
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/tangle.md around line 26, update the
HyperRPC link: replace the incorrect path `/docs/HyperSync/overview-hyperrpc`
with the correct `/docs/HyperRPC/overview-hyperrpc`; also scan the entire
docs/HyperIndex/supported-networks/ directory and perform the same replacement
for every occurrence to ensure all links point to the HyperRPC overview.
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Unichain, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Unichain, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
🧩 Analysis chain
LGTM! Verify the new HyperRPC documentation path.
The URL update correctly reflects the reorganization of HyperRPC into its own documentation section, which aligns with the PR objective.
Please verify that the new path /docs/HyperRPC/overview-hyperrpc exists and is properly configured in the documentation structure:
🏁 Script executed:
#!/bin/bash
# Description: Verify the HyperRPC overview document exists and check for any other references to the old path
# Check if the new HyperRPC overview document exists
echo "=== Checking for HyperRPC overview document ==="
fd -t f "overview-hyperrpc" docs/
# Search for any remaining references to the old path
echo -e "\n=== Checking for any remaining references to old path ==="
rg -n "/docs/HyperSync/overview-hyperrpc" docs/
# Check docusaurus config and sidebars for HyperRPC section configuration
echo -e "\n=== Checking HyperRPC configuration ==="
fd -t f "sidebarsHyperRPC" .
fd -t f "docusaurus.config" . --exec cat {} \; | grep -A 5 -B 5 "HyperRPC" || echo "No HyperRPC config found"Length of output: 20142
Update HyperRPC links in supported-networks docs
The new overview at docs/HyperRPC/overview-hyperrpc.md is in place, but all files under docs/HyperIndex/supported-networks/ (e.g., darwinia.md, goerli.md, others…) still reference /docs/HyperSync/overview-hyperrpc. Replace those with /docs/HyperRPC/overview-hyperrpc.
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/unichain.md around line 26, the link to
the HyperRPC overview incorrectly points to /docs/HyperSync/overview-hyperrpc;
update the link target to /docs/HyperRPC/overview-hyperrpc so the text
references the correct new overview path (apply the same change to other files
in docs/HyperIndex/supported-networks/ as needed).
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Worldchain, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Worldchain, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
🧩 Analysis chain
LGTM! Verify the new documentation path exists and consistency across network files.
The HyperRPC documentation link update correctly reflects the new structure where HyperRPC has its own section, aligning with the PR objectives.
Please verify:
- That the new path
/docs/HyperRPC/overview-hyperrpcexists and is accessible - That similar link updates were applied consistently across all other network documentation files
Run the following script to verify:
🏁 Script executed:
#!/bin/bash
# Description: Verify HyperRPC documentation exists and check consistency across network files
# Check if the new HyperRPC documentation file exists
echo "=== Checking if HyperRPC documentation exists ==="
fd -t f "overview-hyperrpc" docs/HyperRPC/
# Search for any remaining old HyperSync/overview-hyperrpc references
echo -e "\n=== Checking for old HyperSync/overview-hyperrpc references ==="
rg -n "HyperSync/overview-hyperrpc" docs/HyperIndex/supported-networks/
# Verify all network files have the new HyperRPC path
echo -e "\n=== Verifying new HyperRPC path usage in network files ==="
rg -n "HyperRPC/overview-hyperrpc" docs/HyperIndex/supported-networks/Length of output: 65494
Update HyperRPC links across supported network docs
docs/HyperRPC/overview-hyperrpc.md exists, but nearly all files in docs/HyperIndex/supported-networks/ still reference the old /docs/HyperSync/overview-hyperrpc link. Replace those with /docs/HyperRPC/overview-hyperrpc.
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/worldchain.md around line 26 the HyperRPC
link points to /docs/HyperSync/overview-hyperrpc; update that link to
/docs/HyperRPC/overview-hyperrpc so it references the correct file path, and
scan other files in docs/HyperIndex/supported-networks/ to replace any remaining
/docs/HyperSync/overview-hyperrpc occurrences with
/docs/HyperRPC/overview-hyperrpc to keep links consistent.
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Zeta, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Zeta, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
🧩 Analysis chain
LGTM! HyperRPC link correctly updated.
The link path change from /HyperSync/overview-hyperrpc to /HyperRPC/overview-hyperrpc aligns with the PR objective to make HyperRPC its own documentation section.
Verify that all network documentation files have been updated consistently:
🏁 Script executed:
#!/bin/bash
# Description: Verify all HyperRPC links in network documentation point to the new path
# Expected: All links should use /HyperRPC/overview-hyperrpc, none should use /HyperSync/overview-hyperrpc
echo "=== Checking for old HyperRPC links ==="
rg -n "HyperSync/overview-hyperrpc" docs/HyperIndex/supported-networks/
echo ""
echo "=== Verifying new HyperRPC links ==="
rg -n "HyperRPC/overview-hyperrpc" docs/HyperIndex/supported-networks/Length of output: 65362
Bulk update HyperRPC links across supported-network docs
Several files in docs/HyperIndex/supported-networks still reference the old HyperRPC path (/docs/HyperSync/overview-hyperrpc). Update every occurrence to /docs/HyperRPC/overview-hyperrpc to ensure consistency across all network documentation.
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/zeta.md around line 26, the HyperRPC link
uses the old path `/docs/HyperSync/overview-hyperrpc`; replace it with
`/docs/HyperRPC/overview-hyperrpc`. Also search all files under
docs/HyperIndex/supported-networks for any occurrences of
`/docs/HyperSync/overview-hyperrpc` and update them to
`/docs/HyperRPC/overview-hyperrpc` to ensure consistency, then run a quick
link-check or local docs build to verify no broken links remain.
| ### Overview | ||
|
|
||
| Envio is a modular hyper-performant data indexing solution for Zora, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC). | ||
| Envio is a modular hyper-performant data indexing solution for Zora, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperRPC/overview-hyperrpc) (extremely fast read-only RPC). |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
🧩 Analysis chain
LGTM! Verify link target and consistency across network docs.
The HyperRPC link update correctly aligns with the PR objective of separating HyperRPC documentation into its own section.
Please verify:
- The new link target exists and is accessible.
- Similar updates were applied consistently across all network documentation files.
🏁 Script executed:
#!/bin/bash
# Description: Verify the HyperRPC link target exists and check consistency across network docs.
# Check if the new HyperRPC overview file exists
echo "=== Checking if HyperRPC overview file exists ==="
fd -t f "overview-hyperrpc" docs/HyperRPC/
# Check all network documentation files for HyperRPC link consistency
echo -e "\n=== Checking HyperRPC links in all network documentation files ==="
rg -n "HyperRPC\]\(" docs/HyperIndex/supported-networks/ -A 0 -B 0
# Verify the old HyperSync path is not still being used for HyperRPC references
echo -e "\n=== Checking for any remaining old HyperRPC links ==="
rg -n "HyperRPC.*\/docs\/HyperSync" docs/HyperIndex/supported-networks/ -A 0 -B 0Length of output: 65596
Update all HyperRPC links in network docs
Most files under docs/HyperIndex/supported-networks/ still use the old path /docs/HyperSync/overview-hyperrpc for HyperRPC. Change every instance to /docs/HyperRPC/overview-hyperrpc.
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/zora.md around line 26, the HyperRPC link
uses the old path /docs/HyperSync/overview-hyperrpc; update this to the correct
path /docs/HyperRPC/overview-hyperrpc. Search the file (and other files under
docs/HyperIndex/supported-networks/) for occurrences of
/docs/HyperSync/overview-hyperrpc and replace each with
/docs/HyperRPC/overview-hyperrpc, then run a quick link check or preview to
ensure the updated links resolve correctly.
2 participants
Made HyperRPC its own section like HyperSync and HyperIndex are and updated the LLM docs (so hypersync llm no longer includes hyperrpc).
Summary by CodeRabbit
New Features
Documentation
Chores