-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Proposed 1.7.0-b1 #3599
Merged
Merged
Proposed 1.7.0-b1 #3599
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
Tickets are a mechanism to allow for the "out-of-order" execution of transactions on the XRP Ledger. This commit, if merged, reworks the existing support for tickets and introduces support for 'ticket batching', completing the feature set needed for tickets. The code is gated under the newly-introduced `TicketBatch` amendment and the `Tickets` amendment, which is not presently active on the network, is being removed. The specification for this change can be found at: XRPLF/XRPL-Standards#16
With few exceptions, servers will typically receive multiple copies of any given message from its directly connected peers. For servers with several peers this can impact the processing latency and force it to do redundant work. Proposal and validation messages are often relayed with extremely high redundancy. This commit, if merged, introduces experimental code that attempts to optimize the relaying of proposals and validations by allowing servers to instruct their peers to "squelch" delivery of selected proposals and validations. Servers making squelching decisions by a process that evaluates the fitness and performance of a given server and randomly selecting a subset of the best candidates. The experimental code is presently disabled and must be explicitly enabled by server operators that wish to test it.
When attempting to load a validator list from a configured site, attempt to reuse the last IP that was successfully used if that IP is still present in the DNS response. Otherwise, randomly select an IP address from the list of IPs provided by the DNS system. This commit fixes #3494.
Some RPC commands return `ledger_index` as a quoted numeric string. This change allows the returned value to be directly copied and used for follow-on RPC commands. This commit fixes #3533
Based on the PR template used by xpring-eng: https://raw.githubusercontent.com/xpring-eng/.github/master/.github/pull_request_template.md
* Distinguish between recent and historical shards * Allow multiple storage paths for historical shards * Add documentation for this feature * Add unit tests
The "/vl" HTTP endpoint can be used to request a particular UNL from a rippled instance. This commit, if merged, includes the public key of the requested list in the response. This commit fixes #3392
The job queue can impose limits of how many jobs of a particular type can be queued. This commit makes the previously hard-coded limit associated with transactions configurable by the server's operator. Servers that have increased memory capacity or which expect to see an influx of transactions can increase the number of transactions their server will be able to queue. This commit fixes #3556.
Event hooks will allow accounts to introduce configurable behavior in response to send and receive events.
Some transactions specify a keylet directly (Checks, for example). In those cases, the assert will trigger even though there is no error.
Use C++17 constant expressions to calculate the inverse alphabet map at compile time instead of at runtime. Remove support for encoding & decoding tokens using the Bitcoin alphabet.
This commit fixes #3550.
Support for IPv6 messages was added with commit 08382d8 and version 1.1.0. No peer presently connected to the network in a useful capacity fails to understand v2 messages. This commit removes the code that generates and processes v1 messages and deletes legacy messages from the protocol buffer definition file.
carlhua
approved these changes
Sep 3, 2020
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.
If merged, this PR will: