Skip to content

rippled Version 0.22.0
Compare
Choose a tag to compare
@mDuo13 mDuo13 released this 23 May 23:48
· 5128 commits to develop since this release
0.22.0
d9a0181

rippled version 0.22.0 has been released. This release is currently the tip of the develop/ branch and can be found on GitHub at: https://github.com/ripple/rippled/tree/develop The tag is 0.22.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.22.0

This is a critical release affecting transaction processing. All partners should update immediately.

Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:

This release incorporates significant improvements which may not warrant separate entries but are incorporated into the feature changes as summary lines. Please refer to the Git commit history for more information.

Toolchain support

The minimum supported version of GCC used to compile rippled is v4.8. Please follow these instructions if you have not upgraded already.

A minimum of 4GB of RAM are required to successfully compile this release.

The minimum supported version of libBOOST is v1.55. You must upgrade to this release or later to successfully compile this release. Please follow these instructions if you have not upgraded already.

Key release features

  • PeerFinder
    • Actively guides network topology.
    • Scrubs listening advertisements based on connectivity checks.
    • Redirection for new nodes when existing nodes are full.
  • Memos
    • Transactions can optionally include a short text message, which optionally can be encrypted.
  • Database
    • Improved management of I/O resources.
    • Better performance accessing historical data.
  • PathFinding
    • More efficient search algorithm when computing paths

Major Partner Issues Fixed

  • Transactions
    • Malleability: Ability to ensure that signatures are fully canonical.
  • PathFinding
    • Less time needed to get the first path result!
  • Database
    • Eliminated "meltdowns" caused when fetching historical ledger data.

Significant Changes

  • Cleaned up logic which controls when ledgers are fetched and under what conditions.
  • Cleaned up file path calculation for database files.
  • Changed dispatcher for WebSocket requests.
  • Cleaned up multithreading mechanisms.
  • Fixed custom currency code parsing.
  • Optimized transaction node lookup circumstances in the node store.
Assets 2
Loading