Releases: XRPLF/rippled
rippled Version 0.30.0
a8859b4
vinniefalco
Vinnie Falco
rippled 0.30.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.30.0
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:
commit a8859b495b552fe1eb140771f0f2cb32d11d2ac2
Author: Vinnie Falco <vinnie.falco@gmail.com>
Date: Wed Oct 21 18:26:02 2015 -0700
Set version to 0.30.0
This release incorporates a number of important features, bugfixes and functional improvements. Please refer to the Git commit history for more detailed information.
Release Overview
As part of Ripple Labs’ ongoing commitment toward protocol security, the rippled team would like to release rippled 0.30.0.
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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j[number of CPUs - 1].
New Features
- Honor markers in ledger_data requests (RIPD-1010).
- New Amendment - TrustSetAuth (Not currently enabled) Create zero balance trust lines with auth flag (RIPD-1003): this allows a TrustSet transaction to create a trust line if the only thing being changed is setting the tfSetfAuth flag.
- Randomize the initial transaction execution order for closed ledgers based on the hash of the consensus set (RIPD-961). Activates on October 27, 2015 at 11:00 AM PCT.
- Differentiate path_find response (RIPD-1013).
- Convert all of an asset (RIPD-655).
Improvements
- SHAMap improvements.
- Upgrade SQLite from 3.8.8.2 to 3.8.11.1.
- Limit the number of offers that can be consumed during crossing (RIPD-1026).
- Remove unfunded offers on tecOVERSIZE (RIPD-1026).
- Improve transport security (RIPD-1029): to take full advantage of the improved transport security, servers with a single, static public IP address should add it to their configuration file, as follows:
[overlay]
public_ip=<ip_address>
Development-Related Updates
- Transitional support for gcc 5.2: to enable support define the environmental variable
RIPPLED_OLD_GCC_ABI=1 - Transitional support for C++ 14: to enable support define the environment variable
RIPPLED_USE_CPP_14=1 - Visual Studio 2015 support
- Updates to integration tests
- Add uptime to crawl data (RIPD-997)
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.29.0
rippled 0.29.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/commits/0.29.0
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:
commit 5964710f736e258c7892e8b848c48952a4c7856c
Author: Nik Bougalis <nikb@bougalis.net>
Date: Tue Aug 4 13:22:45 2015 -0700
Set version to 0.29.0
This release incorporates a number of important features, bugfixes and functional improvements. Please refer to the Git commit history for more detailed information.
Release Overview
As part of Ripple Labs’ ongoing commitment toward protocol security, the rippled team would like to announce rippled release 0.29.0.
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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j[number of CPUs - 1].
New Features
- Subscription stream for validations (RIPD-504)
Deprecated features
- Disable Websocket ping timer
Bug Fixes
- Fix off-by one bug that overstates the account reserve during OfferCreate transaction. Activates August 17, 2015.
- Fix funded offer removal during Payment transaction (RIPD-113). Activates August 17, 2015.
- Fix display discrepancy in fee.
Improvements
- Add “quality” field to account_offers API response: quality is defined as the exchange rate, the ratio taker_pays divided by taker_gets.
- Add full_reply field to path_find API response: full_reply is defined as true/false value depending on the completed depth of pathfinding search (RIPD-894).
- Add DeliverMin transaction field (RIPD-930). Activates August 17, 2015.
Development-Related Updates
- Add uptime to crawl data (RIPD-997).
- Add IOUAmount and XRPAmount: these numeric types replace the monolithic functionality found in STAmount (RIPD-976).
- Log metadata differences on built ledger mismatch.
- Add enableTesting flag to applyTransactions.
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.28.2
rippled 0.28.2 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/commits/release
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:
commit 6374aad9bc94595e051a04e23580617bc1aaf300
Author: Vinnie Falco <vinnie.falco@gmail.com>
Date: Tue Jul 7 09:21:44 2015 -0700
Set version to 0.28.2
This release incorporates a number of important features, bugfixes and functional improvements. Please refer to the Git commit history for more detailed information.
Release Overview
As part of Ripple Labs’ ongoing commitment toward protocol security, the rippled team would like to announce rippled release 0.28.2. This release is necessary for compatibility with OpenSSL v.1.0.1n and later.
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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j[number of CPUs - 1].
The minimum supported version of Boost is v1.57.0. You must upgrade to this release or later to successfully compile this release of rippled. Please follow these instructions if you have not upgraded already.
rippled.cfg Updates
For [ips] stanza, a port must be specified for each listed IP address with the space between IP address and port, ex.: r.ripple.com 51235 (RIPD-893)
New Features
- New API: gateway_balances to get a gateway's hot wallet balances and total obligations.
Deprecated features
- Removed temp_db (RIPD-887)
Improvements
- Improve peer send queue management
- Support larger EDH keys
- More robust call to get the valid ledger index
- Performance improvements to transactions application to open ledger
Development-Related Updates
- New Env transaction testing framework for unit testing
- Fix MSVC link
- C++ 14 readiness
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.28.1
rippled 0.28.1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.28.1
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:
commit 399c43cae6e90a428e9ce6a988123972b0f03c99
Author: Miguel Portilla <miguelportilla@pobros.com>
Date: Wed May 20 13:30:54 2015 -0400
Set version to 0.28.1
This release incorporates a number of important features, bugfixes and functional improvements. Please refer to the Git commit history for more detailed 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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j[number of CPUs - 1].
The minimum supported version of Boost is v1.57.0. You must upgrade to this release or later to successfully compile this release of rippled. Please follow these instructions if you have not upgraded already.
New Features
Bug fixes
- Expedite zero flow handling for offers
- Fix offer crossing when funds are the limiting factor
Deprecated features
- Wallet_accounts and generator maps (RIPD-804)
Improvements
- Control ledger query depth based on peers latency
- Improvements to ledger history fetches
- Improve RPC ledger synchronization requirements (RIPD-27, RIPD-840)
- Eliminate need for ledger in delivered_amount calculation (RIPD-860)
- Improvements to JSON parsing
Development-Related Updates
- Add historical ledger fetches per minute to get_counts
- Compute validated ledger age from signing time
- Remove unused database table (RIPD-755)
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.28.0
rippled 0.28.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.28.0
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:
commit 7efd0ab0d6ef017331a0e214a3053893c88f38a9
Author: Vinnie Falco <vinnie.falco@gmail.com>
Date: Fri Apr 24 18:57:36 2015 -0700
Set version to 0.28.0
This release incorporates a number of important features, bugfixes and functional improvements. Please refer to the Git commit history for more detailed information.
Release Overview
As part of Ripple Labs’ ongoing commitment toward improving the protocol, the rippled team is excited to announce autobridging — a feature that allows XRP to serve as a bridge currency. Autobridging enhances utility and has the potential to expose more of the network to liquidity and improve prices. For more information please refer to the autobridging blog post.
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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j[number of CPUs - 1].
The minimum supported version of Boost is v1.57.0. You must upgrade to this release or later to successfully compile this release of rippled. Please follow these instructions if you have not upgraded already.
Important rippled.cfg update
With rippled version 0.28, the rippled.cfg file must be changed according to these instructions:
- Change any entries that say
admin = allow to admin =
- For most installations, 127.0.0.1 will preserve current behavior. 0.0.0.0 may be specified to indicate "any IP" but cannot be combined with other IP addresses. Use of 0.0.0.0 may introduce severe security risks and is not recommended. See docs/rippled-example.cfg for more information.
More Strict Requirements on MemoType
The requirements on the contents of the MemoType field, if present, are more strict than the previous version. Transactions that can successfully be submitted to 0.27.4 and earlier may fail in 0.28.0. For details, please refer to updated memo documentation for details. Partners should check their implementation to make sure that their MemoType follows the new rules.
New Features
- Autobridging implementation (RIPD-423). This feature will be turned on May 12, 2015.
- Combine history_ledger_index and online_delete settings in rippled.cfg (RIPD-774).
- Claim a fee when a required destination tag is not specified (RIPD-574).
- Require the master key when disabling the use of the master key or when enabling 'no freeze' (RIPD-666).
- Change the port setting admin to accept allowable admin IP addresses (RIPD-820):
- rpc_admin_allow has been removed.
- Comma-separated list of IP addresses that are allowed administrative privileges (subject to username & password authentication if configured).
- 127.0.0.1 is no longer a default admin IP.
- 0.0.0.0 may be specified to indicate "any IP" but cannot be combined with other MIP addresses. Use of 0.0.0.0 may introduce severe security risks and is not recommended.
- Enable Amendments from config file or static data (RIPD-746).
Bug fixes
- Fix payment engine handling of offer ⇔ account ⇔ offer cases (RIPD-639). This fix will take effect on May 12, 2015.
- Fix specified destination issuer in pathfinding (RIPD-812).
- Only report delivered_amount for executed payments (RIPD-827).
- Return a validated ledger if there is one (RIPD-814).
- Refund owner's ticket reserve when a ticket is canceled (RIPD-855).
- Return descriptive error from account_currencies RPC (RIPD-806).
- Fix transaction enumeration in account_tx API (RIPD-734).
- Fix inconsistent ledger_current return (RIPD-669).
- Fix flags --rpc_ip and --rpc_port (RIPD-679).
- Skip inefficient SQL query (RIPD-870)
Deprecated features
- Remove support for deprecated PreviousTxnID field (RIPD-710). This will take effect on May 12, 2015.
- Eliminate temREDUNDANT_SEND_MAX (RIPD-690).
- Remove WalletAdd (RIPD-725).
- Remove SMS support.
Improvements
- Improvements to peer communications.
- Reduce master lock for client requests.
- Update SQLite to 3.8.8.2.
- Require Boost 1.57.
- Improvements to Universal Port (RIPD-687).
- Constrain valid inputs for memo fields (RIPD-712).
- Binary option for ledger command (RIPD-692).
- Optimize transaction checks (RIPD-751).
Development-Related Updates
- Add RPC metrics (RIPD-705).
- Track and report peer load.
- Builds/Test.py will build and test by one or more scons targets.
- Support a --noserver command line option in tests:
- Run npm/integration tests without launching rippled, using a running instance of rippled (possibly in a debugger) instead.
- Works for npm test and mocha.
- Display human readable SSL error codes.
- Better transaction analysis (RIPD-755).
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use:
rippled Version0.27.4
rippled 0.27.4 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.4
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:
commit 92812fe7239ffa3ba91649b2ece1e892b866ec2a
Author: Nik Bougalis <nikb@bougalis.net>
Date: Wed Mar 11 11:26:44 2015 -0700
Set version to 0.27.4
This release includes one new feature. Please refer to the Git commit history for more detailed 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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j[number of CPUs - 1].
The minimum supported version of Boost is v1.57.0. You must upgrade to this release or later to successfully compile this release of rippled. Please follow these instructions if you have not upgraded already.
Bug Fixes
- Limit passes in the payment engine
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.27.3-sp2
rippled 0.27.3-sp2 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.3-sp2
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:
commit f999839e599e131ed624330ad0ce85bb995f02d3
Author: Nik Bougalis <nikb@bougalis.net>
Date: Thu Mar 12 13:37:47 2015 -0700
Set version to 0.27.3-sp2
This release includes one new feature. Please refer to the Git commit history for more detailed 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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j <number of CPUs - 1>.
The minimum supported version of Boost is v1.57.0. You must upgrade to this release or later to successfully compile this release of rippled. Please follow these instructions if you have not upgraded already.
New Features
- Add noripple_check RPC command: this command tells gateways what they need to do to set "Default Ripple" account flag and fix any trust lines created before the flag was set.
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.27.3-sp1
rippled 0.27.3-sp1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.3-sp1
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:
commit 232693419a2c9a8276a0fae991f688f6f01a3add
Author: Nik Bougalis <nikb@bougalis.net>
Date: Wed Mar 11 10:26:39 2015 -0700
Set version to 0.27.3-sp1
This release includes one new feature. Please refer to the Git commit history for more detailed 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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j[number of CPUs - 1].
The minimum supported version of Boost is v1.57.0. You must upgrade to this release or later to successfully compile this release of rippled. Please follow these instructions if you have not upgraded already.
New Features
- Add "Default Ripple" account flag
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.27.3
rippled 0.27.3 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.3
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:
commit 70c2854f7c8a28801a7ebc81dd62bf0d068188f0
Author: Nik Bougalis <nikb@bougalis.net>
Date: Tue Mar 10 14:06:33 2015 -0700
Set version to 0.27.3
This release includes one new feature. Please refer to the Git commit history for more detailed 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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j[number of CPUs - 1].
The minimum supported version of Boost is v1.57.0. You must upgrade to this release or later to successfully compile this release of rippled. Please follow these instructions if you have not upgraded already.
New Features
- Add "Default Ripple" account flag
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.27.2
rippled 0.27.2 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.2
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:
commit 9cc8eec773e8afc9c12a6aab4982deda80495cf1
Author: Nik Bougalis <nikb@bougalis.net>
Date: Sun Mar 1 14:56:44 2015 -0800
Set version to 0.27.2
This release incorporates a number of important bugfixes and functional improvements. Please refer to the Git commit history for more detailed 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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend compiling on (virtual) machines with 8GB of RAM or more. If your build machine has more than one CPU (grep '^processor' /proc/cpuinfo | wc -l), you can use them to assist in the build process by compiling with the command scons -j[number of CPUs - 1].
The minimum supported version of Boost is v1.57.0. You must upgrade to this release or later to successfully compile this release of rippled. Please follow these instructions if you have not upgraded already.
New Features
- NuDB backend option: high performance key/value database optimized for rippled (set “type=nudb” in .cfg).
- Either import RockdDB to NuDB using import tool, or
- Start fresh with NuDB but delete SQLite databases if rippled ran previously with RocksDB:
rm [database_path]/transaction._ [database_path]/ledger._
Bug Fixes
- Fix offer quality bug
Deprecated
- HyperLevelDB, LevelDB, and SQLlite backend options. Use RocksDB for spinning drives and NuDB for SSDs backend options.
Assistance
For assistance, please contact integration@ripple.com
More information
For more information or assistance, the following resources will be of use: