XRPL Developments Weekly Summary
November 2–8, 2026

TL;DR

A major cleanup week in rippled with 24 PRs merged to develop — highlighted by ~3,000 lines of dead code removal, a fixCleanup3_6_0 amendment placeholder, several bug fixes (UB in JSON/STData, config validation, RPC load charges, null-SLE guards), and a clean-exit-on-bad-config improvement for node operators. In xrpl.js, 5 PRs merged to main adding hex field validation across 46 transaction fields, fixing dropsToXrp precision loss (now returns BigNumber), and hardening non-UTF-8 and error handling. In xrpl4j, a binary parser decode bug was fixed (closes #805) and TrustLine flag test coverage was expanded. On the developer portal, 6 PRs merged including Python/Go Batch tutorial examples and a batch of error code corrections. In XRPL-Standards, XLS-0096 received a FAQ clarification on confidential balances and TransferFee.

Summary

This was a spring-cleaning week for the XRP Ledger's core server software (rippled), with 24 changes merged — the vast majority focused on removing unused code and fixing small but important bugs. Developers systematically deleted roughly 3,000 lines of code that nothing was using anymore: old debugging infrastructure, obsolete data structures, an entire external library that was no longer needed, and test files that had already been migrated to a newer testing framework. While deleting code may sound unexciting, it makes the codebase easier to understand, faster to compile, and reduces the surface area for future bugs. On the bug-fix side, several changes improve the experience for people running XRPL nodes: if you have a typo or duplicate entry in your server configuration file, the server will now print a clear error message and exit cleanly instead of crashing with a cryptic error. Two internal JSON-handling bugs involving "undefined behavior" (a category of subtle programming error that can cause unpredictable results) were also corrected.

For application developers, the JavaScript SDK (xrpl.js) received important improvements that will ship in the next npm release. The most significant is that 46 transaction fields — things like token IDs, vault IDs, and domain names — are now validated to ensure they contain valid hexadecimal strings before being sent to the network. Previously, any string was accepted, which could lead to confusing errors. The dropsToXrp() function, which converts the smallest XRP unit to full XRP, now returns a high-precision number type instead of a regular JavaScript number — this prevents rounding errors when dealing with very large amounts. The Java SDK (xrpl4j) fixed a bug in its binary decoder that was using the wrong formula to calculate field lengths, and exposed several follow-up issues in the same area that the maintainer is now tracking. None of these SDK changes are available to install yet — they're merged into the main development branch and will ship in the next tagged release.

On the documentation side, the developer portal corrected several error code names and numbers that didn't match what the actual server software returns — important for developers writing error-handling logic. Python and Go code examples were also added to the Batch transaction tutorials, so developers working in those languages can now follow along with working code.

For the latest updates, follow @XRPLF and @RippleXDev on X, and explore the XRPLF repos directly for full development activity.


What Merged

Note: All rippled changes below were merged to the develop branch and are not yet live on the network. A tagged release is required for any change to reach production.

Note: SDK PRs below were merged to each library's main branch. They become available to application developers only after a tagged release is published (npm for xrpl.js, Maven Central for xrpl4j, PyPI for xrpl-py). If no corresponding SDK release appears in the data, treat the feature as merged-but-pending-release and phrase availability accordingly.

Protocol & Feature Work (rippled — merged to develop)

Bug Fixes & Stability (rippled — merged to develop)

Refactoring & Architecture (rippled — merged to develop)

A wave of dead-code removal from @mvadari stripped approximately 3,000 lines:

CI & Docs (rippled — merged to develop)

Clio (API Server)

Developer Portal (xrpl-dev-portal)

XRPL-Standards

JavaScript SDK (xrpl.js — merged to main)

Java SDK (xrpl4j — merged to main)

Python SDK (xrpl-py — merged to main)


In Progress

rippled — Performance optimizations: Two PRs from @mvadari target transaction processing overhead:

rippled — Lending Protocol V1.2: Three PRs labeled feature: LP1.2:

rippled — Config error messages: rippled#8691 (+166/−56) — Stacked on the merged #8473, this makes the error message report the section name and rejected text instead of a bare std::bad_cast. Approved by 4 reviewers but has merge conflicts.

rippled — Remove date library dependency: rippled#8668 (+377/−154, 21 files) — Replaces Howard Hinnant's date library with C++20 facilities. Has outstanding review comments about potential overflow in clock conversions.

rippled — Validator keys in-tree: rippled#8223 (+6370/−317, 38 files) — Moves validator-keys from a separate repository into the rippled tree with external (HSM) signing and validator-list signing support. Very large PR with active review.

rippled — Batch DeliverMax fix: rippled#8558 (+430/−25) — Ensures the DeliverMax rule applies to inner Batch Payments and to simulate/submit. Approved by 5 reviewers; has merge conflicts.

xrpl4j — Unrecognized PermissionValue handling: xrpl4j#863 (+745/−76) — Deserializes unknown PermissionValue entries as UnknownPermission instead of throwing, which previously made entire transactions unparseable. Labeled breaking. Approved by 3 reviewers.

xrpl4j — Inverted NFTokenOffer buy/sell flags: xrpl4j#868 (+55/−18) — The lsfSellNFToken bit was bound to a constant named BUY_TOKEN, causing every NFTokenOffer read through xrpl4j to report the trade direction backwards. Approved.

xrpl.js — Review policy update: xrpl.js#3573 (+205/−2) — Lowers the review requirement on main from two human approvals to one, with a needs-second-reviewer label safeguard. Approved.

xrpl-dev-portal — Amendments page: xrpl-dev-portal#4044 (+3190/−3, 15 files) — Proposes an xrpl.org/amendments dashboard with per-feature cards, side panels with key dates and audit links, and live vote counts.

xrpl-dev-portal — Ruby SDK and examples: xrpl-dev-portal#3837 (+358/−3) — Adds Ruby tutorials and code samples, approved by @xVet from the Foundation side.

opensource.ripple.com — Lending Protocol 1.2 docs: opensource.ripple.com#243 (+750/−0, 12 files) — Draft documentation for LP1.2 features. Marked "Do not merge — features not finalized."


What to Watch Next Week


Community & Discussions

Community contributors active across repos this week: @nabe3m contributed four documentation accuracy fixes to the developer portal (error code names and numeric values) plus the permission delegation status update. @hmalinski fixed the Json::Value::asBool() UB in rippled and opened SDK fixes for xrpl.js (OracleSet Scale limit) and xrpl-py (UInt64 decode round-trip). @FawwazLawal's xrpl4j VL decode fix (opened last week) merged with companion tests from maintainer @sappenin. @SAY-5 contributed the null-SLE guards in rippled. @BraedonKlock's noripple_check load-type fix and @shortthefomo's simulate RPC charge fix — both long-standing community PRs — also merged this week. @jarrensj contributed the CLAUDE.md symlink cleanup, and @Krypto-Whitehat fixed the ceilOut template typo.

Clio bug reports: @mvadari filed five bugs (#3289–#3293) after systematically diffing Clio 2.8.0 against rippled 3.4.1 — covering error code mismatches, response field differences, HTTP vs HTTPS in urlgravatar, boolean singleton handling in ledger_entry, and stale data on one altnet node.

xrpl4j follow-up issues: @sappenin filed six issues (#862–#873) exposing pre-existing weaknesses in BinaryParser/BinarySerializer VL prefix handling — including asymmetric encode/decode bounds, truncated input handling, and Error vs IllegalArgumentException throw types. @hmalinski has volunteered to take items 1 and 2.

Standards discussions: @donovanhide proposed a Canonical Transaction Ordering amendment replacing XOR in CanonicalTXSet::accountKey with SipHash-2-4 to prevent prefix-grinding exploits (XRPL-Standards#679). @LeDenti raised a question about XLS-85 (Token Escrow) and whether EscrowFinish by a third party should create the destination trustline (XRPL-Standards#677) — @mvadari responded that this would conflict with the design intent of trustlines requiring active user consent.

New rippled issues: A question was raised about whether the VaultDeposit cap should apply when a vault is already over AssetsMaximum (rippled#8700). A Good First Issue was filed for deferring transaction serialization in ApplyStateTable::apply until it's actually written (rippled#8671).


By the Numbers

Compared to last week (October 26 – November 1, 2026):

MetricThis WeekLast WeekChange
Repos with activity88flat
rippled PRs merged242↑22
rippled PRs opened2226↓4
rippled new issues43↑1
rippled closed issues51↑4
rippled releases00flat
rippled commits232↑21
xrpl.js PRs merged53↑2
xrpl.js PRs opened176↑11
xrpl.js new issues42↑2
xrpl.js closed issues11flat
xrpl.js releases12↓1
xrpl.js commits53↑2
xrpl-py PRs merged10↑1
xrpl-py PRs opened57↓2
xrpl-py new issues01↓1
xrpl-py releases00flat
xrpl-py commits10↑1
xrpl-dev-portal PRs merged623↓17
xrpl-dev-portal PRs opened139↑4
xrpl-dev-portal new issues22flat
xrpl-dev-portal commits625↓19
Clio PRs merged22flat
Clio PRs opened31↑2
Clio new issues70↑7
Clio releases11flat
Clio commits22flat
XRPL-Standards PRs merged32↑1
XRPL-Standards PRs opened54↑1
XRPL-Standards commits32↑1
xrpl4j PRs merged40↑4
xrpl4j PRs opened84↑4
xrpl4j new issues80↑8
xrpl4j closed issues30↑3
xrpl4j releases00flat
xrpl4j commits40↑4
Total PRs merged (all repos)4532↑13
Total releases33flat

Carryovers from last week: Several items noted as "In Progress" last week merged this week: the ApplyContext refactor (rippled#8637), the TaggedPointer assertion (rippled#8661), the dropsToXrp BigNumber fix (xrpl.js#3341), the xrpl4j VL decode fix (xrpl4j#858), and the Batch tutorial expansion (xrpl-dev-portal#4038).

Trends: rippled merges surged from 2 to 24 — last week's wave of 26 opened PRs (robustness and cleanup work) began landing in earnest. The dev portal slowed from 23 merges to 6 after last week's dependency security patch blitz. xrpl4j saw a burst of activity with 4 merges, 8 new PRs opened, and 8 new issues filed — mostly follow-ups from the VL decode bug fix exposing pre-existing weaknesses. Clio saw 7 new bug reports filed (5 from systematic rippled-vs-Clio diffing), signaling a quality alignment effort.

Generated on November 8, 2026 at 05:50 AM UTC using claude-opus-4-6