Version 3.2.1 of xrpld, the reference server implementation of the XRP Ledger protocol, is now available.
This release contains fixes for security issues in validator manifest propagation that, in the worst case, could cause a server to use excessive memory and processing resources. There are no new features or amendments in this release.
If you run an XRP Ledger server, upgrade to version 3.2.1 as soon as possible to ensure service continuity.
On supported platforms, see the instructions on installing or updating xrpld.
| Package | SHA-256 |
|---|---|
| RPM for Red Hat / CentOS (x86-64) | 0349682e4ae99206543dae4861a4af534d12607ece24ffdf9e5c96ba7e0d239c |
| DEB for Ubuntu / Debian (x86-64) | b0cd5762a739feaa9c2c7b0d0d61abbb6cad382c7dc73bddff6af63a5156075e |
For other platforms, please build from source. The most recent commit in the git log should be the change setting the version:
commit d4c1359921f34a4e96c5c8483119e59f0e30e4df
Author: Ed Hennis <[email protected]>
Date: Fri Jul 31 19:46:17 2026 -0400
chore: Bump version to 3.2.1- Fixed a problem with validator manifest propagation that could cause a server to use excessive memory and processing resources. (#7925)
The following RippleX teams and GitHub users contributed to this release:
- RippleX Engineering
- RippleX Docs
- RippleX Product
We welcome reviews of the xrpld code and urge researchers to responsibly disclose any issues they may find.
For more information, see: