docs: add mocha -> sepolia blobstream x lc

[ratankaliani]

Overview

Add Mocha Testnet -> Sepolia Blobstream X light client to the Blobstream X docs.

Summary by CodeRabbit

• Documentation
  • Added documentation for Blobstream X on the Sepolia network, including contract address and testnet details.

[coderabbitai]

Walkthrough

A fresh breeze flows through the digital landscape as Blobstream X finds its new home on the Sepolia network, stretching its connections to the vibrant Mocha testnet. This update marks a significant leap, embedding the essence of innovation within the fabric of development, ready to be explored and utilized by the curious and the bold.

Changes

File Path	Change Summary
developers/.../blobstream.md	Introduced Blobstream X on Sepolia targeting Mocha testnet with new contract address and link.

🐇🌟
In the digital meadow, under the code's bright gleam,
Lies a fresh path, a developer's dream.
Blobstream X now on Sepolia does reside,
With Mocha as its guide, in bytes we confide.
To the future we hop, with every line we type,
In the blockchain's embrace, ripe with lore ripe.
🌱🌈✨

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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: 1

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 4710954 and ea2359f.

Files selected for processing (1)

• developers/blobstream.md (1 hunks)

Additional comments not posted (2)

developers/blobstream.md (2)

169-175: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [1-174]

Review the document for consistent Markdown formatting and adherence to best practices.

Consider using a Markdown linter to automatically identify and fix common formatting issues for improved readability and consistency.

---

172-174: Ensure the new entries are well-integrated and clearly explained within the context of the document.

To enhance clarity, consider adding a brief introduction or explanation for the new entries, especially for readers who might be unfamiliar with the Sepolia network or the Mocha testnet.

[coderabbitai]

Tip

Codebase Verification

The verification process has confirmed that both contract addresses are valid Ethereum addresses, as they match the expected format. However, while the links for the addresses on Arbiscan and Basescan returned a 200 HTTP status code, indicating they are reachable and functional, the link for the address on Etherscan returned a 403 HTTP status code. This suggests that the link to the Sepolia Etherscan might not be accessible or there could be restrictions in place that prevent accessing it in this manner.

Given this information, the contract addresses are accurate, but there is an issue with the accessibility of the link provided for the Sepolia Etherscan. It's important to note that a 403 error could be due to various reasons, including but not limited to, access restrictions, the link being blocked for automated requests, or the resource not being available to the public.

Analysis chain

Ensure the accuracy of the contract addresses and the functionality of the provided links.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the contract addresses are valid Ethereum addresses
echo "0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1e" | grep -E '^0x[a-fA-F0-9]{40}$'
echo "0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2" | grep -E '^0x[a-fA-F0-9]{40}$'

# Check if the links are reachable
curl -o /dev/null -s -w "%{http_code}\n" https://sepolia.etherscan.io/address/0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1e#events
curl -o /dev/null -s -w "%{http_code}\n" https://sepolia.arbiscan.io/address/0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2#events
curl -o /dev/null -s -w "%{http_code}\n" https://sepolia.basescan.org/address/0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2#events

Length of output: 650

[jcstein]

LGTM. thank you for the PR @ratankaliani