Add Avril14th RPC/API/gRPC

[stefanopier]

Overview

Add Avril14th RPC/API/gRPC endpoints

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
  • Introduced new endpoints for the Mocha Testnet, including an RPC endpoint, an API endpoint, and a gRPC endpoint to enhance connectivity and integration capabilities.

[coderabbitai]

Walkthrough

The update introduces new endpoints for the Mocha testnet, enhancing its infrastructure with additional RPC, API, and gRPC endpoints. This expansion aims to improve access and interaction capabilities for developers and users alike, facilitating a more robust and versatile testing environment.

Changes

File	Change Summary
nodes/mocha-testnet	Added RPC endpoint rpc-mocha-full.avril14th.org, API endpoint https://api-mocha-full.avril14th.org, and gRPC endpoint grpc-mocha-full.avril14th.org.

🐇✨
In the land of code and net,
A new path we set.
With RPC, API, and gRPC, we bet,
On a future, seamlessly met.
Hops and leaps, no fret,
For Mocha's wings are now jet.
🌟🐰

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 2db9987 and efb8e34.

Files selected for processing (1)

• nodes/mocha-testnet.md (3 hunks)

Additional comments: 3

nodes/mocha-testnet.md (3)

• 87-87: The addition of the RPC endpoint rpc-mocha-full.avril14th.org is consistent with the format and purpose of existing RPC endpoints. However, ensure that this endpoint is fully operational and secure before publishing it in the documentation.
• 107-107: The API endpoint https://api-mocha-full.avril14th.org has been added correctly, following the HTTPS protocol which is good for security. Verify that this endpoint is properly configured to handle requests securely and efficiently.
• 128-128: The addition of the gRPC endpoint grpc-mocha-full.avril14th.org follows the pattern of existing gRPC endpoints. It's important to ensure that this endpoint supports secure communication (e.g., via SSL/TLS) to protect data in transit.