Published by mDuo13 over 8 years ago
The rippled
0.31.2 release contains important bug fixes for stability. We advise rippled
operators to upgrade immediately.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
New and Updated Features
This release has no new features.
Bug Fixes
LedgerSequence
field. Previous versions of rippled
incorrectly assumed that the optional validation field would always be included. Current versions of the software always include the field, and gracefully handle its absence. (From unreleased version 0.31.1)Published by mDuo13 over 8 years ago
rippled version 0.12 has now been released. This release is currently the tip of the master branch and can be found on GitHub. The tag is v0.12.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 d0a9da6f16f4083993e4b6c5728777ffebf80f3a
Author: JoelKatz <[email protected]>
Date: Mon Aug 26 12:08:05 2013 -0700
Set version to v0.12.0
Major Partner Issues Fixed
This issue was caused by LevelDB periodically compacting its internal data structure. While compacting, rippled's processing would stall causing the node to lose sync with the rest of the network. This issue was solved by switching from LevelDB to HyperLevelDB. rippled operators will need to change their ripple.cfg file. See below for configuration details.
On rare occasions, a transaction would show as locally validated before the full network consensus was confirmed. This issue was resolved by changing the way transactions are saved.
Occasionally, some rippled servers would fail to fetch all ledgers. This left gaps in the local history and caused some API calls to report incomplete results. The ledger fetch code was rewritten to both prevent this and to repair any existing gaps.
Significant Changes
doTransactionEntry
now works against open ledgers.doLedgerEntry
now supports a binary option.getBookPage
that caused it to skip offers is fixed.getNodeFat
now returns deeper chains, reducing ledger acquire latency.Validators
Ripple Labs is now running five validators. You can use this template for your validators.txt
file:
[validators]
n9KPnVLn7ewVzHvn218DcEYsnWLzKerTDwhpofhk4Ym1RUq4TeGw RIP1
n9LFzWuhKNvXStHAuemfRKFVECLApowncMAM5chSCL9R5ECHGN4V RIP2
n94rSdgTyBNGvYg8pZXGuNt59Y5bGAZGxbxyvjDaqD9ceRAgD85P RIP3
n9LeQeDcLDMZKjx1TZtrXoLBLo5q1bR1sUQrWG7tEADFU6R27UBp RIP4
n9KF6RpvktjNs2MDBkmxpJbup4BKrKeMKDXPhaXkq7cKTwLmWkFr RIP5
Update April 2014 - Due to a vulnerability in OpenSSL the validator keys above have been cycled out, the five validators by RippleLabs use the following keys now:
[validators]
n949f75evCHwgyP4fPVgaHqNHxUVN15PsJEZ3B3HnXPcPjcZAoy7 RL1
n9MD5h24qrQqiyBC8aeqqCWvpiBiYQ3jxSr91uiDvmrkyHRdYLUj RL2
n9L81uNCaPgtUJfaHh89gmdvXKAmSt5Gdsw2g1iPWaPkAHW5Nm4C RL3
n9KiYM9CgngLvtRCQHZwgC2gjpdaZcCcbt3VboxiNFcKuwFVujzS RL4
n9LdgEtkmGB9E2h3K4Vp7iGUaKuq23Zr32ehxiU8FWY7xoxbWTSA RL5
You should also raise your quorum to at least three by putting the following in your rippled.cfg
file:
[validation_quorum]
3
If you are a validator, you should set your quorum to at least four.
IPs
A list of Ripple Labs server IP addresses can be found by resolving r.ripple.com
. You can also add this to your rippled.cfg
file to ensure you always have several peer connections to Ripple Labs servers:
[ips]
54.225.112.220 51235
54.225.123.13 51235
54.227.239.106 51235
107.21.251.218 51235
184.73.226.101 51235
23.23.201.55 51235
Node DB
You need to configure the NodeBackEnd that you want the server to use. In most cases, that will mean adding this to your configuration file:
[node_db]
type=HyperLevelDB
path=db/hashnode
Release Candidates
RC1 was the first release candidate.
RC2 fixed a bug that could cause ledger acquires to stall.
RC3 fixed compilation under OSX.
RC4 includes performance improvements in countAccountTx and numerous small fixes to ledger acquisition.
RC5 changed the peer low water mark from 4 to 10 to acquire more server connections.
RC6 fixed some possible load issues with the network state timer and cluster reporting timers.
Issues
Fetching of historical ledgers is slower in this build than in previous builds. This is being investigated.
Published by mDuo13 over 8 years ago
rippled version 0.14 has now been released. This release is currently the tip of the master branch and the tag is v0.12.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 b6d11c08d0245ee9bafbb97143f5d685dd2979fc
Author: vinniefalco
Date: Wed Oct 2 2013
Set version to 0.14.0
Significant Changes
Validators
Ripple Labs is now running five validators. You can use this template for your validators.txt
file:
[validators]
n9KPnVLn7ewVzHvn218DcEYsnWLzKerTDwhpofhk4Ym1RUq4TeGw RIP1
n9LFzWuhKNvXStHAuemfRKFVECLApowncMAM5chSCL9R5ECHGN4V RIP2
n94rSdgTyBNGvYg8pZXGuNt59Y5bGAZGxbxyvjDaqD9ceRAgD85P RIP3
n9LeQeDcLDMZKjx1TZtrXoLBLo5q1bR1sUQrWG7tEADFU6R27UBp RIP4
n9KF6RpvktjNs2MDBkmxpJbup4BKrKeMKDXPhaXkq7cKTwLmWkFr RIP5
You should also raise your quorum to at least three by putting the following in your rippled.cfg
file:
[validation_quorum]
3
If you are a validator, you should set your quorum to at least four.
IPs
A list of Ripple Labs server IP addresses can be found by resolving r.ripple.com
. You can also add this to your rippled.cfg
file to ensure you always have several peer connections to Ripple Labs servers:
[ips]
54.225.112.220 51235
54.225.123.13 51235
54.227.239.106 51235
107.21.251.218 51235
184.73.226.101 51235
23.23.201.55 51235
Node DB
You need to configure the NodeBackEnd that you want the server to use. In most cases, that will mean adding this to your configuration file:
[node_db]
type=HyperLevelDB
path=db/hashnode
Release Candidates
Issues
None known
Published by mDuo13 over 8 years ago
rippled version 0.16 has now been released. This release is currently the tip of the master branch and the tag is v0.16.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 15ef43505473225af21bb7b575fb0b628d5e7f73
Author: vinniefalco
Date: Wed Oct 2 2013
Set version to 0.16.0
Significant Changes
Validators
Ripple Labs is now running five validators. You can use this template for your validators.txt
file:
[validators]
n9KPnVLn7ewVzHvn218DcEYsnWLzKerTDwhpofhk4Ym1RUq4TeGw RIP1
n9LFzWuhKNvXStHAuemfRKFVECLApowncMAM5chSCL9R5ECHGN4V RIP2
n94rSdgTyBNGvYg8pZXGuNt59Y5bGAZGxbxyvjDaqD9ceRAgD85P RIP3
n9LeQeDcLDMZKjx1TZtrXoLBLo5q1bR1sUQrWG7tEADFU6R27UBp RIP4
n9KF6RpvktjNs2MDBkmxpJbup4BKrKeMKDXPhaXkq7cKTwLmWkFr RIP5
You should also raise your quorum to at least three by putting the following in your rippled.cfg
file:
[validation_quorum]
3
If you are a validator, you should set your quorum to at least four.
IPs
A list of Ripple Labs server IP addresses can be found by resolving r.ripple.com
. You can also add this to your rippled.cfg
file to ensure you always have several peer connections to Ripple Labs servers:
[ips]
54.225.112.220 51235
54.225.123.13 51235
54.227.239.106 51235
107.21.251.218 51235
184.73.226.101 51235
23.23.201.55 51235
Node DB
You need to configure the NodeBackEnd that you want the server to use. In most cases, that will mean adding this to your configuration file:
[node_db]
type=HyperLevelDB
path=db/hashnode
Release Candidates
Issues
None known
Published by mDuo13 over 8 years ago
rippled version 0.19 has now been released. This release is currently the tip of the release branch and the tag is 0.19.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 26783607157a8b96e6e754f71565f4eb0134efc1
Author: Vinnie Falco <[email protected]>
Date: Fri Nov 22 23:36:50 2013 -0800
Set version to 0.19.0
Significant Changes
Validators
Ripple Labs is now running five validators. You can use this template for your validators.txt
file (or place this in your config file):
[validators]
n9KPnVLn7ewVzHvn218DcEYsnWLzKerTDwhpofhk4Ym1RUq4TeGw RIP1
n9LFzWuhKNvXStHAuemfRKFVECLApowncMAM5chSCL9R5ECHGN4V RIP2
n94rSdgTyBNGvYg8pZXGuNt59Y5bGAZGxbxyvjDaqD9ceRAgD85P RIP3
n9LeQeDcLDMZKjx1TZtrXoLBLo5q1bR1sUQrWG7tEADFU6R27UBp RIP4
n9KF6RpvktjNs2MDBkmxpJbup4BKrKeMKDXPhaXkq7cKTwLmWkFr RIP5
You should also raise your quorum to at least three by putting the following in your rippled.cfg
file:
[validation_quorum]
3
If you are a validator, you should set your quorum to at least four.
IPs
A list of Ripple Labs server IP addresses can be found by resolving r.ripple.com
. You can also add this to your rippled.cfg
file to ensure you always have several peer connections to Ripple Labs servers:
[ips]
54.225.112.220 51235
54.225.123.13 51235
54.227.239.106 51235
107.21.251.218 51235
184.73.226.101 51235
23.23.201.55 51235
New RocksDB back end
RocksDB is based on LevelDB with improvements from Facebook and the community. Preliminary tests show that it stall less often than HyperLevelDB.
If you are switching over from an existing back end, you have two choices. You can remove your old database or you can import it.
To remove your old database, make sure the server is shutdown. Remove the db/ledger.db
and db/transaction.db
files. Remove all the files in your back end store directory, db/hashnode
by default. Then you can change your configuration file to use the RocksDB back end and restart.
To import your old database, start by shutting the server down. Then modify the configuration file by renaming your [node_db]
portion to [import_db]
. Create a new [node_db]
section specify a RocksDB back end and a different directory. Start the server with rippled --import
. When the import finishes, stop the server (it can take several minutes to shut down after an import), remove the old database, put the new database into place, remove the [import_db]
section, change the [node_db]
section to refer to the final location, and restart the server.
The recommended RocksDB configuration is:
[node_db]
type=RocksDB
path=db/hashnode
open_files=1200
filter_bits=12
cache_mb=256
file_size_mb=8
file_size_mult=2
Configuring your Node DB
You need to configure the NodeBackEnd that you want the server to use. See above for an example RocksDB configuration.
Published by mDuo13 over 8 years ago
rippled version 0.20.1 has been released. This release is currently the tip of the develop branch and the tag is 0.20.1.
This is a critical release. 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:
commit 95a573b755219d7e1e078d53b8e11a8f0d7cade1
Author: Vinnie Falco <[email protected]>
Date: Wed Jan 8 17:08:27 2014 -0800
Set version to 0.20.1
Major Partner Issues Fixed
Toolchain support
Starting with this release, the minimum supported version of GCC used to compile rippled is v4.8.
Significant Changes
Notice
If you are upgrading from version 0.12 or earlier of rippled, these next sections apply to you because the format of the rippled.cfg file changed around that time. If you have upgraded since that time and you have applied the configuration file fixes, you can safely ignore them.
Ripple Labs is now running five validators. You can use this template for your validators.txt file (or place this in your config file):
[validators]
n9KPnVLn7ewVzHvn218DcEYsnWLzKerTDwhpofhk4Ym1RUq4TeGw RIP1
n9LFzWuhKNvXStHAuemfRKFVECLApowncMAM5chSCL9R5ECHGN4V RIP2
n94rSdgTyBNGvYg8pZXGuNt59Y5bGAZGxbxyvjDaqD9ceRAgD85P RIP3
n9LeQeDcLDMZKjx1TZtrXoLBLo5q1bR1sUQrWG7tEADFU6R27UBp RIP4
n9KF6RpvktjNs2MDBkmxpJbup4BKrKeMKDXPhaXkq7cKTwLmWkFr RIP5
You should also raise your quorum to at least three by putting the following in your rippled.cfg file:
[validation_quorum]
3
If you are a validator, you should set your quorum to at least four.
A list of Ripple Labs server IP addresses can be found by resolving r.ripple.com. You can also add this to your rippled.cfg file to ensure you always have several peer connections to Ripple Labs servers:
[ips]
54.225.112.220 51235
54.225.123.13 51235
54.227.239.106 51235
107.21.251.218 51235
184.73.226.101 51235
23.23.201.55 51235
RocksDB is based on LevelDB with improvements from Facebook and the community. Preliminary tests show that it stalls less often than HyperLevelDB for our use cases.
If you are switching over from an existing back end, you have two options. You can remove your old database and let rippled recreate it as it re-syncs, or you can import your old database into the new one.
To remove your old database, make sure the server is shut down (rippled stop
). Remove the db/ledger.db and db/transaction.db files. Remove all the files in your back end store directory (db/hashnode by default). Then change your configuration file to use the RocksDB back end and restart.
To import your old database, start by shutting the server down. Then modify the configuration file by renaming your [node_db] stanza to [import_db]. Create a new [node_db] stanza and specify a RocksDB back end with a different directory. Start the server with the command rippled --import. When the import finishes gracefully stop the server (rippled stop
). Please wait for rippled to stop on its own because it can take several minutes for it to shut down after an import. Remove the old database, put the new database into place, remove the [import_db] section, change the [node_db] section to refer to the final location, and restart the server.
The recommended RocksDB configuration is:
[node_db]
type=RocksDB
path=db/hashnode
open_files=1200
filter_bits=12
cache_mb=256
file_size_mb=8
file_size_mult=2
You need to configure the NodeBackEnd that you want the server to use. See above for an example RocksDB configuration.
Published by mDuo13 over 8 years ago
rippled version 0.21.0 has been released. This release is currently the tip of the develop/ branch and can be found on GitHub at 1. The tag is 0.21.0-rc2 and can be found on GitHub at 2.
This is a critical release. 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:
commit f295bb20a16d1d2999f606c1297c8930d8e33c40
Author: JoelKatz <[email protected]>
Date: Fri Jan 24 11:17:16 2014 -0800
Set version to 0.21.0.rc2
Major Partner Issues Fixed
Toolchain support
As with the previous release, the minimum supported version of GCC used to compile rippled is v4.8.
Significant Changes
Release Candidates
RC1 fixed performance problems with order book retrieval.
RC2 fixed a bug that caused crashes in order processing and a bug in parsing order book requests.
Notice
If you are upgrading from version 0.12 or earlier of rippled, these next sections apply to you because the format of the rippled.cfg file changed around that time. If you have upgraded since that time and you have applied the configuration file fixes, you can safely ignore them.
Ripple Labs is now running five validators. You can use this template for your validators.txt file (or place this in your config file):
[validators]
n9KPnVLn7ewVzHvn218DcEYsnWLzKerTDwhpofhk4Ym1RUq4TeGw RIP1
n9LFzWuhKNvXStHAuemfRKFVECLApowncMAM5chSCL9R5ECHGN4V RIP2
n94rSdgTyBNGvYg8pZXGuNt59Y5bGAZGxbxyvjDaqD9ceRAgD85P RIP3
n9LeQeDcLDMZKjx1TZtrXoLBLo5q1bR1sUQrWG7tEADFU6R27UBp RIP4
n9KF6RpvktjNs2MDBkmxpJbup4BKrKeMKDXPhaXkq7cKTwLmWkFr RIP5
You should also raise your quorum to at least three by putting the following in your rippled.cfg file:
[validation_quorum]
3
If you are a validator, you should set your quorum to at least four.
A list of Ripple Labs server IP addresses can be found by resolving r.ripple.com. You can also add this to your rippled.cfg file to ensure you always have several peer connections to Ripple Labs servers:
[ips]
184.73.226.101 51235
23.23.201.55 51235
54.200.43.173 51235
184.73.57.84 51235
54.234.249.55 51235
54.200.86.110 51235
RocksDB is based on LevelDB with improvements from Facebook and the community. Preliminary tests show that it stalls less often than HyperLevelDB for our use cases.
If you are switching over from an existing back end, you have two options. You can remove your old database and let rippled recreate it as it re-syncs, or you can import your old database into the new one.
To remove your old database, make sure the server is shut down (rippled stop
). Remove the db/ledger.db and db/transaction.db files. Remove all the files in your back end store directory (db/hashnode by default). Then change your configuration file to use the RocksDB back end and restart.
To import your old database, start by shutting the server down. Then modify the configuration file by renaming your [node_db] stanza to [import_db]. Create a new [node_db] stanza and specify a RocksDB back end with a different directory. Start the server with the command rippled --import. When the import finishes gracefully stop the server (rippled stop
). Please wait for rippled to stop on its own because it can take several minutes for it to shut down after an import. Remove the old database, put the new database into place, remove the [import_db] section, change the [node_db] section to refer to the final location, and restart the server.
The recommended RocksDB configuration is:
[node_db]
type=RocksDB
path=db/hashnode
open_files=1200
filter_bits=12
cache_mb=128
file_size_mb=8
file_size_mult=2
You need to configure the NodeBackEnd that you want the server to use. See above for an example RocksDB configuration.
Published by mDuo13 over 8 years ago
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
Major Partner Issues Fixed
Significant Changes
Published by mDuo13 over 8 years ago
rippled version 0.23.0 has been released. The repository tag is 0.23.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.23.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 29a4f61551236f70865d46d6653da2e62de1c701
Author: Vinnie Falco <[email protected]>
Date: Fri Mar 14 13:01:23 2014 -0700
Set version to 0.23.0
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 Boost 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.
Improvements
Bug Fixes
Published by mDuo13 over 8 years ago
rippled version 0.24.0 has been released. The repository tag is 0.24.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.24.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 3eb1c7bd6f93e5d874192197f76571184338f702
Author: Vinnie Falco <[email protected]>
Date: Mon May 5 10:20:46 2014 -0700
Set version to 0.24.0
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 Boost 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.
Improvements
Bug Fixes
Published by mDuo13 over 8 years ago
rippled version 0.25.0 has been released. The repository tag is 0.25.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.25.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 29d1d5f06261a93c5e94b4011c7675ff42443b7f
Author: Vinnie Falco <[email protected]>
Date: Wed May 14 09:01:44 2014 -0700
Set version to 0.25.0
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 Boost 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.
Major Features
rippled-example.cfg
Improvements
Bug Fixes
Published by mDuo13 over 8 years ago
rippled
v0.25.1 has been released. The repository tag is 0.25.1
and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.25.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 b677cacb8ce0d4ef21f8c60112af1db51dce5bb4
Author: Vinnie Falco <[email protected]>
Date: Thu May 15 08:27:20 2014 -0700
Set version to 0.25.1
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 Boost 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.
Major Features
rippled-example.cfg
Improvements
Bug Fixes
Published by mDuo13 over 8 years ago
rippled v0.25.2 has been released. The repository tag is 0.25.2 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.25.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 ddf68d464d74e1c76a0cfd100a08bc8e65b91fec
Author: Mark Travis <[email protected]>
Date: Mon Jul 7 11:46:15 2014 -0700
Set version to 0.25.2
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.
While it may be possible to compile rippled on (virtual) machines with 4GB of RAM, we recommend build machines with 8GB of RAM.
The minimum supported version of Boost 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.
Improvements
Bug Fixes
Published by mDuo13 over 8 years ago
rippled v0.26.0 has been released. The repository tag is 0.26.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.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 9fa5e3987260e39dba322f218d39ac228a5b361b
Author: Vinnie Falco <[email protected]>
Date: Tue Jul 22 09:59:45 2014 -0700
Set version to 0.26.0
This release incorporates a significant number of improvements and 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.
Improvements
Bug Fixes
More information
For more information or assistance, the following resources will be of use:
Published by mDuo13 over 8 years ago
rippled v0.26.1 has been released. The repository tag is 0.26.1 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.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 9a0e806f78300374e20070e2573755fbafdbfd03
Author: Vinnie Falco <[email protected]>
Date: Mon Jul 28 11:27:31 2014 -0700
Set version to 0.26.1
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.
Bug Fixes
More information
For more information or assistance, the following resources will be of use:
Published by mDuo13 over 8 years ago
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
Bug Fixes
Experimental Features
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:
Published by mDuo13 over 8 years ago
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
Bug Fixes
Improvements
Experimental Features
Development-Related Updates
More information
For more information or assistance, the following resources will be of use:
Published by mDuo13 over 8 years ago
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
Bug Fixes
Improvements
Experimental
Development-Related Updates
More information
For more information or assistance, the following resources will be of use:
Published by mDuo13 over 8 years ago
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
Bug Fixes
Improvements
Development-Related Updates
Experimental
Migration Instructions
With rippled version 0.27.0, the rippled.cfg file must be changed according to these instructions:
[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>
[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
[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[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`
[websocket_public_port],
[websocket_public_ip],
[websocket_ssl_key],
[websocket_ssl_cert],
[websocket_ssl_chain]
settings from rippled.cfg[ssl_verify]
section by setting it to 0Integration Notes
With this release, integrators should deprecate the "DeliveredAmount" field in favor of "delivered_amount."
For Transactions That Occurred Before January 20, 2014:
For Transactions That Occur After January 20, 2014:
Assistance
For assistance, please contact [email protected]
More information
For more information or assistance, the following resources will be of use:
Published by mDuo13 over 8 years ago
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
Bug Fixes
Improvements
Experimental
Assistance
For assistance, please contact [email protected]
More information
For more information or assistance, the following resources will be of use: