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

Modify Allnodes RPC #179

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Modify Allnodes RPC #179

wants to merge 1 commit into from

Conversation

3eph1r0th
Copy link

@3eph1r0th 3eph1r0th commented Oct 27, 2024

Summary by CodeRabbit

  • New Features
    • Introduced four new public endpoints for the Evmos mainnet and testnets, including a new gRPC endpoint.
  • Changes
    • Updated maintainer information for existing endpoints to reflect the consolidation under Allnodes.
    • Removed three outdated endpoints previously associated with PublicNode (by Allnodes).

Copy link
Contributor

coderabbitai bot commented Oct 27, 2024

Walkthrough

The document docs/develop/api/networks.mdx has been updated to reflect changes in the public endpoints for the Evmos mainnet and testnets. Three endpoints previously associated with PublicNode (by Allnodes) have been removed, while four new endpoints have been added under the simplified label of Allnodes. This includes the introduction of a new gRPC endpoint and adjustments to the maintainer designation for existing endpoints.

Changes

File Path Change Summary
docs/develop/api/networks.mdx - Removed endpoints: https://evmos-evm.publicnode.com, https://evmos-rpc.publicnode.com, https://evmos-rest.publicnode.com (all previously maintained by PublicNode (by Allnodes))
- Added endpoints: https://evmos-evm-rpc.publicnode.com (Ethereum JSON-RPC, maintained by Allnodes), https://evmos-grpc.publicnode.com (Cosmos gRPC, maintained by Allnodes)

Poem

🐇 In the meadow where endpoints play,
New paths emerge, bright as day.
Allnodes leads with a hop and a skip,
GRPC joins the joyful trip!
Old nodes fade, but new ones gleam,
A network of dreams, a coder's dream! 🌼


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

Copy link

netlify bot commented Oct 27, 2024

Deploy Preview for dancing-hummingbird-242a98 ready!

Name Link
🔨 Latest commit 1c1659c
🔍 Latest deploy log https://app.netlify.com/sites/dancing-hummingbird-242a98/deploys/671dd7f4cad1400008f697a3
😎 Deploy Preview https://deploy-preview-179--dancing-hummingbird-242a98.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

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.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
docs/develop/api/networks.mdx (1)

50-53: LGTM! Consider standardizing the GRPC notation.

The endpoint changes look good. The maintainer designation has been standardized, and the new gRPC endpoint enhances the service offerings. One minor suggestion for consistency:

Consider using gRPC instead of GRPC in line 53 to match the notation used in other entries (e.g., line 13: "Cosmos gRPC").

-| `https://evmos-grpc.publicnode.com`           | `Cosmos` `GRPC`        | [Allnodes](https://evmos.publicnode.com/) | Pruned  |
+| `https://evmos-grpc.publicnode.com`           | `Cosmos` `gRPC`        | [Allnodes](https://evmos.publicnode.com/) | Pruned  |
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 3710b43 and 1c1659c.

📒 Files selected for processing (1)
  • docs/develop/api/networks.mdx (1 hunks)

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.

1 participant