If you want more content like this, please visit Ripple.com.
Ripple has released
rippled version 0.80.2, which improves the transaction dispatch logic of
rippled, allows for more transactions to be in flight at any one time and reduces the overall resource usage of
rippled. The improved transaction dispatch logic ensures that a transaction is dispatched at most once every 10 seconds, even if it received from multiple peers during that interval.
The fix should also improve load accounting on peer links, reducing the number of extraneous server-server connection drops caused by redundant transaction dispatching.
Ripple strongly recommends upgrading to
rippled version 0.80.2 immediately.
If you operate a
rippled server, then you should upgrade to 0.80.2 immediately.
Impact of Not Upgrading
- If you operate a
rippledserver, but do not upgrade to rippled version 0.80.2, then your
rippledserver will use more resources than necessary and may periodically drop transactions and fall out of sync with the network.
For instructions on updating
rippled on supported platforms, see Updating
rippled on supported platforms.
The SHA-256 for the RPM is:
The SHA-256 for the source RPM is:
For other platforms, please compile version 0.80.2 from source.
The first log entry should be the change setting the version:
commit d2fc4e3569d79d3cade78533f673f642a8d26845 Author: Nikolaos D. Bougalis <firstname.lastname@example.org> Date: Thu Dec 14 15:30:20 2017 -0800 Set version to 0.80.2
The Ripple technical operations team will deploy
rippled version 0.80.2 to all production
rippled servers under its operational control, on Friday, 12/15/2017.
Learn, ask questions, and discuss
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
0.80.2 Change Log
0.80.1 Change Log
rippled version 0.80.1 also included the following fixes and improvements:
New and Updated Features
- Allow including validator manifests in published list (#2278)
- Add validator list RPC commands (#2242)
- Support SNI when querying published list sites and use Windows system root certificates (#2275)
- Grow TxQ expected size quickly, shrink slowly (#2235)
- Make consensus quorum unreachable if validator list expires (#2240)
- Properly use ledger hash to break ties when determing working ledger for consensus (#2257)
- Explictly use std::deque for missing node handler in SHAMap code (#2252)
- Verify validator token manifest matches private key (#2268)
Please visit Ripple.com for more information.