Earlier this year, Ripple shared a vision for Federated Sidechains that can complement the XRP Ledger (XRPL) Mainnet. Federated Sidechains support the developer community by unlocking new capabilities related to smart contracts and DeFi, interoperability, NFTs and more.
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.
Version 1.7.3 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release addresses an out-of-bounds memory read identified by Guido Vranken, as well as an unrelated issue identified by the Ripple C++ team that could result in incorrect use of internal data structures. By community demand, this version also introduces the NegativeUNL amendment, which corresponds to the feature which was introduced in the 1.6.0 release.
Version 1.10.0 of ripple-lib, the JavaScript/TypeScript library for the XRP Ledger, no longer requires a separate Lodash script to run in web browsers. This change comes alongside other continued improvements in the library, improving the experience of developing applications on the XRP Ledger.
XRPL Grants is helping enable developers to leverage the XRP Ledger’s (XRPL) open-source technology to further innovate in the Internet of Value. If you’re a developer and would like to build a project on the XRPL, keep reading to find out more info and how to apply.
Version 1.7.2 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release protects against the security issue CVE-2021-3499 affecting OpenSSL, adds an amendment to fix an issue with small offers not being properly removed from order books in some cases, and includes various other minor fixes.
This release supersedes version 1.7.1 and adds fixes for more issues that were discovered during the release cycle.
RippleX and the XRP Ledger Foundation (XRPLF) are pleased to announce the release ofxrpl4j, a pure Java library for interacting with the XRP Ledger (XRPL). xrpl4j provides convenient tooling for developers to take full advantage of all the XRP Ledger has to offer, including wallet derivation, address encoding, transaction serialization and signing and native Java objects modeling core primitives of the rippled API.
by Javier Romero of Ripple
The XRP Ledger is open to anyone: all you need is a computer. For many people, using one of the many available client applications, user interfaces or portals is sufficient. But if you want to go beyond exploring the ledger or sending a payment, you need to run a server to participate as a node in the peer-to-peer network that manages the Ledger.
While the docs on xrpl.org make it fairly easy for anyone to spin up an XRP Ledger node, some nuanced configuration options can complicate the setup process. To help simplify this process, we've built the XRPL Node Configurator, a tool that walks you through setting up a node based on your use case.
by Team RippleX
Today, RippleX and the XRP Ledger Foundation (XRPLF) are excited to announce the launch of xrpl-py, a pure Python implementation for interacting with the XRP Ledger. The xrpl-py library simplifies the hardest parts of XRP Ledger interaction—like serialization and transaction signing—by providing native Python methods and models for XRP Ledger transactions and core server API (rippled) objects.
Two bug-fixing amendments to the XRP Ledger protocol and one amendment that improves robustness of consensus, all introduced in rippled v1.6.0, have gained support from a majority of trusted validators: fix1781, fixAmendmentMajorityCalc, and HardenedValidations. Currently, they are expected to become enabled on 2021-04-08. Any of these amendments that continue to have the continuous support of at least 80% of trusted validators will become enabled on the scheduled date.
Server operators should be sure to upgrade rippled before this date.