Rippled Versions Save

Decentralized cryptocurrency blockchain daemon implementing the XRP Ledger protocol in C++

2.2.0-b2

2 weeks ago

Amendments

Pre-release version 2.2.0-b2 introduces two new amendments:

What's Changed

New Contributors

Full Changelog: https://github.com/XRPLF/rippled/compare/2.2.0-b1...2.2.0-b2

2.1.1

4 weeks ago

Version 2.1.1 introduces one new amendment:

What's Changed

  • Fixed a critical bug when handling large synthetic AMM offers in the payment engine.

Full Changelog: https://github.com/XRPLF/rippled/compare/2.1.0...2.1.1

2.2.0-b1

1 month ago

What's Changed

Full Changelog: https://github.com/XRPLF/rippled/compare/2.1.0...2.2.0-b1

2.1.0

2 months ago

Version 2.1.0 introduces two new amendments:

What's Changed

Full Release Notes for 2.1.0 (xrpl.org)

Full Changelog: https://github.com/XRPLF/rippled/compare/2.0.1...2.1.0

Testing Credits

  • Thanks to @sgramkumar and others for continued testing.

Bug Bounties and Responsible Disclosures:

We welcome reviews of the rippled code and urge researchers to responsibly disclose any issues they may find.

To report a bug, please send a detailed report to: [email protected]

2.1.0-rc1

2 months ago

Version 2.1.0 introduces two new amendments:

What's Changed

Full Changelog: https://github.com/XRPLF/rippled/compare/2.0.1...2.1.0-rc1

Testing Credits

  • Thanks to @sgramkumar and others for continued testing.

2.0.1

2 months ago

This release fixes a few bugs. There are no new features over version 2.0.0.

Highlights:

  • Fixes unbounded memory growth when running the path_find command.
  • Fixes a bug that, in some situations, results in online deletion causing delays in persisting records to disk.
  • A new line in cfg/rippled-example.cfg sets send_queue_limit = 500. Consider adopting this setting in your own rippled.cfg in the appropriate stanza(s) for ws and wss port(s).
    • When the setting is not specified, the default value is 100. At 100, during times when there are >200 transactions per ledger, rippled will disconnect WebSocket clients that subscribe to the transactions stream.
    • Clients receive a disconnected message with code 1008 or a Client too slow disconnection.
    • Using send_queue_limit = 500 fixes this issue.
  • Fixes an assert which could occur under heavy load from unprivileged WebSocket connections. (Assertions are disabled in release builds.)

Testing Credits

  • Thanks to @sgramkumar and others for continued testing.

What's Changed

Full Changelog: https://github.com/XRPLF/rippled/compare/2.0.0...2.0.1

2.0.1-rc1

3 months ago

This is a release candidate for a hotfix release. There are no new features over 2.0.0; only bug fixes.

Highlights:

  • Fixes unbounded memory growth when running the path_find command.
  • Fixes a bug that, in some situations, results in online deletion causing delays in persisting records to disk.
  • A new line in cfg/rippled-example.cfg sets send_queue_limit = 500. Consider adopting this setting in your own rippled.cfg in the appropriate stanza(s) for configured ws and wss port(s).
    • When the setting is not specified in the config, the default value is 100. At 100, during times when there are >200 transactions per ledger, rippled will disconnect WebSocket clients that subscribe to the transactions stream.
    • Clients receive a disconnected message with code 1008 or a Client too slow disconnection.
    • Using send_queue_limit = 500 fixes this issue.

Testing Credits

  • Thanks to @sgramkumar and others for continued testing.

What's Changed

Note: for completeness, the following has been updated to show the changes since 2.0.0, the last stable release (not just 2.0.1-b1).

Full Changelog: https://github.com/XRPLF/rippled/compare/2.0.0...2.0.1-rc1

2.0.1-b1

3 months ago

What's Changed

Full Changelog: https://github.com/XRPLF/rippled/compare/2.0.0...2.0.1-b1

2.0.0

3 months ago

Release notes for rippled 2.0.0

Blog post (xrpl.org)

2.0.0-rc7

3 months ago

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:

  • 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 by @gregtatcam in #4694

Testing Credits

  • Thanks to @sgramkumar and others for continued testing.

What's Changed

Full Changelog: https://github.com/XRPLF/rippled/compare/2.0.0-rc6...2.0.0-rc7