Update ITRocket services

[itrocket-team]

Overview

Summary by CodeRabbit

• Documentation
  • Added new archival data availability RPC endpoint and analytics resource from ITRocket to the Celestia Mainnet Beta guide.
  • Included a new community full node endpoint for the Mocha testnet guide.

[coderabbitai]

Walkthrough

The documentation for Celestia was updated to add new community-provided endpoints from ITRocket. This includes an archival DA RPC endpoint and an analytics tracker for Mainnet Beta, as well as a new full node endpoint for the Mocha testnet. No existing entries were changed.

Changes

File(s)	Change Summary
how-to-guides/mainnet.md	Added ITRocket archival DA RPC endpoint and analytics tracker to mainnet documentation.
how-to-guides/mocha-testnet.md	Added ITRocket full node endpoint to Mocha testnet documentation.

Possibly related PRs

• docs: update rpcs based on dead links from https://celestia-tools.bri… #1745: Both PRs modify documentation to update RPC endpoint listings, focusing on adding or removing endpoints.
• docs: add qn to mocha #1918: Both PRs add new RPC provider endpoints to the Mocha testnet documentation, though with different providers.
• Update mainnet.md #1835: Both PRs update the mainnet documentation by adding new community-provided RPC endpoints.

Suggested reviewers

• jcstein

Poem

Hopping through docs with nimble delight,
ITRocket endpoints now shine bright!
Mainnet and Mocha, new links in the field,
Analytics and access, their secrets revealed.
With every new hop and a twitch of my nose,
The Celestia garden of nodes only grows!
🐇✨

---

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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

how-to-guides/mocha-testnet.md (1)

238-241: Wrap the new endpoint in inline code ticks for consistency.

Other domain entries in this section (e.g., the mzonder endpoint at line 235) are enclosed in backticks. Please wrap celestia-testnet-da-full-storage.itrocket.net in backticks as well to match the existing style.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9440340 and 342829b.

📒 Files selected for processing (2)

• how-to-guides/mainnet.md (2 hunks)
• how-to-guides/mocha-testnet.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: deploy-preview
• GitHub Check: build

🔇 Additional comments (2)

how-to-guides/mainnet.md (2)

215-215: Archival DA RPC: ITRocket entry looks good.

The new ITRocket archival DA RPC endpoint has been correctly added with matching ports and inline code formatting. Verify the surrounding table alignment remains consistent after insertion.

---

253-253: Analytics: ITRocket consensus tracker added.

The new analytics link for the “Consensus signal tracker” follows the existing list syntax and link style. No further changes needed.