Tempo URL fix

[nikbhintade]

because of (), url was getting generated incorrectly

Summary by CodeRabbit

Documentation

• New Features

  • Added Tempo Testnet support documentation with RPC configuration guidance
  • Expanded HyperRPC supported networks reference with complete network listings and details
  • Expanded HyperSync supported networks reference with complete network listings, IDs, URLs, and tier information

• Documentation

  • Updated Tempo Testnet network naming and references for consistency across documentation and configuration files

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
envio-docs	Ready	Preview	Comment	Dec 10, 2025 1:43pm

[coderabbitai]

Walkthrough

This pull request adds documentation and updates configuration files for Tempo Testnet network support across the platform. Changes include a new HyperIndex network documentation file with RPC configuration guidance, network tables for HyperRPC and HyperSync, standardized naming from "Tempo Testnet (Andantino)" to "Tempo Testnet" in network registry files.

Changes

Cohort / File(s)	Summary
HyperIndex Network Documentation docs/HyperIndex/supported-networks/tempo-testnet.md	New file documenting Tempo Testnet RPC-based indexing with configuration guidance, YAML example showing rpc_config.url, start_block, contracts, handlers, and events; includes RPC reliability warnings and Discord support link.
HyperRPC & HyperSync Network Tables docs/HyperRPC/hyperrpc-supported-networks.md, docs/HyperSync/hypersync-supported-networks.md	Added comprehensive networks tables listing supported chains with Network Name, Network ID, URL, and (for HyperSync) Tier information across multiple network entries.
Network Registry Updates scripts/rpc-networks.json, supported-networks.json	Updated Tempo Testnet naming from "Tempo Testnet (Andantino)" to "Tempo Testnet" in RPC networks registry and supported networks catalog array entry.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10–15 minutes

• Network tables are long but follow consistent formatting patterns
• JSON changes are straightforward single-field and array element updates
• No complex logic or functional changes; purely documentation and configuration

Possibly related PRs

• Add Tempo to Supported Chains for HyperIndex #758: Directly related—modifies same Tempo Testnet HyperIndex documentation entry and scripts/supported-networks JSON artifacts.
• docs: refresh content metadata #748: Overlaps on HyperRPC/HyperSync supported-networks documentation files and supported-networks.json updates.
• fix: remove duplicate from sidebar #743: Modifies the same HyperRPC and HyperSync network listing tables with additional network entries.

Suggested reviewers

• DenhamPreen
• moose-code

Poem

🐰 Tempo's name now clean and bright,
No "(Andantino)" in sight!
Tables bloom with networks new,
RPC guidance—fresh and true.
Docs grow faster, hop by hop! 🌱

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Tempo URL fix' is vague and does not clearly convey the specific changes made in the changeset, which involve renaming Tempo Testnet documentation and updating network entries across multiple files.	Consider a more descriptive title such as 'Rename Tempo Testnet (Andantino) to Tempo Testnet across docs and configs' to better reflect the actual changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch nb/update-tempo

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 771a806 and 46cd7a0.

📒 Files selected for processing (5)

• docs/HyperIndex/supported-networks/tempo-testnet.md (1 hunks)
• docs/HyperRPC/hyperrpc-supported-networks.md (1 hunks)
• docs/HyperSync/hypersync-supported-networks.md (1 hunks)
• scripts/rpc-networks.json (1 hunks)
• supported-networks.json (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

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

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

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

• supported-networks.json
• docs/HyperIndex/supported-networks/tempo-testnet.md
• scripts/rpc-networks.json
• docs/HyperSync/hypersync-supported-networks.md
• docs/HyperRPC/hyperrpc-supported-networks.md

🔇 Additional comments (5)

supported-networks.json (1)

173-173: URL identifier fix approved.

Removing parentheses from "tempo-testnet-(andantino)" to "tempo-testnet" correctly addresses the PR objective of fixing URL generation issues caused by special characters.

scripts/rpc-networks.json (1)

5-5: Network name fix approved.

Removing "(Andantino)" suffix from the Tempo Testnet name is correct and necessary for proper URL generation. This change aligns perfectly with the PR objective.

docs/HyperIndex/supported-networks/tempo-testnet.md (1)

1-51: Documentation well-written and accurate.

The new Tempo Testnet documentation is clear, well-structured, and provides excellent guidance for users. The YAML configuration example is properly formatted, and the warning about RPC reliability is appropriately placed.

However, note that Tempo Testnet is missing from the HyperRPC and HyperSync network support tables (separate files), which should be added to complete the PR's objective of fully documenting Tempo Testnet support across all relevant documentation.

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

35-120: Tempo Testnet does not have functional HyperSync support and should not be added to this table.

Tempo Testnet (chain ID 42429) currently only supports RPC-based indexing. The official documentation explicitly requests HyperSync support via Discord and states: "Want HyperSync for Tempo Testnet? Request network support here." The HyperSync endpoints (https://tempo.rpc.hypersync.xyz and https://42429.rpc.hypersync.xyz) are not functional. This HyperRPC table should only include networks with working HyperSync endpoints, so the current state is correct.

Likely an incorrect or invalid review comment.

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

43-128: The review comment is incorrect and should not be adopted.

Tempo Testnet exists in the documentation but explicitly lacks HyperSync support. Both tempo-testnet.md and tempo-testnet-(andantino).md state: "Want HyperSync for Tempo Testnet? Request network support here Discord". This indicates HyperSync is not currently available for Tempo Testnet—only RPC-based indexing is supported. The HyperSync networks table (lines 43-128) should only list networks with functional HyperSync endpoints, so Tempo Testnet should not be added.

Likely an incorrect or invalid review comment.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}