docs: use old blobstream addresses for now

[jcstein]

Overview

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

Summary by CodeRabbit

• Documentation
  • Updated contract addresses for Blobstream X across various Ethereum networks in the developer documentation.

[coderabbitai]

Walkthrough

The recent update involves modifying the contract addresses for Blobstream X across various Ethereum networks. This change impacts several networks, including Arbitrum One, Base, Ethereum Sepolia, and Arbitrum Sepolia, by either introducing new addresses or noting pending deployments for certain contracts.

Changes

File Path	Change Summary
developers/.../blobstream.md	Updated contract addresses for Blobstream X on Arbitrum One, Base, Ethereum Sepolia, and Arbitrum Sepolia. Some contracts pending deployment.

🐰✨
In the land of code and mist,
Changes come; they can't resist.
New addresses, far and wide,
Across the networks, they now reside.
Let's hop along, no time to bide,
For in our code, we take great pride.
🚀🌌

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-tests 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 tests 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 tests.
  • @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[github-actions]

PR Preview Action v1.4.7
Preview removed because the pull request was closed.
2024-03-19 14:50 UTC

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 5609f24 and ffb7326.

Files selected for processing (1)

• developers/blobstream.md (1 hunks)

Additional comments: 1

developers/blobstream.md (1)

• 166-169: The contract addresses for Ethereum Sepolia and Arbitrum Sepolia have been updated, while the addresses for Arbitrum One, Base, and Ethereum Mainnet are marked as "Not yet deployed". Ensure that these updates accurately reflect the current deployment status of the Blobstream X contracts across the specified networks. If any of these contracts are in the process of being deployed or have been deployed after this document was last updated, it would be beneficial to include the most current addresses or status information.