XRPKuwait

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

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

@Vet_X0 @uptownsaul We take both token price and network capacity into consideration when making reserve changes, but our primary focus is always on the network itself For instance, when the XRP price reached $3 and we lowered the base reserve from 10 to 1 XRP and the owner reserve from 2 to 0.2 XRP, we observed a significant increase in transactions and new accounts. During that period, we closely monitored how the network handled this additional traffic through validation, and it performed very well Based on these observations, this is why we are currently voting in favor of lowering the reserves

@XRPKuwait do you make the reserve changes, in your case lowering, based on token price or network capacity?

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

@Kirjakulov 🤝

@XRPKuwait Welcome to the club. :)

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/ripp…

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: #bug-bounties-and-responsible-disclosures" target="_blank" rel="nofollow noopener">xrpl.org/blog/2025/ripp…

@_tequ_ Well deserved! Big congratulations

It's an honor to be included in the list provided by the XRPL Foundation!

@Vet_X0 Appreciate it, XRPK wouldn’t have come online without your support 🙏

@XRPKuwait Thank you for your participation. It's great to serve among giants like yourself.

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/… 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/ripp…

@uptownsaul 🤫

SWIFT is inside us

@uptownsaul We appreciate you Saul 🙏❤️

Wanted to give another shout out to @XRPKuwait 👏 -Self-funded XRPL infrastructure provider running 5 (!) hubs with almost 700 total peers -Brings intimate knowledge from IRL professional life about how money moves around the world -Located in Kuwait City, adds geographic decentralization xrpkuwait.com/xrpkhubs

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

@ekiserrepe 🤣🤣🤣🤣

Reminder: Update your XRPL validator/node to rippled 2.5.0.

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/ripp… 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.

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