A technical dispute has emerged in the XRP Ledger (XRPL) community over a plan to expand the capacity of its transaction memo field from 1KB to about 1.3MB. Supporters of allowing large data such as images and PDFs, as well as music, video and software source code to be stored directly on the XRP Ledger have faced objections that it could place an excessive burden on the network.

On Aug. 9, U.Today, a blockchain outlet, reported that the proposal centres on sharply raising the limit of the XRPL transaction memo field. It aims to allow far more data to be included in transactions, expanding the XRP Ledger's use from payments to various types of content storage.

Vet, a figure at the XRPL Foundation who is involved in the proposal, said the protocol should provide an option to allow it if users are willing to bear additional storage costs. With an expanded memo field, users would be able to embed images, documents, music, short videos, source code and compressed files directly in transaction data.

Some view it as a new use case for the XRP Ledger. They expect network usage could rise sharply if it can record content and data on-chain beyond simple payments and asset transfers.

But Matt Hamilton (맷 해밀턴), a former developer relations lead at Ripple, strongly criticised the plan. He called the proposal a "really bad idea" and said it does not fit the XRP Ledger's original purpose.

The core issue is the data storage structure. XRP Ledger validators and nodes must store and synchronise the network's transaction history. If large image or video files are continually added to transaction data, the size of the overall ledger could grow rapidly.

Hamilton said if users start continually storing large files on the ledger, all nodes would face the burden of keeping that data over the long term. If higher storage capacity and hardware performance are needed to run nodes, the barrier to entry for independent network participants could also rise.

That has led to concerns it could also affect the XRP Ledger's decentralisation. As node operating costs rise, individuals and small operators could find it harder to participate in the network, potentially reducing the diversity of validators and nodes.

Hamilton suggested an alternative of using decentralised storage networks such as Filecoin rather than storing large content on the blockchain itself. Under that approach, the XRP Ledger would record only references or link information, while the large files would be managed on a separate storage network.

He argued that such a hybrid structure is a way to use large content while keeping the XRP Ledger fast and light as a payment ledger. He said it is efficient for the blockchain to focus on payments and asset transfers, and to leave large data storage to a separate network designed for that purpose.

The debate can be seen as a clash of design philosophies over how far to expand the XRP Ledger's scope of use. Views that favour putting more data on-chain to increase utility are at odds with views that prioritise keeping the network lightweight and decentralised.

Future discussions are expected to focus on whether the memo field expansion will lead to an actual protocol change, and how to minimise node operating costs and the potential erosion of decentralisation that could come with expanded data storage features.