on the Ledger
This Week on the Ledger
XRPL discloses a long-standing payment engine overflow bug, Batch and Permission Delegation amendments activate on Mainnet, and Ripple Prime expands its Brevan Howard mandate.
On October 9, XRPL.org published the details of two vulnerabilities that were fixed privately in xrpld 3.4.1, including a payment engine flaw that could have created spendable XRP beyond the total supply. The same day, the amendment that fixes the second of those bugs activated on Mainnet, followed half an hour later by Batch transactions, a day after Permission Delegation went live. Outside the protocol, Ripple Prime widened its mandate with Brevan Howard, Evernorth said its XRP treasury company expects to begin trading on Nasdaq on or about October 12, and the European Securities and Markets Authority gave crypto firms three months to wind down services in stablecoins that do not comply with MiCA.
Protocol Security: A Long-Hidden Payment Engine Flaw, Disclosed After the Fix
The vulnerability disclosure report published on XRPL.org on October 9 covers two bugs fixed in xrpld 3.4.1, the emergency release that shipped on September 25. The more serious one was reported on September 22 through the XRPL Bug Bounty program by Cayden Liao and Veria AI. RippleX Engineering reproduced it, confirmed that the XRP it created could be spent, and raised its severity to critical. The report suggests the flaw dates to the payment engine’s 2015 code.
The mechanism was an arithmetic overflow. An attacker could place a few hundred offers, spread across accounts they control, each selling a tiny amount of a token for a very large amount of XRP, and then consume all of them with a single payment from another account. The engine added up the buyer’s XRP cost using 64-bit integer addition with no overflow check, so the total wrapped around to a small number. Each offer owner was paid in full while the buyer was charged only the wrapped total, and the difference was newly created XRP. The invariant that confirms no XRP is created used the same unchecked arithmetic, so the transaction looked like an ordinary fee-only payment, and per-account balance checks also passed because the XRP was spread across many accounts. The report estimates the cost to an attacker at a few hundred XRP in reserves plus fees, and states that it found no evidence the issue was exploited on any public network.
The fix did not go through an amendment vote. It took effect on each server as that server upgraded, which the report describes as the first time a change to transaction processing has deliberately shipped this way. According to the report, more than 80 percent of default UNL validators were running 3.4.1 or later by September 25. The full source code is now on GitHub, and the release notes tell every server operator to upgrade as soon as possible. The report also adds a re-verification step to the release process: every security finding marked as fixed is retested against the release candidate and closes only when a test reproducing the original issue passes. It lists AI-assisted red teaming alongside audits, attackathons, fuzzing and formal verification as layers of defence.
Protocol Governance: Batch Transactions and Permission Delegation Go Live
The second bug in the report affected Batch transactions before they had activated. It was first logged as a low-severity finding in the Sherlock Attackathon; during re-verification, Denis Angell of the XRPL Foundation found the original fix was incomplete, and Mayukha Vadari of RippleX identified a consensus risk that made it a blocker. Validators withdrew support from BatchV1_1, which had been scheduled to activate on September 29, to reset its clock, and the corrective amendment fixBatchV1_2 entered its two-week window on September 25. The report states there was no loss of funds and no Mainnet transaction was processed incorrectly.
According to the XRPL Dashboard, three amendments activated this week:
- PermissionDelegationV1_1 on October 8 at 21:29 UTC (ledger 107,524,865).
- fixBatchV1_2 on October 9 at 14:15 UTC (ledger 107,540,481).
- BatchV1_1 on October 9 at 14:47 UTC (ledger 107,540,993).
Batch transactions let an account package up to eight inner transactions and execute them as a single unit, in one of four modes: all-or-nothing, only-one, until-failure or independent. The all-or-nothing mode removes the risk of a multi-step operation completing only partway. Because fixBatchV1_2 is now enabled, the 3.4.1 release notes state that older server versions are amendment blocked.
Permission Delegation lets an account grant another account the right to send specific transaction types on its behalf, with up to 10 permissions per delegate. The delegate signs with its own keys, and the delegating account can change or revoke the grant at any time. The documentation frames this as role-based access control: an institution can keep high-privilege keys offline while day-to-day, internet-connected systems hold only narrow permissions. The same documentation recommends against delegating the PaymentBurn permission until the fixCleanup3_4_0 amendment is enabled, because before that fix a delegate holding it could, in certain circumstances, also mint trust line tokens or MPTs.
One open question concerns the vote counting itself. GitHub issue #8534, filed on October 8, reports that long-running servers stop counting a validator’s amendment votes, and drop it from the threshold calculation, after it rotates its ephemeral signing key, until the server restarts. The reporter observed BatchV1_1 showing 33 validations and a threshold of 26 rather than 35 and 28. The error can push a vote either way, since dropping a “no” voter can grant majority early, though the reporter states that no current amendment outcome is affected. The issue remains open.
Institutional Markets: Ripple Prime Widens Its Mandate, Evernorth Approaches Nasdaq
On October 6, Ripple announced that Ripple Prime will provide funds managed by Brevan Howard with multi-asset prime brokerage, clearing and financing across traditional and digital markets. Brevan Howard manages about $35 billion. Ripple describes the service as a unified platform intended to improve capital efficiency and operational simplicity; for a macro fund, having brokerage, clearing and financing with one provider means positions across asset classes sit with a single counterparty rather than being split among several. Noel Kimmel, President of Ripple Prime, said there are “few firms equipped to provide the next generation of prime services that sophisticated investors expect.”
Evernorth Holdings, which aims to build what it calls “the world’s leading institutional XRP treasury,” filed a Form 8-K on October 6 saying an administrative delay had moved the expected closing of its business combination with Armada Acquisition Corp. II to on or about October 9. Trading of the combined company’s Class A shares on Nasdaq under the ticker XRPN is expected to begin on or about October 12. The filing does not state how much XRP the company holds.
In Brief
EU stablecoin deadline. On October 8, ESMA published an opinion stating that MiCA-authorised crypto-asset service providers should cease providing services related to non-MiCA-compliant stablecoins to clients in the EU. Firms must prevent clients from acquiring or increasing exposure to these tokens. Remaining exposures are to be remediated no later than three months after publication, with services limited in the meantime to liquidating, converting, withdrawing, transferring or safekeeping existing holdings.
Next amendment: fixCleanup3_4_0. The XRPL Dashboard shows this bundle of fixes from xrpld 3.4.0 holding majority, with expected activation on October 23 at 09:34 UTC if support stays above 80 percent. According to the 3.4.0 release notes of September 16, it includes changes such as blocking offers from receiving tokens from issuers that disallow incoming trust lines and preventing AMMClawback from burning LP tokens when MPT rounding floors the amount to zero. Its activation is also the condition the Permission Delegation documentation sets before the PaymentBurn permission should be delegated.
Lending and confidential transfers short of majority. As of October 11, the XRPL Dashboard shows SingleAssetVault at 21 of 35 trusted validators, and LendingProtocol, LendingProtocolV1_1 and ConfidentialTransfer at 19 of 35 each. Activation requires 29 of 35 for two weeks, so none has an expected date.
New York developer events. The XRPL.org events calendar lists the XRP Ledger Core Dev Bootcamp on October 20–22 and an XRPL Commons hackathon on October 24–25, both in New York. They lead into Swell 2026, Ripple’s annual conference, which runs October 27–29 at The Shed in Hudson Yards.
Sources
- XRPL.org — “Vulnerability Disclosure Report for xrpld 3.4.1,” October 9, 2026 — https://xrpl.org/blog/2026/vulnerabilitydisclosurereport-bug-20261009
- XRPLF/rippled on GitHub — “Release 3.4.1,” October 2026 — https://github.com/XRPLF/rippled/releases/tag/3.4.1
- XRPL Dashboard — “Amendments,” accessed October 11, 2026 — https://xrpldashboard.com/amendments
- XRPL.org — “Batch Transactions,” documentation, accessed October 11, 2026 — https://xrpl.org/docs/concepts/transactions/batch-transactions
- XRPL.org — “Permission Delegation,” documentation, accessed October 11, 2026 — https://xrpl.org/docs/concepts/accounts/permission-delegation
- XRPLF/rippled on GitHub — “Amendment voting drops validators that rotate their signing key from votes and threshold,” Issue #8534, October 8, 2026 — https://github.com/XRPLF/rippled/issues/8534
- Ripple — “Ripple Prime and Brevan Howard Expand Partnership,” October 6, 2026 — https://ripple.com/ripple-press/ripple-and-brevan-howard-deepen-relationship/
- Evernorth Holdings Inc. (SEC EDGAR) — “Form 8-K,” October 6, 2026 — https://www.sec.gov/Archives/edgar/data/0002092592/000119312526415577/d184020d8k.htm
- European Securities and Markets Authority — “ESMA sets out supervisory expectations on services related to unauthorised stablecoins,” October 8, 2026 — https://www.esma.europa.eu/press-news/esma-news/esma-sets-out-supervisory-expectations-services-related-unauthorised
- XRPL.org — “Introducing XRP Ledger version 3.4.0,” September 16, 2026 — https://xrpl.org/blog/2026/xrpld-3.4.0
- XRPL.org — “Events,” accessed October 11, 2026 — https://xrpl.org/community/events
- Ripple — “Swell 2026,” accessed October 11, 2026 — https://swell.ripple.com/
XRPL Canada is a non-profit community organization dedicated to growing the XRP Ledger ecosystem across Canada. Have a story we should cover? Reach us at team@xrplcanada.org or follow @XRPLCanada on X.