A steady week of cleanup and performance work across the ecosystem. In rippled, 14 PRs merged to develop — highlighted by two performance wins eliminating redundant STTx parsing/copying during transaction relay, a Batch preflight allocation optimization, a database write failure recovery fix, and continued dead-code removal. In xrpl.js, 3 PRs merged to main including a revert that keeps main releasable as 5.x by deferring the breaking BigNumber change to a dedicated 6.0.0 branch. In xrpl4j, 4 PRs merged to main including a breaking change scoping Jackson ObjectMapperFactory behaviors to xrpl4j types only. On the developer portal, 7 PRs merged adding the fixBatchV1_2 amendment to Known Amendments, publishing the Testnet/Devnet reset blog post, clarifying LoanPay docs, and fixing several error codes. In Clio, a fix merged making the ETL publisher stoppable to prevent shutdown hangs.
This week's work on the XRP Ledger focused on making the core server faster and cleaner, while the client libraries and documentation continued to mature. In the server software (rippled), developers eliminated unnecessary work during transaction processing — when a node relays a transaction to its peers, it was previously parsing the transaction data from scratch even though it had already parsed it moments earlier. Two changes fixed this by passing along the already-parsed transaction instead. Another optimization removed heap memory allocations from a frequently-run validation check for Batch transactions, replacing them with pre-sized inline storage. A separate fix addressed a scenario where, if the database failed while saving a validated ledger, the server would incorrectly skip retrying that save — now the save state is properly reset so recovery can proceed.
For the JavaScript library (xrpl.js), the team made an important decision about release strategy. A recent change that would have altered how XRP amounts are returned (using a high-precision number type instead of a regular JavaScript number) was moved off the main development branch onto a separate branch for version 6.0.0. This means the next release from the main branch can ship as a non-breaking 5.4.0 update, giving developers time to prepare for the bigger change. The Java library (xrpl4j) made a breaking improvement to how its JSON configuration works — previously, its settings could accidentally affect other parts of a Java application that share the same JSON processing machinery, and now those settings only apply to XRPL-specific types. On the documentation side, the developer portal published an important announcement: both the Testnet and Devnet test networks will be reset on November 25, deleting all accounts, balances, and other data. Developers who rely on these networks should plan to re-create their test data from the faucet afterward.
For the latest updates, follow @XRPLF and @RippleXDev on X, and see the Testnet/Devnet reset announcement for details on the upcoming reset.
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.
std::unordered_set/std::unordered_map containers in Batch::preflight with std::flat_sets backed by inline small_vector storage. Since preflight runs for every submitted and relayed Batch (XLS-56) transaction, this eliminates per-insertion heap allocations from a hot path.saveValidatedLedger(), the pending-saves entry and SAVED flag are now cleared so the next save attempt proceeds as a first attempt rather than being skipped. Synchronous callers waiting on that ledger sequence also wake up correctly.Database::asyncFetch() now completes reads immediately with no object when the queue is closed, and Database::stop() drains all queued reads after releasing the lock. This prevents shutdown hangs caused by callbacks that never fire.log_level RPC parameters: rippled#7595 (+38/−0) — The log_level admin RPC called asString() on severity and partition without checking their JSON type. Non-string values (e.g. {"severity": 5}) could throw or return an internal error. Now returns rpcINVALID_PARAMS for invalid types. Contributed by community member @harshitgupta62.STTx during transaction relay: rippled#8593 (+133/−5) — Adds an Overlay::relay overload that accepts the already-parsed STTx. Both NetworkOPs and OpenLedger now use it, eliminating a redundant full parse (template application, sha512Half, batch build) on every relayed transaction.STTx in NetworkOPs: rippled#8582 (+2/−2) — Two sites in NetworkOPsImp deep-copied an STTx via auto const sttx = *transaction->getSTransaction() when they only needed to read it. Changed to auto const& to bind to the shared pointer's target.TMTransaction.receiveTimestamp and deprecate it: rippled#8702 (+2/−9) — The receiveTimestamp field was added in 2011 so relaying nodes could annotate transactions with their clock. Every sender has set it from its own clock since 2012, and no receiver reads it. The field is now deprecated in the protobuf definition, and no code populates it.results.h and Output.h, following up on the dead-code wave from the previous week.pubProposedAccountTransaction declared an accountHistoryNotify vector, never inserted into it, and then tested and iterated it. Removed.json::Value accepts std::string_view: rippled#8486 (+175/−3) — Adds a constructor and operator== so callers holding a string_view no longer need to materialize a std::string just to construct or compare a JSON value.docker/login-action 4.7.0 → 4.8.0: rippled#8706 (+2/−2) — Dependabot CI dependency update.SECURITY.md scope: rippled#8714 (+1/−1)Publisher was not stopped on ETL shutdown. Also adds a 5-minute timeout for publisher retries — if the database is stuck on an older sequence, Clio will now crash by assertion instead of hanging indefinitely. Closes clio#2833.SECURITY.md: clio#3300 (+27/−0)fixBatchV1_2 to Known Amendments and link disclosure reports: xrpl-dev-portal#4056 (+24/−9) — Documents the fixBatchV1_2 amendment (enabled on Mainnet 2026-10-09) and links vulnerability disclosure reports from Batch (XLS-56), fixBatchInnerSigs, PermissionDelegation (XLS-75), PermissionDelegationV1_1, and Sponsor (XLS-68).SignerListSet error code: xrpl-dev-portal#4059 (+4/−4) — Corrects the documented result code for an unreachable SignerQuorum from temMALFORMED to temBAD_QUORUM, matching the actual rippled behavior.PaymentBurn delegation warning: xrpl-dev-portal#4053 (+1/−11) — The fixCleanup3_4_0 amendment was enabled on Mainnet on 2026-11-04, so the warning about not delegating PaymentBurn until that amendment is enabled no longer applies.tecNO_PERMISSION typo in LoanBrokerDelete: xrpl-dev-portal#4058 (+1/−1)markdown requirement to ≥3.11.3.dropsToXrp() BigNumber change to keep main releasable as 5.x: xrpl.js#3587 (+89/−159) — The breaking change from #3341 (returning BigNumber instead of number) is not dropped — it moves to the xrpl-6.0.0 branch. This lets main ship a non-breaking 5.4.0 release first. Merged — pending npm release.CONTRIBUTING.md and RELEASE.md: breaking changes now target a dedicated major-version branch, not main. Merged — pending npm release.ObjectMapperFactory behaviors to xrpl4j types only (breaking): xrpl4j#850 (+556/−32) — Previously, five Jackson configuration settings applied mapper-wide to every type, including consumer-owned types. A new Xrpl4jAnnotationIntrospector now limits these behaviors to xrpl4j classes, so applications sharing an object graph no longer have their serialization silently altered. Closes xrpl4j#671. Merged — pending Maven Central release.serializationInclusion in BinaryCodecObjectMapperFactory: xrpl4j#851 (+53/−1) — Replaces the one deprecated MapperBuilder method in Jackson 2.21 with its non-deprecated equivalent and pins the configuration with a test. Merged — pending release.macos-15: xrpl4j#879 (+1/−1) — GitHub retired the macos-14 runner image; the darwin-aarch64 integration test leg now runs on macos-15.SECURITY.md: xrpl-py#1079 (+27/−0)rippled — DER parsing removal and libsecp256k1 reliance: rippled#8710 (+1,382/−1,346) — Removes the hand-written ECDSA signature pre-parser, relies on libsecp256k1 for strict DER parsing and low-S detection, and randomizes the process-wide libsecp256k1 context against side-channel leakage. Approved by @JoelKatz; has outstanding Copilot review comments about a diagnostic message and alignment.
rippled — Vault value-conservation invariant: rippled#8719 (+923/−18) — Under fixCleanup3_6_0, adds an object-level invariant requiring AssetsAvailable changes to match the vault pseudo-account's balance changes. Reviewed by @exocognosis who confirmed the three key cases are covered.
rippled — Vault share rounding in vault's favor: rippled#8708 (+1,136/−30) — Under fixCleanup3_6_0, deposits round shares down / assets up, and withdrawals round the opposite way, preventing shareholder dilution. Community contribution by @muhammadsalah; reviewed positively by @hmalinski. Awaiting maintainer review.
rippled — Loan payment precision bound: rippled#8727 (+1,171/−15) — Under LendingProtocolV1_2, bounds loan payment size to the loan scale. Approved by core reviewer.
rippled — Fuzz targets for the serializer: rippled#8713 (+675/−0) — Adds libFuzzer infrastructure and two initial targets (serial_iter and another). Approved by 2 reviewers, but placed on hold pending serializer refactoring work.
rippled — JSON-RPC version constants: rippled#8487 (+243/−288) — Declares ripplerpc and jsonrpc version literals in one place. Approved by 4 reviewers.
xrpl4j — Inverted NFTokenOffer buy/sell flags: xrpl4j#868 (+109/−21) — The lsfSellNFToken bit was bound to BUY_TOKEN, reporting every NFTokenOffer's trade direction backwards. Approved by 3 reviewers. Merged — pending release.
xrpl4j — Unrecognized PermissionValue handling (breaking): xrpl4j#863 (+745/−76) — Deserializes unknown PermissionValue entries as UnknownPermission instead of throwing, which previously made entire transactions unparseable. Approved by 2 reviewers.
xrpl4j — VL boundary constants and 3-byte length rejection: xrpl4j#874 (+162/−26) — Consolidates variable-length prefix constants and rejects 3-byte lengths above 918,744. Approved by maintainer @sappenin; needs re-approval after rebase.
xrpl4j — UnsignedByte defensive copy (bug fix): xrpl4j#857 (+337/−23) — Fixes a bug where destroy() on one array could mutate shared static key-prefix constants process-wide. Approved.
xrpl-dev-portal — Get Started tutorial rewrites: Three PRs converting Go (#4061), Java (#4062), and PHP (#4063) tutorials to an interactive walkthrough format with latest SDK versions. Combined +2,721/−1,275.
xrpl-dev-portal — Redocly framework migration: xrpl-dev-portal#4065 (+2,152/−4,848) — Replaces @redocly/realm with @redocly/framework 1.0.0. Marked do-not-merge pending comparison.
xrpl.js — Q4 batch dependency upgrade: xrpl.js#3590 (+2,448/−2,520) — Supersedes 25 Dependabot PRs. Has outstanding review changes requested.
Clio — Prevent crash on malformed DosGuard params: clio#3301 (+3/−7) — Community contribution by @0xUnd3adBeef fixing an unauthenticated crash vector in the ng web server where malformed params hit an ASSERT that calls std::exit().
UnsignedByte defensive copy (#857), unrecognized PermissionValue handling (#863), VL boundary constants (#874), and the breaking ObjectMapperFactory scoping (#850) — are all merged to main. Watch for a v7.0.0 tagged release that ships these to Maven Central.fixCleanup3_6_0 vault invariant and rounding PRs: Two substantial PRs (#8719 and #8708) would strengthen vault value conservation and prevent shareholder dilution — both gated on the fixCleanup3_6_0 amendment that was placeholder-landed last week. Active review from domain experts.Community contributors: @harshitgupta62's log_level type validation fix (rippled#7595) merged after persistent follow-up across multiple review cycles — a good example of a community contributor seeing a fix through to completion. @muhammadsalah reopened the vault share rounding fix (rippled#8708), which supersedes a prior closed PR, and received positive technical feedback from @hmalinski. @0xUnd3adBeef submitted a Clio crash fix (clio#3301) with a reproduction repo. @quantova-inc contributed a comment correction in rippled (#8728), an AMMDeposit overflow fix (#8717), an MPT validation fix for xrpl.js (#3584), and known-answer signing tests across xrpl.js, xrpl-py, and xrpl4j. @SoubeDev submitted a Batch flags interface fix for xrpl.js (#3588). @FawwazLawal contributed fixes across repos: moving generateBlindingFactor() to test utilities in rippled (#8644), fixing f-string prefixes in xrpl-py (#1082), and improving error handling in xrpl4j (#881).
Standards: @quantova-inc submitted a draft XLS for "Qstamp Post Quantum Evidence Anchor Memo" (XRPL-Standards#665), an Ecosystem spec for anchoring post-quantum evidence records on the ledger. @mvadari noted that Ecosystem XLS specs require demonstrated ecosystem consensus — the author has been directed to gather builder support.
Clio issues: The ETL publisher stoppability fix (clio#3295) was prompted by a production hang reported by @coovxrp on clio#2833 where the fallback-recovery timer interacted badly with a long-running ledger.
New rippled issue: @nabe3m reported that CredentialCreate returns temMALFORMED instead of temINVALID_ACCOUNT_ID for a zero-account Subject, inconsistent with sibling Credentials transactions (rippled#8715). A corresponding docs issue was also filed on xrpl-dev-portal (#4067).
Compared to last week (November 2–8, 2026):
| Metric | This Week | Last Week | Change |
| Repos with activity | 7 | 8 | ↓1 |
| rippled PRs merged | 14 | 24 | ↓10 |
| rippled PRs opened | 18 | 22 | ↓4 |
| rippled new issues | 1 | 4 | ↓3 |
| rippled closed issues | 0 | 5 | ↓5 |
| rippled releases | 0 | 0 | flat |
| rippled commits | 14 | 23 | ↓9 |
| xrpl.js PRs merged | 3 | 5 | ↓2 |
| xrpl.js PRs opened | 15 | 17 | ↓2 |
| xrpl.js new issues | 0 | 4 | ↓4 |
| xrpl.js closed issues | 0 | 1 | ↓1 |
| xrpl.js releases | 1 | 1 | flat |
| xrpl.js commits | 3 | 5 | ↓2 |
| xrpl-py PRs merged | 2 | 1 | ↑1 |
| xrpl-py PRs opened | 3 | 5 | ↓2 |
| xrpl-py new issues | 0 | 0 | flat |
| xrpl-py releases | 0 | 0 | flat |
| xrpl-py commits | 2 | 1 | ↑1 |
| xrpl-dev-portal PRs merged | 7 | 6 | ↑1 |
| xrpl-dev-portal PRs opened | 9 | 13 | ↓4 |
| xrpl-dev-portal new issues | 2 | 2 | flat |
| xrpl-dev-portal commits | 11 | 6 | ↑5 |
| Clio PRs merged | 2 | 2 | flat |
| Clio PRs opened | 4 | 3 | ↑1 |
| Clio new issues | 2 | 7 | ↓5 |
| Clio closed issues | 1 | 0 | ↑1 |
| Clio releases | 1 | 1 | flat |
| Clio commits | 2 | 2 | flat |
| XRPL-Standards PRs merged | 1 | 3 | ↓2 |
| XRPL-Standards PRs opened | 1 | 5 | ↓4 |
| XRPL-Standards commits | 1 | 3 | ↓2 |
| xrpl4j PRs merged | 4 | 4 | flat |
| xrpl4j PRs opened | 11 | 8 | ↑3 |
| xrpl4j new issues | 2 | 8 | ↓6 |
| xrpl4j closed issues | 2 | 3 | ↓1 |
| xrpl4j releases | 0 | 0 | flat |
| xrpl4j commits | 4 | 4 | flat |
| Total PRs merged (all repos) | 33 | 45 | ↓12 |
| Total releases | 3 | 3 | flat |
Carryovers from last week: Several items noted as "In Progress" last week merged this week: the xrpl4j inverted NFTokenOffer flags fix (xrpl4j#868) and the unrecognized PermissionValue handling (xrpl4j#863) both merged to main (pending release). The xrpl.js review policy update (xrpl.js#3573) remains open. The Lending Protocol V1.2 PRs from last week continue in active review with a new addition (#8727).
Trends: rippled merges dropped from 24 to 14, normalizing after last week's surge of cleanup PRs. The dev portal held steady at 7 merges. xrpl4j maintained its 4-merge pace with heavy open PR activity (11 opened). Community contributions remained strong — external contributors submitted PRs across all major repos. The xrpl.js release (5.4.0-smartcontract.0) is a pre-release tag, not a production release.