- RippleX drafts propose optimized accounts and trustlines, metering storage usage precisely to reduce reserves and idle ledger overhead.
- Trustlines comprise roughly thirty percent of ledger data; proposed changes could shrink total size by six percent overall.
RippleX is preparing a set of amendments aimed at making the XRP Ledger (XRPL) faster to run, cheaper to store, and safer to use. Software engineer Mayukha Vadari said draft specifications will roll out in the coming weeks, prompting early discussion among developers and validators.
The first track targets account design and reserve math. An “Optimized accounts and trustlines” proposal would charge users only for resources they actually consume, without toggling between “lite” and “full” accounts or introducing extra flags. In plain terms, the ledger would meter storage more precisely, lowering idle overhead.
Over the past few weeks, I've realized that a number of specs sitting in my drafts may actually be useful for discussion. So over the next few weeks I'll be publishing them as Ideas (I don't quite have the time to polish them).
Here's the first of those: https://t.co/gn0mq2uZPI— Mayukha Vadari (@msvadari) September 11, 2025
Trustlines sit at the center of the storage debate. Vadari estimated that trustlines account for roughly 30% of ledger data. Cutting over 200 MB from more than six million trustlines would reduce total ledger size by about 6%—roughly 20% of trustline storage. However, validators cautioned that savings must be weighed against operational complexity.
Meanwhile, the community is weighing Multi-Purpose Tokens (MPTs). Some asked whether MPTs will replace trustlines. Vadari said it is too early to conclude, as MPTs are not live and still need full feature integration. Still, many see MPTs as a path to leaner token issuance and transfer.
Security hardening arrives on a parallel track. A new “Credentials” amendment enables on-chain issuance and verification of items like KYC and AML attestations tied to decentralized identities. Additionally, the proposed XLS-86 “Firewall” would let users set protective rules that can limit damage if a private key is compromised—turning a worst-case event into a contained incident.
Taken together, the drafts aim to tighten XRPL’s operational footprint while adding guardrails for identity and asset protection. If finalized and adopted, these changes would give issuers, exchanges, and payment firms clearer cost controls and a sturdier base for production workflows—one brick at a time.
