The NFT-Devnet Decommissioned on January 31, 2023

The "NFT-Devnet" was a test network running experimental code to support Non-Fungible Tokens (NFTs) natively on the XRP Ledger (per the XLS-20 standard).

The NFT-Devnet server has been down for unrelated reasons since January 16th, 2023. Given that there have been no inquiries from developers, it is likely all users have reconfigured their sample applications to use the XRP Testnet. We encourage you to move to the XRP Testnet at your earliest convenience.

The "NFT-Devnet" preview server is now decommissioned and will not return to service.

The NFT-Devnet Has Been Reset

The "NFT-Devnet" is a test network running experimental code to support Non-Fungible Tokens (NFTs) natively on the XRP Ledger (per the XLS-20 draft standard). Ripple has reset the NFT-Devnet while upgrading it to the latest version of the preview code.

Lower Reserves Are Now In Effect

Over the course of the past year, several members of the XRP Ledger community have advocated for lowering the reserve requirements in the network to compensate for the sustained increase in the price of XRP. On 2021-09-19, the new reserve values went into effect after gaining support from a majority of validators. The new reserve amounts are 10 XRP base for an account plus 2 XRP per object owned in the ledger, down from 20 XRP base and 5 XRP per object owned.

Moving Devnet to a Validator List

Ripple plans to upgrade the XRP Ledger Devnet to use a recommended validator list like the ones used on the Testnet and Mainnet. Ripple also plans to reset the Devnet history and state at this time. If you operate a server on the XRP Ledger Devnet, or run software on the Devnet, you must upgrade your configuration to remain synced.

Postmortem: Testnet Amendments from rippled 1.5.0

Like most new releases, version 1.5.0 of the XRP Ledger core server (rippled) contains new amendments which are not understood by earlier versions of the software.

XRP Ledger version 1.4.0 Upgrade Advisory

Version 1.4.0 of the XRP Ledger core server (rippled) contains a change that can cause upgrades to take much longer than usual.

XRP Testnet Has Been Reset

Update: The second reset occurred as planned and the Testnet became fully available by approximately 7:56 PM PDT. The amendments that are enabled on the Testnet now match the status of amendments on the production Mainnet.

On 2019-08-27 at approximately 1:00 UTC (6 PM PDT), Ripple reset their XRP Testnet. This means that all accounts, balances, and settings in the Testnet have been deleted and all contents of the Testnet's decentralized exchange have been erased. However, in the process of resetting the XRP Testnet, a procedural issue caused amendments that were previously enabled to be disabled in the fresh ledger chain. Ripple plans to reset the XRP Testnet again today (2019-08-30) at 4 PM PDT. Starting at this time, the Testnet may be unavailable for a maintenance window lasting up to 4 hours.

The production XRP Ledger, or Mainnet, is completely unaffected. This also has no effect on other test networks not run by Ripple.

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.

rippled Validator Key Replacement

On Wednesday, January 18, 2018, as described in the 0.81.0 release notes, the current validator keys on all five Ripple-operated rippled validator servers will be replaced. If you have been using the previous recommended default configuration and do not reconfigure your rippled server to the new recommended default configuration before that time, then your rippled server will stop seeing validated ledgers.

Boost 1.66 Not Supported for rippled 0.81.0

A warning to developers: rippled versions 0.81.0 and earlier do not compile with the recently-released Boost library version 1.66.0. To compile rippled yourself, Ripple recommends using Boost version 1.65.1. The minimum supported version of Boost is 1.58.0, which is included in the official repositories of Ubuntu 16.04 Xenial.

rippled RPM version 0.60.2-2

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.

Gateway Bulletin: Setting Trust Line Quality with SendMax

Summary

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.

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.

Gatewayd No Longer Available

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

Calculating Balance Changes for a Transaction

Introduction

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