Skip to content

Added Staker Space Public Endpoints: RPC - API - GRPC to mainnet.md#1477

Merged
jcstein merged 1 commit intocelestiaorg:mainfrom
StakerSpace:main
Mar 14, 2024
Merged

Added Staker Space Public Endpoints: RPC - API - GRPC to mainnet.md#1477
jcstein merged 1 commit intocelestiaorg:mainfrom
StakerSpace:main

Conversation

@Suleymann85
Copy link
Copy Markdown
Contributor

@Suleymann85 Suleymann85 commented Mar 13, 2024

Overview

We would like to add Staker Space's RPC - API and GRPC to the docs.

Also at the end of the API section "celestia-api.f5nodes.com" and "https://celestia-api.chainode.tech" were next to each other. I adjust that to be below each other.

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

  • New Features
    • Added new endpoints for Mainnet Beta participation including RPC, API, and gRPC endpoints to enhance network connectivity and interaction capabilities.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 13, 2024

Walkthrough

The recent update introduces a significant enhancement to the network's infrastructure by adding a new RPC, API, and gRPC endpoint for Mainnet Beta participation. This enhancement is aimed at improving accessibility and interaction with the network, ensuring users and developers have more reliable and varied options for connecting to the Mainnet Beta.

Changes

File Path Change Summary
nodes/mainnet.md Added new RPC, API, and gRPC endpoints https://...staker.space/ for Mainnet Beta participation.

🐇🌌
In the digital meadow, under the code's bright gleam,
A new path opens, as if from a dream.
RPC, API, gRPC, a trio so fine,
Connecting to Mainnet, as stars align.
🚀🌐✨

  • @coderabbitai

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

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.

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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 9c1fb99 and 5302177.
Files selected for processing (1)
  • nodes/mainnet.md (3 hunks)
Additional comments: 3
nodes/mainnet.md (3)
  • 126-126: The addition of the new RPC endpoint https://rpc-celestia.staker.space/ is correctly placed within the Consensus RPC endpoints section. This ensures users can easily find the endpoint when setting up their consensus nodes.
  • 150-151: The addition of the new API endpoint https://api-celestia.staker.space/ is correctly placed within the API endpoints section. However, it's important to ensure that the formatting adjustment mentioned in the PR objectives, which involves listing two existing API endpoints (celestia-api.f5nodes.com and https://celestia-api.chainode.tech) one below the other, is correctly implemented to improve readability.
  • 175-175: The addition of the new gRPC endpoint https://grpc-celestia.staker.space/ is correctly placed within the gRPC endpoints section. This ensures users can easily find the endpoint when setting up their gRPC connections.

@jcstein jcstein merged commit 5a84cf9 into celestiaorg:main Mar 14, 2024
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