Added Public CasperLabs JSON-RPC Endpoints #1466
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ACStone-MTS
approved these changes
Jun 19, 2024
Co-authored-by: Adam Stone <[email protected]>
|
Merging on behalf of @dylanireland. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR fix/introduce?
This PR adds the public CasperLabs JSON-RPC endpoints as the preferred method of communicating with the network.
Additional context
The current method encourages choosing from a list of currently online Casper Network peers, many of which may have RPC ports disabled or could theoretically act in malicious ways.
Checklist
yarn install && yarn run build.../../faq/faq-general.md- instead of introducing absolute file path, or relative/absolute URL.yarn run check:externals.