This hotfix release is strongly recommended for any operators currently running 2.3.0, and upgrading from prior versions. It fixes an ongoing issue where normal peer traffic is charged incorrectly, causing peers to be disconnected inappropriately during normal operations. This affects network connectivity and the ability of some UNL validators to reach consensus with the others.
Version 2.3.1 does not introduce any new amendments over 2.3.0.
What's Changed
- Proposed 2.3.1-rc1: Reduce the peer charges for well-behaved peers by @vlntb in #5243
- Peer charges are completely different from transaction cost/fees. They are used to rate limit other
ripplednodes, and to detect and disconnect peers putting too much demand on the server.
- Peer charges are completely different from transaction cost/fees. They are used to rate limit other
- Proposed version 2.3.1 by @ximinez in #5259
Full Changelog: 2.3.0...2.3.1
Bug Bounties and Responsible Disclosures:
We welcome reviews of the rippled code and urge researchers to responsibly disclose any issues they may find.
To report a bug, please send a detailed report to: bugs@xrpl.org