xrpld 3.4.1: the latest XRP Ledger release, and where 3.5.0 stands (November 2026)

The XRP Ledger (XRPL) server software, xrpld (formerly rippled), is the reference implementation of the protocol. Validators and nodes run it. The question was whether version 3.5.0 is out. The short answer: not as of 14 November 2026. There is a 3.5.0-rc1 tag on GitHub, which is a release candidate, not a release. The latest actual release is 3.4.1 (GitHub, XRPLF/rippled releases). This article covers 3.4.1 and sets out what can be verified about 3.5.0 today.

On the GitHub releases list, the newest release marked "Latest" is 3.4.1 (GitHub, XRPLF/rippled releases). The repository does contain a 3.5.0-rc1 tag. Its message reads "Version 3.5.0-rc1 release" and it is dated 20 October 2026 (GitHub, 3.5.0-rc1 tag). No published release or release notes are attached to it. The xrpl.org blog has no 3.5.0 post either; its most recent server release post is for 3.4.1 (xrpl.org blog).

For that reason, this article does not describe 3.5.0's contents, amendments or deadlines. Those can be verified once official release notes are published.

According to the release notes, 3.4.1 is an emergency release to fix security-sensitive issues (xrpl.org, xrpld 3.4.1). It was first published as binary-only packages. The source code followed later on GitHub, where the release is dated 10 October 2026 (GitHub, 3.4.1).

The release introduces one new amendment:

• fixBatchV1_2, with the default vote set to "Yes". It closes a validation gap in Batch transactions and also carries other security and stability fixes (xrpl.org, xrpld 3.4.1).

The changelog lists four items, including the Batch fix and integer-arithmetic hardening in the payment engine and ledger helpers (xrpl.org, xrpld 3.4.1).

Packages are hosted at packages.xrplf.org and signed with an XRP Ledger Foundation key. Version 3.4.0 introduced that hosting (xrpl.org, xrpld 3.4.0).

The details are in the disclosure report dated 9 October 2026 (xrpl.org, Vulnerability Disclosure Report for xrpld 3.4.1).

1. Batch: wrapping of inner transactions. The Batch feature (XLS-56) lets one account submit up to eight transactions as a unit. The specification requires each inner transaction to sit in a RawTransaction field. The server did not enforce this, so inner transactions wrapped in other fields could still be applied. The second risk was consensus: validators on different versions could disagree about the same transaction. The report says 3.3.0 and 3.4.0 were affected, but BatchV1_1 was not yet enabled on Mainnet. After the fix, the protocol rejects a wrong wrapper with temMALFORMED.

2. Overflow in the payment engine. An integer overflow meant that a crafted set of offers and a single payment could produce a state in which XRP was created. The report says the bug had likely been present since 2015 and rated it critical. This fix is not an amendment; it takes effect on each server when that server upgrades to 3.4.1.

According to the report, there is no evidence that either issue was exploited on a public network, and no funds were lost.

The required action is clear, and its deadline has already passed.

• The 3.4.1 post said fixBatchV1_2 was expected to be enabled on 9 October 2026, and that servers not upgraded by then would become amendment blocked, unable to stay in sync with the network (xrpl.org, xrpld 3.4.1).
• The disclosure report states that fixBatchV1_2 and BatchV1_1 were enabled on Mainnet on 9 October 2026 (xrpl.org, report).
• The GitHub release text says older releases are therefore now amendment blocked (GitHub, 3.4.1).

Anyone running a server connected to Mainnet needs version 3.4.1 or later. Installation and update instructions are in the xrpl.org documentation (xrpl.org, Installation).

• Batch is live on Mainnet. BatchV1_1 was deliberately held back until the fix was active, so Batch only became available together with the fix (xrpl.org, report).
• Stricter validation. A tool that builds Batch transactions must place each inner transaction in a RawTransaction field, or it will receive temMALFORMED.
• Testnet and Devnet reset. A separate matter in the same month: on 25 November 2026 all ledger data on both test networks will be deleted (xrpl.org blog).

Affected:

• every xrpld server running a version older than 3.4.1 (amendment blocked);
• tools and libraries that build Batch transactions.

Not affected:

• account balances: according to the report, no funds were lost and there is no evidence of exploitation;
• 3.5.0, because it has not been released.

• When 3.5.0 will be released and what it will contain. There are no official release notes yet.
• The 3.4.1 source code appeared on GitHub on 10 October. The 3.4.1 post also said a retrospective would follow at a later date (xrpl.org, xrpld 3.4.1).

Data Analytic Investments is not affiliated with Ripple or the XRP Ledger Foundation (XRPLF).

• GitHub – XRPLF/rippled releases
• GitHub – xrpld 3.4.1 release (10 October 2026)
• GitHub – 3.5.0-rc1 tag (20 October 2026)
• xrpl.org – Introducing XRP Ledger version 3.4.1 (25 September 2026)
• xrpl.org – Vulnerability Disclosure Report for xrpld 3.4.1 (9 October 2026)
• xrpl.org – Introducing XRP Ledger version 3.4.0 (16 September 2026)
• xrpl.org – Upcoming Testnet and Devnet Resets (9 November 2026)
• xrpl.org – Installation
• xrpl.org – Blog

Educational content. Not investment advice.