Draft release blog for 2.3.1

Author: amarantha-k

blog/2025/rippled-2.3.1.md

@@ -0,0 +1,70 @@
+---
+category: 2025
+date: 2025-01-27
+seo:
+    title: Introducing XRP Ledger version 2.3.1
+    description: rippled version 2.3.1 is now available. This version introduces new features and stability fixes.
+labels:
+    - rippled Release Notes
+markdown:
+    editPage:
+        hide: true
+---
+# Introducing XRP Ledger version 2.3.1
+
+Version 2.3.1 of `rippled`, the reference server implementation of the XRP Ledger protocol, is now available. This release includes bug fixes and updates.
+
+## Action Required
+
+If you run an XRP Ledger server, upgrade to version 2.3.1 as soon as possible to ensure service continuity.
+
+## Install / Upgrade
+
+On supported platforms, see the [instructions on installing or updating `rippled`](../../docs/infrastructure/installation/index.md).
+
+| Package | SHA-256 |
+|:--------|:--------|
+| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-2.3.1-1.el7.x86_64.rpm) | `fb74f401e5ba121bbc37e6188aa064488ad78ffef549a1e19bc8b71316d08031` |
+| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.3.1-1_amd64.deb) | `5d616d53218b47a2f0803c1d37d410f72d19b57cdb9cabdf77b1cf0134cce3ca` |
+| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
+
+For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
+
+```text
+commit f64cf9187affd69650907d0d92e097eb29693945
+Author: Elliot Lee <github.public@intelliot.com>
+Date:   Mon Nov 25 12:27:17 2024 -0800
+
+    Set version to 2.3.0
+```
+
+
+## Full Changelog
+
+### Amendments and New Features
+
+- None
+
+### Bug Fixes and Updates
+
+- A fix for an erroneous high fee penalty that peers could incur for sending older transactions.
+- An update to the fees charged for imposing a load on the server.
+- A fix to prevent the relaying of internal pseudo-transactions. Previously, psuedo-transactions received from a peer failed the signature check, even if they were requested (using TMGetObjectByHash), because they had no signature. This caused the peer to be charged for an invalid signature. With the fix, pseudo-transactions are placed in the global cache (TransactionMaster) only. If the transaction is not part of a TMTransactions batch, the peer is charged an unwanted data fee. These fees will not be a problem in the normal course of operations, but should dissuade peers from sending a bunch of unwanted transactions.
+- Improved logging now specifies the reason for the fee charged to the peer.
+
+## Credits
+
+The following people contributed directly to this release:
+
+- Ed Hennis <ed@ripple.com>
+- JoelKatz <DavidJoelSchwartz@GMail.com>
+- Sophia Xie <106177003+sophiax851@users.noreply.github.com>
+- Valentin Balaschenko <13349202+vlntb@users.noreply.github.com>
+
+
+## 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>
+

blog/sidebars.yaml

@@ -6,8 +6,9 @@
     - group: '2025'
       expanded: false
       items:
-        - page: 2025/vulnerabilitydisclosurereport-bug-nov2024.md
+        - page: 2025/rippled-2.3.1.md      
         - page: 2025/devnet-reset.md
+        - page: 2025/vulnerabilitydisclosurereport-bug-nov2024.md
     - group: '2024'
       expanded: false
       items: