This is a release candidate.
- Includes
api_version
2 general availability.- The "DeliverMax" field reflects the maximum amount that the payment may deliver. To get the amount of a payment, use the "delivered_amount" field. "DeliverMax" is now provided for all Payment transactions, and successful transactions include "delivered_amount".
- In api_version: 2, the "Amount" field is removed. In most cases, the field you actually want is "delivered_amount". But if you really want the field formerly known as "Amount", then you can use "DeliverMax".
- In api_version: 2, "ledger_index" is always returned as an integer (not a string).
- Notable performance improvements in TPS (transactions per second): up to 4,300 TPS.
- XLS-38 sidechains support.
- This is a large change and adds significant new functionality to the protocol.
- XLS-40 decentralized identity (DID) support.
- New
server_definitions
method. - Many aspects of the code have been refactored and changed since the previous major version.
Amendments
rippled
2.0.0 is expected to include the following new amendments:
XChainBridge
: side chains (XLS-38) by @seelabs in #4292fixDisallowIncomingV1
by @dangell7 in #4721DID
: Decentralized identifiers (DIDs) (XLS-40) by @mvadari in #4636fixFillOrKill
: fix offer crossing with tfFillOrKill #4694 (not in 2.0.0-b4)
Testing Credits
- Thanks to @sgramkumar and others for continued testing.
What's Changed
- Consistently show ledger_index as integer on JSON output by @Bronek in #4820
- Show DeliverMax in submit_multisigned etc if API v2 selected by @Bronek in #4827
- Proposed 2.0.0-rc4 by @intelliot in #4841
Full Changelog: 2.0.0-rc3...2.0.0-rc4