Skip to content

docs: add bootstrappers new #2009

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 28, 2025
Merged

docs: add bootstrappers new #2009

merged 2 commits into from
Apr 28, 2025

Conversation

jcstein
Copy link
Member

@jcstein jcstein commented Apr 24, 2025

Overview

Resolves #1974

Summary by CodeRabbit

  • Documentation
    • Updated guides to reference the official Celestia bootstrappers list instead of listing static node endpoints.
    • Added direct links to the Celestia bootstrappers list in relevant sections for Arabica devnet, Mainnet, and Mocha testnet documentation.
    • Introduced a new subsection for community bridge and full node endpoints in the Mocha testnet guide.

Copy link
Contributor

coderabbitai bot commented Apr 24, 2025

Walkthrough

The documentation for Arabica Devnet, Mainnet, and Mocha Testnet was updated to remove static listings of Celestia node endpoints and instead direct users to the official Celestia bootstrappers list in the celestia-node GitHub repository. Each relevant section now includes a reference link to the authoritative source for bootstrapper peers, ensuring endpoint information remains current. No changes were made to code, logic, or exported entities.

Changes

File(s) Change Summary
how-to-guides/arabica-devnet.md Removed static DA bridge node endpoints and replaced with a link to the official Celestia bootstrappers list.
how-to-guides/mainnet.md Added a direct link to the official Celestia bootstrappers list under the community consensus endpoints section.
how-to-guides/mocha-testnet.md Added a new subsection with a reference link to the official Celestia bootstrappers list for bridge and full node endpoints.

Assessment against linked issues

Objective (Issue #) Addressed Explanation
Update docs to reference the official Celestia bootstrappers list in mainnet, mocha-testnet, and arabica-devnet guides (#1974)

Possibly related PRs

Poem

A hop, a skip, a doc update bright,
No more static lists to keep us up at night.
With links to bootstrappers, fresh and clear,
Finding nodes is now less of a fear.
Rabbits rejoice—no more stale DNS!
The docs are current, and so is our happiness.
🐇✨


📜 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 0cbba6c and 83b0f43.

📒 Files selected for processing (3)
  • how-to-guides/arabica-devnet.md (1 hunks)
  • how-to-guides/mainnet.md (1 hunks)
  • how-to-guides/mocha-testnet.md (1 hunks)
🔇 Additional comments (3)
how-to-guides/mocha-testnet.md (1)

78-81: Standardize bootstrapper peer references across guides.

Adding the “Community bridge and full node endpoints” section with a link to the official Celestia bootstrappers list centralizes peer information and prevents stale or conflicting endpoint listings. This change aligns with other network guides and ensures users always have the most up-to-date data.

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

119-119: Link to official Celestia bootstrappers for community consensus endpoints.

Providing a direct reference to the Celestia-node bootstrap.go file offers a single source of truth for consensus peer endpoints, reducing maintenance overhead and minimizing the risk of outdated information.

how-to-guides/arabica-devnet.md (1)

90-90: Replace static DA bridge node listing with centralized bootstrapper link.

Shifting from hard-coded Data Availability bridge endpoints to a link to the official Celestia bootstrappers list keeps the documentation DRY and ensures peer data remains current without manual updates.


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

@jcstein jcstein self-assigned this Apr 24, 2025
@jcstein jcstein requested review from smuu and Copilot and removed request for smuu April 24, 2025 17:44
Copy link

@Copilot 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 updates the documentation for various Celestia network guides by referencing the official list of bootstrappers via a GitHub link, thereby resolving issue #1974.

  • Updated mocha-testnet.md to include a new section with the official bootstrappers reference.
  • Updated mainnet.md to add a reference to the official bootstrappers.
  • Updated arabica-devnet.md by replacing multiple hardcoded endpoints with a link to the official bootstrappers.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
how-to-guides/mocha-testnet.md Added a new section for community bridge and full node endpoints referencing bootstrappers.
how-to-guides/mainnet.md Inserted a line referencing the official bootstrappers for node endpoints.
how-to-guides/arabica-devnet.md Replaced the detailed data availability node endpoints with a link to official bootstrappers.

Copy link
Contributor

github-actions bot commented Apr 24, 2025

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

@jcstein jcstein requested a review from smuu April 24, 2025 17:45
@jcstein jcstein merged commit 217ee5c into main Apr 28, 2025
7 checks passed
@jcstein jcstein deleted the jcs/bootstrappers branch April 28, 2025 16:56
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.

docs: update bootstrapper dns
1 participant