Skip to content

docs: add scroll & holesky#2029

Merged
jcstein merged 3 commits intomainfrom
jcs/update-blobstream-addys
Jun 4, 2025
Merged

docs: add scroll & holesky#2029
jcstein merged 3 commits intomainfrom
jcs/update-blobstream-addys

Conversation

@jcstein
Copy link
Copy Markdown
Member

@jcstein jcstein commented May 7, 2025

Overview

Adds Blobstream SP1 contracts to docs for:
Scroll: https://scrollscan.com/address/0x5008fa5CC3397faEa90fcde71C35945db6822218
Holesky: https://holesky.etherscan.io/address/0x315A044cb95e4d44bBf6253585FbEbcdB6fb41ef

Note: these don't yet exist on Celenium, so marked as "N/A" for now. cc @vvuwei incase you are planning to add these

Summary by CodeRabbit

  • Documentation
    • Updated the table of deployed SP1 Blobstream contracts to include Scroll and Holesky networks, with contract addresses and block explorer links. Deployment on Celenium is marked as "N/A" for these networks.
  • Chores
    • Added ScrollScan URL pattern to the link checker exclusion list to improve link validation.

@jcstein jcstein self-assigned this May 7, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented May 7, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The documentation for Blobstream deployments was updated to add entries for the Scroll and Holesky networks. Each entry includes the contract address and a block explorer link, with "Deployment on Celenium" marked as "N/A" for both. No other changes were made to the document. Additionally, the lychee link checker configuration was updated to exclude URLs matching the pattern for ScrollScan.

Changes

File Change Summary
how-to-guides/blobstream.md Added Scroll and Holesky networks to the deployed SP1 Blobstream contracts table with addresses and block explorer links.
lychee.toml Added "https://scrollscan.com/*" to the list of excluded URLs for the lychee link checker.

Sequence Diagram(s)

sequenceDiagram
    User->>Documentation: Views Blobstream deployment table
    Documentation-->>User: Displays updated table with Scroll and Holesky entries
    User->>Block Explorer: Follows provided links for contract details
Loading

Possibly related PRs

Suggested labels

documentation

Poem

Two new networks join the stream,
Scroll and Holesky, fresh as a dream.
Contract links for all to see,
Deployment tables growing with glee.
A hop, a skip, a doc update—
More networks now, isn’t it great?
🐇✨


📜 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 1156a92 and 253be5b.

📒 Files selected for processing (1)
  • lychee.toml (2 hunks)

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
🪧 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.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented May 7, 2025

PR Preview Action v1.6.1
Preview removed because the pull request was closed.
2025-06-04 09:28 UTC

@jcstein jcstein requested a review from Copilot May 8, 2025 14:04
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds documentation entries for SP1 Blobstream contracts on the Scroll and Holesky chains.

  • Adds a new row for the Scroll network with its corresponding contract link.
  • Adds a new row for the Holesky network with its corresponding contract link.

Comment thread how-to-guides/blobstream.md Outdated
Comment thread how-to-guides/blobstream.md Outdated
@jcstein jcstein requested a review from gbarros May 9, 2025 20:44
@jcstein
Copy link
Copy Markdown
Member Author

jcstein commented May 9, 2025

Note: these don't yet exist on Celenium, so marked as "N/A" for now. cc @vvuwei incase you are planning to add these

We'll add links to celenium when they're there, this should be good to go for now.

@jcstein jcstein marked this pull request as ready for review May 9, 2025 20:44
@jcstein jcstein enabled auto-merge (squash) May 9, 2025 20:44
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (2)
how-to-guides/blobstream.md (2)

159-159: Clarify the "N/A" placeholder for Celenium deployment
Consider adding a note below the table indicating that "N/A" signifies the contract is not yet deployed on Celenium and will be updated once the deployment is live.


163-163: Clarify the "N/A" placeholder for Celenium deployment
As above, add a footnote below the table explaining that "N/A" indicates pending Celenium deployment.

🧹 Nitpick comments (2)
how-to-guides/blobstream.md (2)

159-159: Ensure consistency in event-log links
Other EVM network entries append #events to the block-explorer URL to jump directly to the event logs. Consider adding #events to the ScrollScan link for parity:

-[`0x5008fa5CC3397faEa90fcde71C35945db6822218`](https://scrollscan.com/address/0x5008fa5CC3397faEa90fcde71C35945db6822218)
+[`0x5008fa5CC3397faEa90fcde71C35945db6822218`](https://scrollscan.com/address/0x5008fa5CC3397faEa90fcde71C35945db6822218#events)

163-163: Ensure consistency in event-log links
For consistency with other entries, append #events to the Holesky Etherscan URL:

-[`0x315A044cb95e4d44bBf6253585FbEbcdB6fb41ef`](https://holesky.etherscan.io/address/0x315A044cb95e4d44bBf6253585FbEbcdB6fb41ef)
+[`0x315A044cb95e4d44bBf6253585FbEbcdB6fb41ef`](https://holesky.etherscan.io/address/0x315A044cb95e4d44bBf6253585FbEbcdB6fb41ef#events)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 41f085b and 46b23f1.

📒 Files selected for processing (1)
  • how-to-guides/blobstream.md (1 hunks)

@jcstein jcstein disabled auto-merge June 4, 2025 09:22
@jcstein jcstein merged commit 961658b into main Jun 4, 2025
9 of 10 checks passed
@jcstein jcstein deleted the jcs/update-blobstream-addys branch June 4, 2025 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants