Releases: XRPLF/rippled
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 <[email protected]>
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 [email protected]
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 <[email protected]>
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 [email protected]
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 <[email protected]>
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 [email protected]
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 <[email protected]>
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 [email protected]
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 <[email protected]>
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 [email protected]
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.27.1
rippled 0.27.1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.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 95973ba3e8b0bd28eeaa034da8b806faaf498d8a
Author: Vinnie Falco <[email protected]>
Date: Tue Feb 24 13:31:13 2015 -0800
Set version to 0.27.1
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
- RocksDB to NuDB import tool (RIPD-781, RIPD-785): custom tool specifically designed for very fast import of RocksDB nodestore databases into NuDB
Bug Fixes
- Fix streambuf bug
Improvements
- Update RocksDB backend settings
- NuDB improvements:
- Limit size of mempool (RIPD-787)
- Performance improvements (RIPD-793, RIPD-796): changes in Nudb to improve speed, reduce database size, and enhance correctness. The most significant change is to store hashes rather than entire keys in the key file. The output of the hash function is reduced to 48 bits, and stored directly in buckets.
Experimental
- Add /crawl cgi request feature to peer protocol (RIPD-729): adds support for a cgi /crawl request, issued over HTTPS to the configured peer protocol port. The response to the request is a JSON object containing the node public key, type, and IP address of each directly connected neighbor. The IP address is suppressed unless the neighbor has requested its address to be revealed by adding "Crawl: public" to its HTTP headers. This field is currently set by the peer_private option in the rippled.cfg file.
Assistance
For assistance, please contact [email protected]
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.27.0
rippled 0.27.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.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 c6c8e5d70c6fbde02cd946135a061aa77744396f
Author: Vinnie Falco <[email protected]>
Date: Mon Jan 26 10:56:11 2015 -0800
Set version to 0.27.0
This release incorporates a number of important bugfixes and functional improvements. Please refer to the Git commit history for more detailed information.
Release Overview
The rippled team is proud to release rippled 0.27.0. This new version includes many exciting features that will appeal to our users. The team continues to work on stability, scalability, and performance.
The first feature is Online Delete. This feature allows rippled to maintain it’s database of previous ledgers within a fixed amount of disk space. It does this while allowing rippled to stay online and maintain an administrator specify minimum number of ledgers. This means administrators with limited disk space will no longer need to manage disk space by periodically manually removing the database. Also, with the previously existing backend databases performance would gradually degrade as the database grew in size. In particular, rippled would perform poorly whenever the backend database performed ever growing compaction operations. By limiting rippled to less history, compaction is less resource intensive and systems with less disk performance can now run rippled.
Additionally, we are very excited to include Universal Port. This feature allows rippled's listening port to handshake in multiple protocols. For example, a single listening port can be configured to receive incoming peer connections, incoming RPC commands over HTTP, and incoming RPC commands over HTTPS at the same time. Or, a single port can receive both Websockets and Secure Websockets clients at the same.
Finally, a new, experimental backend database, NuDB, has been added. This database was developed by Ripple Labs to take advantage of rippled’s specific data usage profile and performs much better than previous databases. Significantly, this database does not degrade in performance as the database grows. Very excitingly, this database works on OS X and Windows. This allows rippled to use these platforms for the first time.
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
The format of the configuration file has changed. If upgrading from a previous version of rippled, please see the migration instructions below.
New Features
- SHAMapStore Online Delete (RIPD-415): Makes rippled configurable to support deletion of all data in its key-value store (nodestore) and ledger and transaction SQLite databases based on validated ledger sequence numbers. See doc/rippled-example.cfg for configuration setup.
- Universal Port. See necessary config changes below.
- Config "ledger_history_index" option (RIPD-559)
Bug Fixes
- Fix pathfinding with multiple issuers for one currency (RIPD-618)
- Fix account_lines, account_offers and book_offers result (RIPD-682)
- Fix pathfinding bugs (RIPD-735)
- Fix RPC subscribe with multiple books (RIPD-77)
- Fix account_tx API
Improvements
- Improve the human-readable description of the tesSUCCESS code
- Add 'delivered_amount' to Transaction JSON (RIPD-643): The synthetic field 'delivered_amount' can be used to determine the exact amount delivered by a Payment without having to check the DeliveredAmount field, if present, or the Amount field otherwise.
Development-Related Updates
- HTTP Handshaking for Peers on Universal Port (RIPD-446)
- Use asio signal handling in Application (RIPD-140)
- Build dependency on Boost 1.57.0
- Support a "no_server" flag in test config
- API for improved Unit Testing (RIPD-432)
- Option to specify rippled path on command line (--rippled=)
Experimental
- NuDB backend option: high performance key/value database optimized for rippled (set “type=nudb” in .cfg)
Migration Instructions
With rippled version 0.27.0, the rippled.cfg file must be changed according to these instructions:
- Add new stanza -
[server]. This section will contain a list of port names and key/value pairs. A port name must start with a letter and contain only letters and numbers. The name is not case-sensitive. For each name in this list, rippled will look for a configuration file section with the same name and use it to create a listening port. To simplify migration, you can use port names from your previous version of rippled.cfg (see Section 1. Server for detailed explanation in doc/rippled-example.cfg). For example:
[server]
rpc_port
peer_port
websocket_port
ssl_key = <set value to your current [rpc_ssl_key] or [websocket_ssl_key] setting>
ssl_cert = <set value to your current [rpc_ssl_cert] or [websocket_ssl_cert] setting>
ssl_chain = <set value to your current [rpc_ssl_chain] or [websocket_ssl_chain] setting>
- For each port name in
[server]stanza, add separate stanzas. For example:
[rpc_port]
port = <set value to your current [rpc_port] setting, usually 5005>
ip = <set value to your current [rpc_ip] setting, usually 127.0.0.1>
admin = allow
protocol = https
[peer_port]
port = <set value to your current [peer_port], usually 51235>
ip = <set value to your current [peer_ip], usually 0.0.0.0>
protocol = peer
[websocket_port]
port = <your current [websocket_port], usually 6006>
ip = <your current [websocket_ip], usually 127.0.0.1>
admin = allow
protocol = wss
- Remove current
[rpc_port],[rpc_ip],[rpc_allow_remote],[rpc_ssl_key],[rpc_ssl_cert],and[rpc_ssl_chain],[peer_port],[peer_ip],[websocket_port],[websocket_ip]settings from rippled.cfg - If you allow untrusted websocket connections to your rippled, add
[websocket_public_port]stanza under[server]section and replace websocket public settings with[websocket_public_port]section:
[websocket_public_port]
port = <your current [websocket_public_port], usually 5005>
ip = <your current [websocket_public_ip], usually 127.0.0.1>
protocol = ws ← make sure this is ws, not wss`
- Remove
[websocket_public_port],[websocket_public_ip],[websocket_ssl_key],[websocket_ssl_cert],[websocket_ssl_chain]settings from rippled.cfg - Disable
[ssl_verify]section by setting it to 0 - Migrate the remaining configurations without changes. To enable online delete feature, check Section 6. Database in doc/rippled-example.cfg
Integration Notes
With this release, integrators should deprecate the "DeliveredAmount" field in favor of "delivered_amount."
For Transactions That Occurred Before January 20, 2014:
- If amount actually delivered is different than the transactions “Amount” field
- "delivered_amount" will show as unavailable indicating a developer should use caution when processing this payment.
- Example: A partial payment transaction (tfPartialPayment).
- Otherwise
- "delivered_amount" will show the correct destination balance change.
For Transactions That Occur After January 20, 2014:
- If amount actually delivered is different than the transactions “Amount” field
- A "delivered_amount" field will determine the destination amount change
- Example: A partial payment transaction (tfPartialPayment).
- Otherwise
- "delivered_amount" will show the correct destination balance change.
Assistance
For assistance, please contact [email protected]
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.26.4
rippled 0.26.4 has been released. The repository tag is 0.26.4 and can be found on GitHub at: https://github.com/ripple/rippled/commits/0.26.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 05a04aa80192452475888479c84ff4b9b54e6ae7
Author: Vinnie Falco <[email protected]>
Date: Mon Nov 3 16:53:37 2014 -0800
Set version to 0.26.4
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.55.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 JSON-RPC Update
With rippled version 0.26.4, the rippled.cfg file must set the ssl_verify property to 0. Without this update, JSON-RPC API calls may not work.
New Features
- Rocksdb v. 3.5.1
- SQLite v. 3.8.7
- Disable SSLv3
- Add counters to track ledger read and write activities
- Use trusted validators median fee when determining transaction fee
- Add --quorum argument for server start (RIPD-563)
- Add account_offers paging (RIPD-344)
- Add account_lines paging (RIPD-343)
- Ability to configure network fee in rippled.cfg file (RIPD-564)
Bug Fixes
- Fix OS X version parsing/error related to OS X 10.10 update
- Fix incorrect address in connectivity check report
- Fix page sizes for ledger_data (RIPD-249)
- Make log partitions case-insensitive in rippled.cfg
Improvements
- Performance
- Ledger performance improvements for storage and traversal (RIPD-434)
- Improve client performance for JSON responses (RIPD-439)
- Other
- Remove PROXY handshake feature
- Change to rippled.cfg to support sections containing both key/value pairs and a list of values
- Return descriptive error message for memo validation (RIPD-591)
- Changes to enforce JSON-RPC 2.0 error format
- Optimize account_lines and account_offers (RIPD-587)
- Improve fee setting logic (RIPD-614)
- Improve transaction security
- Config improvements
- Improve path filtering (RIPD-561)
- Logging to distinguish Byzantine failure from tx bug (RIPD-523)
Experimental
- Add "deferred" flag to transaction relay message (required for future code that will relay deferred transactions)
- Refactor STParsedJSON to parse an object or array (required for multisign implementation) (RIPD-480)
Development-Related Updates
- Changes to DatabaseReader to read ledger numbers from database
- Improvements to SConstruct
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.26.3-sp1
rippled 0.26.3-sp1 has been released. The repository tag is 0.26.3-sp1 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.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 2ad6f0a65e248b4f614d38d199a9d5d02f5aaed8
Author: Vinnie Falco <[email protected]>
Date: Fri Sep 12 15:22:54 2014 -0700
Set version to 0.26.3-sp1
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.55.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
- New command to display HTTP/S-RPC sessions metrics (RIPD-533)
Bug Fixes
- Improved handling of HTTP/S-RPC sessions (RIPD-489)
- Fix unit tests for Windows.
- Fix integer overflows in JSON parser.
Improvements
- Improve processing of trust lines during pathfinding.
Experimental Features
- Added a command line utility called LedgerTool for retrieving and processing ledger blocks from the Ripple network.
Development-Related Updates
- HTTP message and parser improvements.
- Streambuf wrapper supports rvalue move.
- Message class holds a complete HTTP message.
- Body class holds the HTTP content body.
- Headers class holds RFC-compliant HTTP headers.
- Basic_parser provides class interface to joyent's http-parser.
- Parser class parses into a message object.
- Remove unused http get client free function.
- Unit test for parsing malformed messages.
- Add enable_if_lvalue.
- Updates to includes and scons.
- Additional ledger.history.mismatch insight statistic.
- Convert rvalue to an lvalue. (RIPD-494)
- Enable heap profiling with jemalloc.
- Add aged containers to Validators module. (RIPD-349)
- Account for high-ASCII characters. (RIPD-464)
More information
For more information or assistance, the following resources will be of use:
rippled Version 0.26.2
rippled 0.26.2 has been released. The repository tag is 0.26.2 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.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 b9454e0f0ca8dbc23844a0520d49394e10d445b1
Author: Vinnie Falco <[email protected]>
Date: Mon Aug 11 15:25:44 2014 -0400
Set version to 0.26.2
This release incorporates a small number of important bugfixes. 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.55.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
- Freeze enforcement: activates on September 15, 2014 (RIPD-399)
- Add pubkey_node and hostid to server stream messages (RIPD-407)
Bug Fixes
- Fix intermittent exception when closing HTTPS connections (RIPD-475)
- Correct Pathfinder::getPaths out to handle order books (RIPD-427)
- Detect inconsistency in PeerFinder self-connects (RIPD-411)
Experimental Features
- Add owner_funds to client subscription data (RIPD-377)
The offer funding status feature is “experimental” in this version. Developers are able to see the field, but it is subject to change in future releases.
More information
For more information or assistance, the following resources will be of use: