Ripple has released rippled version 0.40.0, which introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL). Ripple recommends that all server operators upgrade to version 0.40.0 by Tuesday, 2017-01-17, for service continuity.
The Flow Amendment became available on the Ripple Consensus Ledger in ledger 24,970,753 (2016-10-21T19:47:22Z).
A majority of rippled validators voted to enable the Flow Amendment, which is scheduled to become active on the protocol on Thursday, 2016-10-20. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling.
Originally introduced in rippled version 0.32.1, but later vetoed after a flaw was discovered in the code while testing, the new Flow Amendment is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling.
Ripple has released rippled version 0.33.0-hf1, which fixes a JSON parsing issue in all rippled servers. Ripple recommends upgrading to 0.33.0-hf1 only if server operators are experiencing a jsonInvalid error response to client requests. There are no new or updated features in the 0.33.0-hf1 release.
Ripple has released rippled version 0.33.0, which introduces several new enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL). Ripple recommends that all server operators upgrade to version 0.33.0 by Wednesday, 2016-10-20, for service continuity.
On 2016-09-02, Ripple will be resetting the test network ledger and balances. This means that all test net order books will be deleted and all account balances will be depleted.
Originally, the FlowV2 amendment was planned to replace rippled’s payment processing engine with a more robust and efficient implementation. It was previously expected to become active on Wednesday, 2016-08-24.
The FlowV2 Amendment is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the FlowV2 engine. The new version of the payment processing engine is intended to follow the same rules as the old engine. However, the new engine occasionally produces different results due to floating point rounding.
Ripple is proud to announce the release of rippled version 0.32.1, which introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger. Ripple recommends that all server operators upgrade to version 0.32.1 by Wednesday, 2016-08-24, for the best performance.
As predicted previously, TrustSetAuth became available on the Ripple Consensus Ledger this afternoon (PDT) in ledger 22,721,281 (2016-07-19T15:10).
TrustSetAuth Will Soon Be Available
This notice is for all validator operators, and may be relevant to gateways that utilize the Authorized Account feature.
As predicted previously, multi-signing became available on the Ripple Consensus Ledger this afternoon in Pacific time (2016-06-27T11:34:41Z, to be exact).
Ripple is proud to announce the release of rippled version 0.32.0. This release introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger. Ripple recommends that all server operators upgrade to the new version.
The multi-signing amendment is currently supported by the majority of voting validators on Ripple, and is scheduled to become active on the protocol on Monday, 2016-06-27. For more information, please see the multi-signing documentation in the Ripple Developer Portal:
The Data team is proud to announce the release of the Ripple Data API v2.2! This release includes lots of new features, including a total of 15 new methods, improvements in data quality, and documentation.
Ripple is proud to announce an improved, unified interface to the Ripple Consensus Ledger: the new RippleAPI! RippleAPI merges ripple-lib and Ripple-REST into a single high-level interface for JavaScript that is fully-documented, fully-tested, schema-validated, stateless, and easier to use.
The rippled team is proud to announce a bundle of related news items:
The latest version of rippled, the core server of the Ripple Consensus Ledger, is here! Version 0.30.1 contains lots of small features and improvements, including updates to account_offers, server_info, peer subscriptions, and more. It also adds several optimizations to the consensus process that have already led to a dramatic increase in the number of ledgers validated per day! Learn more: