To provide additional predictability to the XRP supply, Ripple has locked 55 billion XRP (55% of the total possible supply) into a series of escrows. These escrows are on the ledger itself and the ledger mechanics, enforced by consensus, control the release of the XRP.
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.
Ripple has released rippled version 0.80.0, which introduces several enhancements that improve the reliability, scalability and security of the XRP Ledger. Ripple recommends that all rippled server operators upgrade to version 0.80.0 by Tuesday, 2017-11-07, for service continuity.
As Ripple progresses towards further decentralizing the XRP Ledger, we want to make server operators and members of the XRP Ledger community aware of a few upcoming changes to help ensure the reliability and stability of the network as it transitions to a distributed architecture with fully decentralized validators.
Blockchain technology is set to fundamentally transform the way the world moves value, but to do so, it must first meet a number of challenges.
The rippled team has released rippled version 0.70.2, which corrects an emergent behavior that resulted in high transaction costs and fewer transactions in validated ledgers over the past few days. The problematic behavior involved large numbers of transactions being stuck in different rippled instances' open ledgers without being consistently relayed to validators. The large number of "stuck" transactions filled the transaction queue and caused a dramatic increase in the open ledger cost.
By Nik Bougalis, Engineering Manager
UPDATE 7-12-2017: This announcement now contains corrected SHA-256 values for the RPM and source RPM.
The rippled team has released rippled version 0.70.1, which corrects a technical flaw in the newly refactored consensus code that could, in rare cases, cause a node to get stuck in consensus due to stale votes from a peer. Ripple requires upgrading to rippled version 0.70.1 immediately.
Ripple has released rippled version 0.70.0, which introduces several enhancements that improve the reliability, scalability and security of the Ripple Consensus Ledger. Ripple recommends that all rippled server operators upgrade to version 0.70.0 by Thursday, 2017-06-29, for service continuity.
The rippled team has released rippled version 0.60.3, which helps to increase the stability of the overlay network under increased load. Ripple recommends server operators upgrade to rippled version 0.60.3 immediately. There are no new features in the 0.60.3 release.
Ripple has released a new rippled 0.60.2-2 RPM that contains an update to the validator-keys key generation and management tool. The latest version of validator-keys allows validator operators to sign data with their validator key.
The rippled team has released rippled version 0.60.2, which further strengthens handling of cases associated with a previously patched exploit, in which NoRipple flags were being bypassed by using offers. Ripple requires upgrading to rippled version 0.60.2 immediately. There are no new features in the 0.60.2 release. Note: This does not affect XRP transactions.
The rippled team has released rippled version 0.60.1, which corrects a technical flaw that resulted from using 32-bit space identifiers instead of the protocol-defined 16-bit values for Escrow and Payment Channel ledger entries. rippled version 0.60.1 also fixes a problem where the websocket timeout timer would not be cancelled when certain errors occurred during subscription streams. Ripple strongly recommends upgrading to rippled version 0.60.1 immediately.
A majority of rippled validators voted to enable the Escrow, PayChan, and fix1368 Amendments, which are scheduled to become enabled on the network on Thursday, 2017-03-30.
Ripple has released rippled version 0.60.0, which introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL), including Interledger Protocol compatibility for ledger interoperability. Ripple recommends that all server operators upgrade to version 0.60.0 by Thursday, 2017-03-30, for service continuity.
When you build an automated system to send payments into the Ripple Consensus Ledger (RCL) for your customers, you must make sure that it constructs payments carefully. Malicious actors are constantly trying to find flaws in a system implementation that pays them more money than it should.
The rippled team has released version 0.50.3, which patches a reported exploit that would allow a combination of trust lines and order books in a payment path to bypass the blocking effect of the NoRipple flag. Ripple recommends that all rippled server operators immediately upgrade to version 0.50.3, which contains a patch that fixes the exploit. There are no new or updated features in the 0.50.3 release.
2016 was an important year for Ripple. Banks were added to our growing network, we completed a successful Series B investment round and formed the Global Payments Steering Group. Underlying all those milestones was the Ripple Consensus Ledger (RCL), which runs 24 hours a day, 7 days a week and recently celebrated its 4th birthday on February 17, 2017. In 2016 alone, RCL closed over 8 million ledgers, processing more than 225 million transactions and handling more than $1 Billion dollars in payment volume throughout the year.
As predicted previously, the TickSize amendment became available on the Ripple Consensus Ledger yesterday afternoon (PST) in ledger 27841793 (2017-02-21T23:02:52Z).
This notice is for all validator operators, and may be useful for gateways that intend to use tick sizes.
This notice is for all validator operators, and may be useful for gateways that intend to use tick sizes.
Previously introduced in rippled version 0.50.0, the TickSize amendment to the Ripple Consensus Ledger is now open for voting. The amendment changes the way offers are ranked in the RCL's order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.
The rippled team has released 0.50.2, which adjusts the default TLS cipher list and corrects a flaw that would not allow an SSL handshake to properly complete if the port was configured using the wss keyword. Ripple recommends upgrading to 0.50.2 only if server operators are running rippled servers that accept client connections over TLS. There are no new or updated features in the 0.50.2 release.
Ripple has released rippled version 0.50.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.50.0 by Tuesday, 2017-02-21, for service continuity.
The Ripple Data team will be running load balancing tests on Ripple Data API starting Wednesday, 2017-01-18, at 2pm PST, which will last approximately 15 minutes. The Ripple Data API is an open and free resource that provides access to information about changes in the Ripple Consensus Ledger, including transaction history and processed analytical data.
As a leader in open-source, distributed financial technology, Ripple recognizes the importance of security researchers and we always encourage responsible disclosure of potential security vulnerabilities via our bug bounty program. Ripple also employs regular external security audits and, as a matter of practice, the maintainers of the Ripple Consensus Ledger (RCL) technology (rippled) routinely use static and dynamic analysis tools on the C++ codebase (most recently version 0.50.0-b1).
The rippled team has released version 0.40.1, which increases SQLite database limits in all rippled full-history servers. Ripple recommends upgrading to 0.40.1 only if server operators are running rippled servers with full-history of the ledger. There are no new or updated features in the 0.40.1 release.