For out of the ground we were taken, for the XRPL we are, and to the XRPL we shall return.

"3 to 5 business days..😂" @swiftcommunity #XRPL #XRP

The XRPL amendment BatchV1_1 has reached majority votes and has now entered the activation phase. BatchV1_1 introduces Atomic Batch Transactions (XLS-56) to the XRP Ledger. ⏳ Time remaining until activation: 13d 23h.. xrpl.org/resources/known-ame… #XRPL #XRP #XLS56

XRPK Phase 2 A major step forward, bringing more of the network, infrastructure, and tooling together in one place. • Full XRPK Network View • In-depth peering & connectivity statistics • Automated Peer Reservations & Removal (APR) • XRPK Ledger Explorer • Live ledger & network metrics • Improved XRPK infrastructure visibility • Redesigned interface built around real-time data • A clearer view into the XRPL network from the XRPK perspective This is more than a new look. It’s a major expansion of what XRPK provides and what node operators can do directly through the platform. xrpkuwait.com #XRPL #XRP

Introducing XRPK Hubs Map Beta xrpkuwait.com/xrpkhubs-visua… A real-time visual representation of peer activity across the XRPK Hubs infrastructure. Monitor connections across all 5 hubs, inbound/outbound peers, server states, latency and peer details - live. #XRPL #XRP

XRP Ledger 3.2.1 is now available. This fixes the manifest flood observed on Friday, July 31. The XRPL continued closing ledgers normally throughout. A post-mortem will follow soon for the community. Nodes previously accepted, stored and re-broadcast an unlimited number of manifests from unknown validator keys. 3.2.1 adds four limits: 1) Size cap per manifest - any single manifest larger than expected is rejected. 2) Receive cap - incoming batches over the limit are discarded, instead of breaking the peer connection. 3) Send cap - the bulk manifest greeting sent to each new peer is now bounded. 4) Cache cap - once 100 unknown keys are held, new ones are refused. We also no longer persist manifests from unknown keys to disk, so a flood cannot survive a restart. Please update immediately by following these steps: 1) Update normally to XRPL 3.2.1 2) Wait 1–2 min, confirm xrpld is running, it does not need to be in status full or proposing. 3) Restart xrpld again - very important.

xrpld: THE MIGRATION The XRP Ledger is migrating from rippled to xrpld. xrpld v3.2.0 introduces the fixCleanup3_2_0 amendment, along with various improvements and fixes. All validators and node operators are encouraged to migrate to xrpld v3.2.0 and review their infrastructure to ensure a smooth transition. Release Notes: xrpl.org/blog/2026/xrpld-3.2… Migration Script by @Vet_X0 github.com/xVet/migrate-ripp… According to data from @XRPScan and @Bithomp, approximately 18% of nodes are currently running xrpld v3.2.0. We appreciate the efforts of all operators participating in this important network transition. #xrpl #xrpld

XRPK Validator vote is now in effect after upgrading to v3.1.0

XRPK Validator will be voting to lower account and object reserves. The network handled recent transaction spikes well, and we believe these changes better reflect current market conditions. Changes take effect on the next validator restart. Updated vote: Account reserve: 0.1 XRP → 100,000 drops Object reserve: 0.01 XRP → 10,000 drops

Rippled v3.0.0 has officially been released, introducing five new amendments: • fixAMMClawbackRounding • fixIncludeKeyletFields • fixMPTDeliveredAmount • fixPriceOracleOrder • fixTokenEscrowV1 XRPK infrastructure is now running on the latest rippled v3.0.0 We urge all node operators to update promptly to avoid amendment block. #XRPL #XRPCommunity Release notes: xrpl.org/blog/2025/rippled-3…

rippled 2.6.2 has been officially released. This version introduces the new fixDirectoryLimit amendment and includes a critical bug fix. All node operators are advised to upgrade to v2.6.2 immediately to maintain stable operations. XRPK servers are now running on v2.6.2, alongside 194 other nodes. Source: @xrpscan Release notes: xrpl.org/blog/2025/rippled-2…

The CenturyLedger #XRPLedger Congratulations to the #XRPL on reaching 100 million ledgers. XRPK is honored to be part of this historic accomplishment, and we extend our best wishes for the continued growth and success of the network.

🔔Reminder for node operators A scheduled dUNL migration will take place on September 30, 2025. Nodes must switch to the new settings to continue retrieving the XRPL Foundation’s validator list. The previous UNL will reach full deprecation on January 18, 2026. Configuration Guidance: github.com/XRPLF/rippled/dis… Source: @XRPLF #XRPLedger #XRPL

The dUNL migration to the new XRP Ledger Foundation is in full motion. What does this mean for Validators and Nodes? 👉 Update your config by September 30th 2025 to keep using our list. Check the guide below to see if you need to change:

Recently, #XRPLedger contributors released rippled 2.6.0. Soon after launch, @offledger deployed a validator and performed extensive real-world testing on this release. During testing, @offledger identified issues with increased RAM usage on servers running 2.6.0 (a memory leak that could cause servers to crash). This discovery was crucial, as it helped prevent potential performance problems across the network. After discussions with contributors, a hotfix release (2.5.1) was published. This is currently the stable version to run. Importantly, there are no amendments to vote on in this release. We strongly urge all node operators to upgrade to 2.5.1 for stability and smooth performance. Once again, huge thanks to @offledger and to all contributors for their dedication. All XRPK infrastructure is running on 2.5.1 alongside 189 nodes. Source: @bithomp @xrpscan 2.5.1 release notes: xrpl.org/blog/2025/rippled-2…

rippled 2.6.0 has been released! XRPK infrastructure is already running on it, with 271 nodes (25% of the network) upgraded. This update has no amendments to vote on. Huge thanks to all contributors, and we urge all node operators to upgrade. Source: @xrpscan @bithomp #XRPLedger #XRPCommunity #XRP

Rippled v2.5.0 is officially released with key new amendments: 🔵 TokenEscrow 🔵 Batch 🔵 PermissionedDEX 🔵 PermissionDelegation 🔵 AMMv1_3 🔵 EnforceNFTokenTrustlineV2 🔵 PayChanCancelAfter As of now, 354 nodes have upgraded to rippled v2.5.0, representing approximately 35% of the network. We encourage all remaining operators to upgrade as soon as possible to ensure service continuity. xrpl.org/blog/2025/rippled-2… source: @xrpscan @bithomp #XRPL

The compromised xrpl.js NPM package does not affect @XamanWallet. Xaman uses in-house infrastructure and libraries developed by @XRPLLabs. We do not rely on third-party libraries like xrpl.js to handle private keys or transactions. Xaman users are not affected.

RT @alloynetworks: This is verified. The latest version of the npm package is compromised. Roll back if you’re on the latest. Immediately!

Be aware. Make sure your project is not using latest npm version, as it will compromise all accounts created with the library

We're now running on rippled v2.4.0 New amendments: ⚫️PermissionedDomains ⚫️DeepFreeze ⚫️DynamicNFT ⚫️fixFrozenLPTokenTransfer ⚫️fixInvalidTxFlags We are currently reviewing the amendments and will be casting our vote soon. #XRPL