Skip to content
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

Add kjnodes endpoints and slashboard #1402

Merged
merged 1 commit into from
Feb 7, 2024
Merged

Conversation

kj89
Copy link
Contributor

@kj89 kj89 commented Feb 7, 2024

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

  • New Features
    • Added new API and gRPC endpoints for Mainnet Beta.
    • Launched a new analytics website for Mainnet Beta insights.

Copy link
Contributor

coderabbitai bot commented Feb 7, 2024

Walkthrough

This update introduces new API and gRPC endpoints for the Mainnet Beta, enhancing connectivity and data accessibility. Additionally, it launches a new analytics website, providing users with a comprehensive view of network performance and statistics. These changes aim to improve user experience and facilitate easier integration with the Celestia network.

Changes

File Path Change Summary
nodes/mainnet.md Added new API and gRPC endpoints: celestia.rpc.kjnodes.com, celestia.api.kjnodes.com, celestia.grpc.kjnodes.com:443. Introduced a new analytics website: services.kjnodes.com/mainnet/celestia/slashboard.

Poem

In the digital meadow, under the cybernetic sky,
A new portal opens, as data waves goodbye.
🌐🐰 With a hop and a skip, to new nodes, we latch,
"To the future!" we cheer, with every patch.

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.
  • 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 from git 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
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 0bada64 and 6624ea5.
Files selected for processing (1)
  • nodes/mainnet.md (4 hunks)
Additional comments: 4
nodes/mainnet.md (4)
  • 113-113: Ensure the new RPC endpoint celestia.rpc.kjnodes.com is accessible and correctly integrated into the network's infrastructure.
  • 132-132: Verify the API endpoint celestia.api.kjnodes.com for accessibility and correct integration with the network's services.
  • 150-150: Confirm the gRPC endpoint celestia.grpc.kjnodes.com:443 is accessible, properly secured, and integrated with the network's gRPC services.
  • 226-226: Check the accessibility and content relevance of the new analytics website https://services.kjnodes.com/mainnet/celestia/slashboard to ensure it provides valuable insights for Mainnet Beta users.

@jcstein jcstein merged commit a60eef4 into celestiaorg:main Feb 7, 2024
1 of 2 checks passed
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