Posted 2022-05-23 to

Introducing XRP Ledger version 1.9.1

Version 1.9.1 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release includes several important fixes, including a fix for a syncing issue from 1.9.0, a new fix amendment to correct a bug in the new Non-Fungible Tokens (NFTs) code, and a new amendment to allow multi-signing by up to 32 signers.

Read more
Posted 2022-03-01 to

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.

Read more
Posted 2022-02-08 to

Introducing XRP Ledger version 1.8.5

Version 1.8.5 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release includes fixes and updates for stability and security, and improvements to build scripts, including the ability to compile natively on Apple's M1 chips. There are no user-facing API or protocol changes in this release.

Read more
Posted 2022-01-13 to

Introducing XRP Ledger version 1.8.4

Version 1.8.4 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release improves syncing performance including a new "fast load" setting, adds countermeasures for a security vulnerability in LZ4, and adjusts some tuning parameters to improve resource usage. Notably, this release limits pathfinding API methods to fewer and shorter paths because the previous pathfinding settings were causing excessive memory usage as a result of the overall size of the XRP Ledger Mainnet data.

This release supersedes version 1.8.3, and fixes an issue that was discovered during the release cycle.

Read more
Posted 2021-12-20 to

Introducing XRP Ledger version 1.8.2

Version 1.8.2 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release addresses the full transaction queues and elevated transaction fees issue observed on the XRP ledger, and also provides some optimizations and small fixes to improve the server's performance overall.

Due to the holidays, version 1.8.2 is being made available as a "soft release" in the unstable package channel so that operators who are interested can upgrade. Automatic updates will not update to this release until it is pushed to the stable branch at a later date.

Read more
Posted 2021-12-02 to

Introducing XRP Ledger version 1.8.1

Version 1.8.1 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release contains several improvements and optimizations to improve stability and performance under load, along with other features and fixes including deterministic history shards, default amendment votes, and the CheckCashMakesTrustLine amendment.

This release supersedes version 1.8.0. Version 1.8.1 makes additional changes to database tuning parameters to optimize start-up and syncing time. It is highly recommended that operators upgrade to 1.8.1 as soon as possible because the optimizations in this release should help alleviate some of the pressure on the network from increased usage.

Read more
Posted 2021-11-10 to

Five Amendments Expected Soon

Several amendments to the XRP Ledger protocol are expected to become enabled on the XRP Ledger Mainnet soon. Three of these amendments fix bugs in the XRP Ledger protocol, one (NegativeUNL) improves the ability of the network to make forward progress during periods of instability, and the last one (TicketBatch) adds the ability to prepare and send transactions in a more flexible order. The details are as follows (all dates are in UTC):

  • fixSTAmountCanonicalize (min version: 1.7.0) expected 2021-11-11.
  • FlowSortStrands (min version: 1.7.0) expected 2021-11-11.
  • fixRmSmallIncreasedQOffers (min version: v1.7.2) expected 2021-11-18.
  • TicketBatch (min version: v1.7.2) expected 2021-11-18.
  • NegativeUNL (min version: v1.7.3) expected 2021-11-21.

Each amendment will become enabled if it maintains support from at least 80% of trusted validators until its expected time. Operators of rippled servers must upgrade to the minimum version or higher by the time these amendments become enabled.

Read more

Older Articles