Skip to content

Releases: XRPLF/rippled

rippled (XRP Ledger server) Version 2.0.0

09 Jan 15:05
2b0313d
Compare
Choose a tag to compare

rippled (XRP Ledger server) Version 2.0.0-rc7 (release candidate)

05 Jan 21:02
350d213
Compare
Choose a tag to compare

This is a release candidate. There are no code changes in rc7 vs. rc6; rather, we have only added a flag to override a superfluous error during the build process (which blocks packaging).

  • General availability for api_version: 2. In order for requests to experience breaking changes, you must specify "api_version": 2. Thus, rippled 2.0 is backward-compatible for most users.
    • The "DeliverMax" field reflects the maximum amount that the payment may deliver. To get the amount of a payment, use the "delivered_amount" field.
    • 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".
    • The "ledger_index" is now always returned as an integer (not a string).
  • Notable performance improvements in TPS (transactions per second) throughput.
  • XLS-38 sidechains support, adding 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 improved since the previous major version.

Amendments

rippled 2.0.0 is expected to include the following new amendments:

Testing Credits

  • Thanks to @sgramkumar and others for continued testing.

What's Changed

  • Ignore python error about modifying system python by @legleux in #4863

Full Changelog: 2.0.0-rc6...2.0.0-rc7

rippled (XRP Ledger server) Version 2.0.0-rc6 (release candidate)

21 Dec 00:25
ca31981
Compare
Choose a tag to compare

This is a release candidate.

  • Includes api_version: 2 general availability. Since you must specify "api_version": 2 in your requests to get the breaking changes, rippled 2.0 is backward-compatible for most users.
    • The "DeliverMax" field reflects the maximum amount that the payment may deliver. To get the amount of a payment, use the "delivered_amount" field.
    • 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".
    • The "ledger_index" is now always returned as an integer (not a string).
  • Notable performance improvements in TPS (transactions per second) throughput.
  • XLS-38 sidechains support, adding 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 improved 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 #4292
  • fixDisallowIncomingV1 by @dangell7 in #4721
  • DID: Decentralized identifiers (DIDs) (XLS-40) by @mvadari in #4636
  • fixFillOrKill: fix offer crossing with tfFillOrKill #4694

Testing Credits

  • Thanks to @sgramkumar and others for continued testing.

What's Changed

New Contributors

Full Changelog: 2.0.0-rc5...2.0.0-rc6

rippled (XRP Ledger server) Version 2.0.0-rc5 (release candidate)

04 Dec 17:32
46f3d3e
Compare
Choose a tag to compare

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).
  • 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 #4292
  • fixDisallowIncomingV1 by @dangell7 in #4721
  • DID: Decentralized identifiers (DIDs) (XLS-40) by @mvadari in #4636
  • fixFillOrKill: fix offer crossing with tfFillOrKill #4694

Testing Credits

  • Thanks to @sgramkumar and others for continued testing.

What's Changed

New Contributors

Full Changelog: 2.0.0-rc4...2.0.0-rc5

rippled (XRP Ledger server) Version 2.0.0-rc4 (release candidate)

29 Nov 23:47
4316464
Compare
Choose a tag to compare

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 #4292
  • fixDisallowIncomingV1 by @dangell7 in #4721
  • DID: Decentralized identifiers (DIDs) (XLS-40) by @mvadari in #4636
  • fixFillOrKill: 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

rippled (XRP Ledger server) Version 2.0.0-rc3 (release candidate)

28 Nov 00:16
8ec475b
Compare
Choose a tag to compare

This is a release candidate.

  • Includes api_version 2 general availability.
    • The "DeliverMax" field name clarifies that the field is the maximum amount that the payment may deliver. To get the amount of a payment, use the "delivered_amount" field. "DeliverMax" is provided for all Payment transactions regardless of api_version.
    • In api_version: 2, the "Amount" field is removed. In most cases, the field you want is "delivered_amount". But if you really, really want the field formerly known as "Amount", then look for "DeliverMax".
  • 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
  • Lastly, 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 #4292
  • fixDisallowIncomingV1 by @dangell7 in #4721
  • DID: Decentralized identifiers (DIDs) (XLS-40) by @mvadari in #4636
  • fixFillOrKill: fix offer crossing with tfFillOrKill #4694 (not in 2.0.0-b4)

What's Changed

New Contributors

Testing Credits

  • Thanks to @sgramkumar and others for testing this release.

Full Changelog: 2.0.0-b4...2.0.0-rc3

rippled (XRP Ledger server) Version 2.0.0-b4 (beta)

24 Oct 20:34
2a66bb3
Compare
Choose a tag to compare

This is a beta for the next release.

When finalized, the next stable release of rippled is expected to be the last release for 2023 (given the holidays in Nov/Dec). The major version is bumped because:

  • api_version 2 general availability is expected.
    • The "DeliverMax" field name clarifies that the field is the maximum amount that the payment may deliver. To get the amount of a payment, use the "delivered_amount" field. "DeliverMax" is provided for all Payment transactions regardless of api_version.
    • In api_version: 2, the "Amount" field is removed. In most cases, the field you want is "delivered_amount". But if you really, really want the field formerly known as "Amount", then look for "DeliverMax".
  • Notable performance improvements in TPS (transactions per second): up to 3,900 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
  • Lastly, many aspects of the code have been refactored and changed since the previous major version bump.

Amendments

rippled 2.0.0 is expected to include the following new amendments:

  • XChainBridge: side chains (XLS-38) by @seelabs in #4292
  • fixDisallowIncomingV1 by @dangell7 in #4721
  • DID: Decentralized identifiers (DIDs) (XLS-40) by @mvadari in #4636
  • fixFillOrKill: fix offer crossing with tfFillOrKill #4694 (not in 2.0.0-b4)

What's Changed

New Contributors

Full Changelog: 2.0.0-b3...2.0.0-b4

rippled (XRP Ledger server) Version 2.0.0-b3 (beta)

18 Oct 23:32
1fc1eb9
Compare
Choose a tag to compare

This is a beta for the next release.

When finalized, the next stable release of rippled is expected to be the last release for 2023 (given the holidays in Nov/Dec). The major version is bumped because:

  • api_version 2 general availability is expected.
  • Notable performance improvements in TPS (transactions per second): up to 3,900 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
  • Lastly, many aspects of the code have been refactored and changed since the previous major version bump.

What's Changed

New Contributors

Full Changelog: 2.0.0-b2...2.0.0-b3

rippled (XRP Ledger server) Version 2.0.0-b2 (beta)

25 Sep 21:59
2c56d9f
Compare
Choose a tag to compare

This is a beta for the next release.

Highlights:

  • APIv2(gateway_balances, channel_authorize): update errors (#4618)
  • Accept all valid currency codes in API (#4566)

When finalized, the next stable release of rippled is expected to be the last release for 2023 (given the holidays in Nov/Dec). The major version is bumped because:

  • api_version 2 general availability is expected.
    • This api_version is not available yet (except in beta, requiring a configuration change), but it will be in the next release.
  • Notable performance improvements in TPS (transactions per second).
  • XLS-38 sidechains support
    • This is a large change and adds significant new functionality to the protocol.
  • Lastly, many aspects of the code have been refactored and changed since the previous major version bump.

What's Changed

New Contributors

Full Changelog: 2.0.0-b1...2.0.0-b2

rippled (XRP Ledger server) Version 2.0.0-b1 (beta)

15 Sep 21:19
046d0c2
Compare
Choose a tag to compare

This is a beta for the next release.

Highlights:

When finalized, the next stable release of rippled is expected to be the last release for 2023 (given the holidays in Nov/Dec). The major version is bumped for the following reasons:

  • api_version 2 general availability
    • This api_version is not available yet (except in beta, requiring a configuration change), but it will be in the next release.
  • Notable performance improvements in TPS (transactions per second).
  • XLS-38 sidechains support
    • This is a large change and adds significant new functionality to the protocol.
  • Lastly, many aspects of the code have been refactored and changed since the previous major version bump.

(Note that the replacement for getting and setting thread name (#4312) was reverted, so it is not in this release.)

What's Changed

New Contributors

Full Changelog: 1.12.0...2.0.0-b1