Load Testing Data API

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. … Continued

Response to China CERT Report

Ripple recognizes the importance of security researchers, and we take any reports of security vulnerabilities very seriously.

rippled 0.40.1

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. Action Recommended If you operate a rippled server and … Continued

rippled version 0.40.0 Released

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. Highlights of this release include: Suspended Payments, a new transaction type on the Ripple network that functions … Continued

The Flow Amendment is Now Available

The Flow Amendment became available on the Ripple Consensus Ledger in ledger 24,970,753 (2016-10-21T19:47:22Z). 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. Action Required If you operate a rippled … Continued

The Flow Amendment Will Be Available Soon

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 … Continued

The Flow Amendment is Open for Voting

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 … Continued

rippled version 0.33.0-hf1

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. Action Recommended If you operate a rippled server and are … Continued

rippled version 0.33.0 Released

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. Highlights of this release include: An improved version of the payment code, which Ripple expects to … Continued

Ripple Test Network Ledger Will Be Reset

Summary 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. This will have absolutely no effect on the live, production Ripple Consensus Ledger (RCL). Action Required If you have projects built or scripts running … Continued

The FlowV2 Amendment Was Vetoed

Background 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. FlowV2 Was Vetoed The rippled team found a flaw in FlowV2 while testing. As a result, the Ripple network has vetoed the new payment engine … Continued

The FlowV2 Amendment Is Open For Voting

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 … Continued

rippled version 0.32.1 Released

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. Highlights of this release include: A new, optional WebSocket implementation based on … Continued

TrustSetAuth is Now Available

As predicted previously, TrustSetAuth became available on the Ripple Consensus Ledger this afternoon (PDT) in ledger 22,721,281 (2016-07-19T15:10). This amendment allows pre-authorization of accounting relationships (zero-balance trust lines) when using Authorized Accounts. Action Required To remain operational, all rippled instances running on a version earlier than 0.31.0 must be upgraded to rippled server version 0.32.0 … Continued

TrustSetAuth Will Soon Be Available

This notice is for all validator operators, and may be useful for gateways that utilize the Authorized Accounts feature. A majority of trusted validators voted to enable the TrustSetAuth amendment, which is scheduled to become active on the protocol on Tuesday, 2016-07-19. This amendment allows pre-authorization of accounting relationships (zero-balance trust lines) when using Authorized … Continued

The TrustSetAuth Amendment Is Open For Voting

This notice is for all validator operators, and may be relevant to gateways that utilize the Authorized Account feature. The new TrustSetAuth amendment is open for voting now. This amendment allows pre-authorization of accounting relationships (zero-balance trust lines) when using Authorized Accounts. With this amendment enabled, currency issuers can authorize other addresses to hold their … Continued

Multi-Signing is Now Available

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). Multi-signing provides more flexibility for sending transactions from your Ripple address. You can use multi-signing alongside a master key pair or regular key pair, or you can disable your other keys and use multi-signing exclusively. … Continued

rippled 0.32.0 has been released

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. Highlights of this release include: The transaction queue now supports batching and can hold up to 10 … Continued

Multi-Signing Will Soon Be Available

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: How to Multi-Sign MultiSign Amendment Information To continue receiving updates about the rippled server, please subscribe … Continued

Data API v2.2 Released

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. One of the biggest changes in the new version is the incorporation of data relating to the Ripple network itself. … Continued

rippled 0.31.2 and Other Updates

The rippled team is proud to announce a bundle of related news items: rippled release 0.31.2 Amendments system Transaction cost changes Multi-signing rippled 0.31.2 rippled 0.31 introduced several new features, including Amendments, Multi-Signing, a transaction queue, and changes to transaction cost escalation. Version 0.31.2 includes important fixes for security, stability, and compatibility with the official … Continued

Introducing RippleAPI

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. If you’re excited to get started with the new RippleAPI right away, jump right in with … Continued

rippled 0.30.1 Released

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 … Continued

Correction to Ripple White Paper

We’ve recently been made aware of a paper discussing the possibility of forks in the Ripple system. We agree with the authors’ conclusion that a fork is not possible given that the UNL overlap is greater than 40%. Unfortunately, this is different than the 20% figure stated in our 2014 white paper. We apologize for … Continued

Validator Registry

Today we are excited to announce the launch of the Ripple Validator Registry at validators.ripple.com

Introducing the Data API

Ripple Labs data is moving under one roof, the Data API – a version two of the Historical Database API – and one infrastructure, Hadoop.

Gatewayd No Longer Available

In the interest of focusing our resources on other projects, starting today, Gatewayd will no longer be available on Github.

Do You Have What It Takes to Be a Gateway?

We’re proud to announce the first release of our new Gateway Guide, a comprehensive manual to operating a gateway in the Ripple network. Whether you’re trying to understand how a gateway makes revenue, or how to use the authorized accounts feature, or even just what a warm wallet is, the gateway guide has you covered. … Continued

Calculating Balance Changes for a Transaction

When interacting with Transactions on the Ripple Network you often care about the changes that have been made to a specific account. For example, if you make a payment, you want to know by how much the balance on your account has been decreased. Parsing out the exact balance changes from a transaction can often be complicated and we’ve spend a lot of time to provide a simple method for getting accurate information. In an effort to standardize the way we deal with balance changes and make sure we have one place that captures our efforts, we released a module, called ripple-lib-transactionparser. We’ve made the module available on npm and you can find the source on our github

In this post we want to provide some background on why parsing balance changes is hard and give details on how a transaction’s metadata should be interpreted.

Turn your exchange into a Ripple Gateway

Throughout 2014 we’ve talked to businesses all over the world, both big and small, who are interested in tapping into Ripple’s increasing liquidity and settlement capabilities. For exchanges dealing in bitcoins and other assets, the value proposition is clear – deeper orderbooks and the ability for customers to hop between different assets instantly is a … Continued

Why the Stellar Forking Issue Does Not Affect Ripple

The Stellar Development Foundation (SDF) which maintains Stellar, a network built on a modified version of the Ripple code base, recently published a post claiming flaws in the Ripple consensus algorithm. We take any reports about possible security issues very seriously and after reviewing the information conclude that there is no threat to the continued operation of … Continued

Release Notes (3 December 2014)

Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features. Codius [Github] New website and documentation – check it out! Ripple-Rest [Release Notes | Github | Issue Tracking] Released version 1.3.2-rc1 Add place and cancel order functionality d80d198 … Continued

Release Notes (19 November 2014)

Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features. Rippled [Release Notes | Github | Issue Tracking] Released version 0.26.4 Rocksdb v. 3.5.1 SQLite v. 3.8.7 Disable SSLv3 Add counters to track ledger read and … Continued

ripple-rest 1.3 release

Last Friday we did a master release of ripple-rest version 1.3.0. We’ve done a few changes externally but the substantial additions in 1.3.0 have been stability and verbose error handling. If you’ve been following the commits on [github](https://github.com/ripple/ripple-rest), we’ve also vastly improved test coverage and introduced simplicity by removing the need for Postgres.

Release Notes (29 October 2014)

Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.

We hope you find these useful! Please let us know if you have feedback in the comments.

Gateway Advisory On Partial Payment Flag

Ripple Labs has issued a Gateway Bulletin on the Partial Payment flag which describes the flag and best practices around balancing activity on and off the ledger. The tfPartialPayment flag is set by the sender to specify a payment where the beneficiary can receive less than the specified amount.
Gateways are encouraged to implement best practices and understand the Partial Payment flag to mitigate errors that can result in fraud if undetected.
To view this bulletin, please visit: https://wiki.ripple.com/Gateway_Bulletins

Release Notes (14 October 2014)

Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.
We hope you find these useful! Please let us know if you have feedback in the comments.
Rippled [Release Notes | Github | Issue Tracking]
Released version 0.26.3-sp4
Update for validating rippled servers that includes new transaction fee logic

How Ripple Labs supports gateways

To help accelerate the creation of strong, reliable, and compliant gateways, Ripple Labs will be providing XRP incentives and extended technical support for gateways that meet criteria considered to be critical for the success of a gateway.

Ripple Labs wants every gateway to achieve a gold standard in business planning, technical reliability and stability, regulatory compliance, and liquidity. The Ripple protocol enables the federation and interoperability of many independent payment systems.

As such, we’re actively developing the specifications for Gateway Services APIs and are eager to help gateways with implementation. In the meantime, here are some of the steps and assistance provided by Ripple Labs to help get your gateway to that point.

Biweekly release notes (17 September 2014)

Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.

We hope you find these useful! Please let us know if you have feedback in the comments.

Biweekly Release Notes (3 September 2014)

A few days tardy, but better late than never…

Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.

We hope you find these useful! Please let us know if you have feedback in the comments.

Consensus Whitepaper Released

Ripple Labs has just released a whitepaper describing the Ripple network’s consensus algorithm and its properties. The Ripple network combines Ryan Fugger’s original rippling ideas with a p2p transactional database. Consensus is the distributed agreement protocol that the Ripple network uses to irreversibly arbitrate changes to this database in just a few seconds.

Use of C++14 in rippled

C++ is a language under constant development, resulting in alternating minor and major releases. The last major release of C++ was C++11. A minor release has just been approved by all participating national bodies (zero negative votes). This will be C++14. C++17 is the next planned major release and is currently under development by the committee.

Rippled has already adopted a number of useful C++14 features. We’ve done this through the development environment where native support is available, or by emulating the features through providing compatible implementations using our beast cxx14 compatibility library ( https://github.com/ripple/rippled/tree/develop/src/beast/beast/cxx14). A brief list of notable features:

Biweekly Release Notes (14 August 2014)

Release notes are part of a larger overhaul of our developer resources, which we are continually adding to.

Curated release notes wiposted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.

We hope you find these useful! Please let us know if you have feedback in the comments.

Dev Portal Adds rippled APIs

Today, the Ripple Dev Portal gets a big boost of content and usability. The new additions to our development portal include thorough and tested documentation of all the public API methods for our core server software, ‘rippled’, alongside a host of improvements in styling and formatting, as well as new introductory material to give you direction in navigating the sea of Ripple technology.

This update brings very crucial content into the fold of documentation that’s thorough, complete, and software-tested. Today, you can access full specs and usage information for all 20+ public methods in the rippled WebSocket API.

Biweekly release notes (31 July 2014)

Starting today, Ripple Labs will release curated release notes on a bi-weekly basis to ensure better communication with the developer community about ongoing projects.

This effort is part of a larger overhaul of our developer resources which currently leave a bit to be desired.

The curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.

XRP Giveaway for Developers

Ripple Labs has partnered with Assembla to send qualified developers 1,000 XRP to their Ripple Trade account. To apply for this giveaway please fill out and submit the application form.

If you’re interested in developing on Ripple please check out the Primer for a high level overview. From there you can dive into different layers of the Ripple ecosystem.

Ripple Labs Bounty Program Moves To Bountysource

The Ripple Labs Bounty Program is moving to its new home at Bountysource, a vibrant and robust bounty marketplace that will make paid contributions to the Ripple source code more effective and efficient.

By making Ripple projects easier to manage and participate in, the Bountysource platform will help us expand and engage with our open source community. We look forward to your contributions!

Introducing: Offer Autobridging

Ripple’s powerful system allows payments between any source and destination currency to be made easily. Pathfinding considers multiple conversions between currencies to find the best rate for a payment.

The new autobridging feature improves offer placement in a similar fashion to pathfinding: when consuming existing offers, a newly placed offer will have the liquidity available in not only the direct order book (source to destination currency) but also in the corresponding books in which XRP is the destination and source respectively.

This expands the Ripple protocol’s capabilities and brings improved market depth for heavily-used asset pairs and improved liquidity for less-heavily-used asset pairs. A primer for Ripple’s autobridging implementation is available on the Ripple Forums.

Curves with a Twist

Ripple Labs is considering the addition of a new elliptic curve implementation to the Ripple protocol to complement the existing cryptographic system. The addition of a Schnorr-based cryptosystem will produce more optimal and secure design schemes and provides a platform for robust and sophisticated functionality while preserving existing network structure and efficiency.

Introducing Ripple Names

We’re excited to introduce Ripple names. Ripple names will work in conjunction with Ripple addresses as a destination to receive funds, an identifier for the sender, and setting trustlines.