2019

Posted 2019-06-14 to

Welcome to xrpl.org!

xrpl.org is a new, community-driven website for developers to access technical documentation, developer tools, tutorials, and network metrics for the XRP Ledger. The XRP Ledger is one of the largest, most technically mature, open-source, public blockchain networks in the world. If you are learning about, building on, and contributing to the XRP Ledger, xrpl.org is your best resource.

Posted 2019-04-17 to

Introducing XRP Ledger (rippled) version 1.2.4

Ripple has released version 1.2.4 of rippled, the reference implementation of the core XRP Ledger protocol.

Version 1.2.4 improves the verification and routing of shard crawl requests and imposes a 20 second timeout onto the component that checks for an updated validator list to prevent it from becoming blocked for an indefinite amount of time.

Posted 2019-04-05 to

Protecting the Ledger: Secure Development Practices

By Nik Bougalis, Engineering Manager

The primary mission of the C++ team at Ripple is to contribute to rippled, the reference implementation of the protocol that underpins the XRP Ledger. The codebase—which is now over 6 years old—has contributions from over 100 developers from all over the world.

As a team, our primary focus is on ensuring that the codebase is solid, that the code is robust and that it is well-suited to be the core of the next-generation of financial infrastructure, one which allows value to not only move as fast and as efficiently as information does today, but to move securely as well.

In an earlier blog post, I noted that our existing software development and quality assurance process—honed over several years—places heavy emphasis on correctness and security. I highlighted our use of automated tests and specialized tooling (such as static analyzers) but I also alluded to the human element as well: our rigorous and public code reviews and regular security audits of the codebase by specialists. I’d like to take the opportunity to discuss those practices in greater detail.

Posted 2019-04-04 to

Corrections to Data API / XRP Charts Metrics for 2019-03-23

The Data API, an open API that provides data to XRP Charts and third-party tools, suffered gaps in data ingestion on 2019-03-23. As a result, several metrics on XRP Charts, including the number of ledgers closed per day, were overcounted. During this time, the XRP Ledger did not experience any outages. However, the Data API's ingestion service was unable to process ledgers with transactions containing the tecKILLED transaction response code. tecKILLED is a new response code added to the XRP Ledger by amendment fix1578 on 2019-03-23. This necessitated changes to the ripple-binary-codec library used by the ingestion service, but those changes were only partially deployed to the ingestion service. We have since reprocessed and corrected the metrics that were affected by this problem.

Posted 2019-04-03 to

Interledger Check-in

Here at Ripple, we've been eagerly following and contributing to the progress of Interledger, a neutral standard for connecting all money systems into an Internet-like network of networks. Since finalizing the core protocol suite in late 2017, contributors from a variety of companies and backgrounds have been working hard on growing the ecosystem with implementations and infrastructure. Progress has been rapid and wild, so we thought we'd help make sense of it by checking in to see where Interledger stands today.

Posted 2019-03-19 to

The fix1578 and fixTakerDryOfferRemoval Amendments are Expected

The fix1578 amendment to the XRP Ledger, introduced in rippled v1.2.0, has gained support from a majority of trusted validators. Currently, it is expected to become enabled on 2019-03-23.

The fixTakerDryOfferRemoval amendment to the XRP Ledger has also gained support from a majority of trusted validators. Currently, it is expected to become enabled on 2019-04-02.

As long as the amendments continue to have the support of at least 80% of trusted validators continuously, they will become enabled on the expected dates.

Posted 2019-03-06 to

Introducing XRP Ledger (rippled) version 1.2.2

Ripple has released version 1.2.2 of rippled, our reference implementation of the core XRP Ledger server.

Version 1.2.2 corrects a technical flaw in the fee escalation engine which could cause some fee metrics to be calculated incorrectly. In some circumstances this can potentially cause the server to crash.

Posted 2019-02-26 to

Introducing XRP Ledger (rippled) version 1.2.1

Ripple has released version 1.2.1 of rippled, our reference implementation of the core XRP Ledger server.

Version 1.2.1 introduces several fixes including:

  • A change in the information reported via the enhanced crawl functionality introduced in version 1.2.0.

  • A fix for a potential race condition when processing a status message for a peer.

  • A fix for a technical flaw that could cause a server to not properly detect that it had lost connectivity.

Version 1.2.1 also adds the delivered_amount field to more responses to simplify the handling of payment or check cashing transactions.

Posted 2019-02-13 to

Introducing XRP Ledger (rippled) version 1.2.0

Ripple is pleased to announce the release of XRP Ledger (rippled) version 1.2.0.

The XRP Ledger version 1.2.0 release introduces the MultisignReserve Amendment, which reduces the reserve requirement associated with signer lists for Multisign. This release also includes incremental improvements to the code that handles offers in the decentralized exchange (fixTakerDryOfferRemoval and fix1578 Amendments).

One of the major benefits of decentralized blockchain technologies, such as the XRP Ledger, is censorship resistance. Already highly resistant to censorship attempts, with the release of version 1.2.0 of the XRP Ledger, servers now have the ability to automatically detect transaction censorship attempts and issue warnings of increasing severity for transactions that a server believes should have been included in a closed ledger after several rounds of consensus.

Posted 2019-01-14 to

Statement on the “Biased Nonce Sense” Paper

In the cryptography industry, it is well known that using repeated or insufficiently random "nonces" (also called "k" values) in ECDSA digital signatures carries security risks. A new research paper authored by Joachim Breitner and Nadia Heninger discloses a more serious attack than was previously known on signatures with imperfect nonces.