XRPL server v1.8.0 docs #1233
Merged
XRPL server v1.8.0 docs #1233
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
Peer protocol renamed from RTXP/1.2 to XRPL/2.0
Upgrade script no longer restarts the server. [v1.8.0]
subscribe updates for 1.8.0
Amendment default votes and retirement
Shards updates for v1.8.0
- Move recommended specs first for people who skim - Mention of automatic [node_size] - No longer recommending RocksDB in any circumstance - Reduced usage of the `rippled` name.
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.
Here are all the 1.8.0 changes (through rc1) that affect documentation:
account_history_tx_streamnode_to_shardmethodvalidationsandmanifestssubscription streams (previously these returnedreportingUnsupported)validationsstream now that the HardenedValidations amendment is enabledsigner_listfield of the account_info response.)XRPL/2.0now (formerlyRTXP/1.2) and servers on the legacy protocol can no longer connect - minor mention in Peer Protocol article.