feat: Add Celestia Mainnet -> Ethereum Blobstream X deployment

[ratankaliani]

Overview

Add Celestia Mainnet -> Ethereum Blobstream X contract deployment.

Summary by CodeRabbit

• Documentation
  • Updated the contract address for Blobstream X on Ethereum Mainnet.

[coderabbitai]

Walkthrough

The update changes the contract address for Blobstream X on the Ethereum Mainnet from Not yet deployed to a specific address 0x7Cf3876F681Dbb6EdA8f6FfC45D66B996Df08fAe. This change signifies that Blobstream X has now been deployed and is live on the Ethereum network.

Changes

Files	Change Summary
developers/blobstream.md	Updated the Blobstream X contract address to 0x7Cf3876F681Dbb6EdA8f6FfC45D66B996Df08fAe on Ethereum Mainnet

Poem

In the digital sky so bright and clear,
Blobstream X has landed here.
With code so sleek, on Ethereum it flies,
A contract address, a beacon in the skies.
0x7Cf3, a new dawn we cheer,
For blockchain dreams, the future's near.
🌟🚀✨

---

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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @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: 0

Outside diff range and nitpick comments (1)

developers/blobstream.md (1)

Line range hint 189-189: Consider breaking long lines for better readability.

Lines 189, 191, 193, and 195 exceed the recommended line length of 80 characters. While this is often necessary for URLs or detailed descriptions, consider breaking the text into multiple lines or paragraphs to enhance readability, especially for non-URL parts of the text.

Also applies to: 191-191, 193-193, 195-195

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a00deab and 0639eb6.

Files selected for processing (1)

• developers/blobstream.md (1 hunks)

Additional context used

Markdownlint

developers/blobstream.md

189-189: Expected: 80; Actual: 168 (MD013, line-length)
Line length

---

191-191: Expected: 80; Actual: 260 (MD013, line-length)
Line length

---

193-193: Expected: 80; Actual: 169 (MD013, line-length)
Line length

---

195-195: Expected: 80; Actual: 252 (MD013, line-length)
Line length

Additional comments not posted (1)

developers/blobstream.md (1)

178-178: Update the contract address to the deployed one.

The update from a placeholder to an actual deployed address (0x7Cf3876F681Dbb6EdA8f6FfC45D66B996Df08fAe) on Ethereum Mainnet is accurate and reflects the deployment status correctly.