What the proposal changes
The Memo field is a small data slot attached to transactions on the XRP Ledger. Right now it caps out at 1 KB — enough for a short note, a reference, or a hash pointing elsewhere. The proposal would raise that ceiling to about 1.3 MB, a jump of more than a thousandfold. That's room for documents, images, or other sizable files to be written into the ledger itself rather than pointed to from off-chain storage.
For users, the appeal is straightforward. Instead of storing a hash or a link and hoping the underlying service stays alive, they could embed the actual content in a transaction. The data would live on the ledger, replicated across the network, as long as the ledger exists.
The decentralization warning
The former Ripple engineer's concern is about what bigger files do to the network's structure. Running a node on the XRP Ledger means validating and storing transaction history. If every transaction can carry 1.3 MB of data, the storage burden on operators climbs sharply. That could push smaller operators out, leaving the network in the hands of a few well-resourced players.
The engineer's warning frames the proposal as a trade-off: more utility on one side, a heavier load on the other. The ledger's appeal has always been its speed and low cost, and both depend on keeping the system light enough for a broad set of participants to run it. A network that only a handful of operators can afford to run stops being decentralized in any meaningful sense.
The warning lands at a sensitive moment for the network. Decentralization is the selling point that separates the XRP Ledger from a conventional database, and any change that concentrates power in fewer hands cuts against that pitch. The engineer's point isn't that bigger files are useless — it's that the price of storing them may be paid by the network's structure.
The trade-off at the heart of the debate
The proposal isn't just a technical tweak. It's a question about what the XRP Ledger is for. A 1 KB limit keeps the ledger lean and fast. A 1.3 MB limit turns it into something closer to a storage layer, with all the costs that come with it.
There's also the question of who pays. Larger files mean larger transactions, and while the
