Ripple CTO Emeritus Responds to XRP Wallet Fee Backlash On Xaman Fees Row

TLDR

Table of Contents

David Schwartz replied “What did I do?” amid Xaman Wallet fee criticism.
A screenshot showed a 659 XRP service fee on XRPL DEX.
Xaman cited a user-created nested multisig that froze funds.
An XLS-103d amendment proposal awaits validator voting.

A brief remark from Ripple CTO Emeritus David Schwartz has drawn wide attention across the XRP community. His response, “What did I do?”, came as users voiced anger over Xaman Wallet fees and a disputed nested multisig setup on the XRP Ledger.

The debate centers on wallet service charges and a technical configuration under XLS-103d. While Ripple is not responsible for third-party wallets, Schwartz was tagged in online criticism. His reply placed focus on who controls fees and protocol changes within the XRP ecosystem.

Ripple CTO Emeritus Responds to Wallet Fee Backlash

Tension rose in the XRP community after reports of high wallet service fees linked to Xaman Wallet. Some users claimed small transactions carried charges higher than expected on the XRP Ledger.

A screenshot shared online showed a 659 XRP service fee. This amount was far above the XRPL base fee of 0.000012 XRP. The image spread quickly across social media platforms.

David Schwartz, known as JoelKatz, was tagged in several posts. He responded with a short message, asking, “What did I do?” His comment signaled distance from third-party wallet operations.

Schwartz does not manage Xaman Wallet or its pricing structure. Ripple develops software for the XRP Ledger but does not control independent wallet providers. His reply aimed to clarify that distinction.

Xaman Wallet Fees and User Complaints

Critics argued that using Xaman Wallet could cost more than expected, especially for small trades. Some compared the reported fees to Ethereum transaction costs.

The 659 XRP charge became a focal point of the debate. Users questioned whether hidden routing or service layers caused the high amount. Others asked for clearer fee disclosure within wallet interfaces.

Xaman Wallet provides access to the XRP Ledger and its decentralized exchange. Service providers can apply additional charges beyond the base network fee. These charges are separate from validator fees.

The XRP Ledger base fee remains minimal under normal network conditions. However, wallet services may include their own costs. This difference fueled confusion among some XRP holders.

Nested Multisig Dispute Under XLS 103d

The discussion expanded to a technical issue involving nested multisignature configurations. Critics pointed to XLS-103d, which allows complex signing structures on the XRP Ledger.

In one reported case, a user created a nested multisig setup that could not be resolved. As a result, access to funds became frozen. The configuration followed existing ledger rules.

Wietse Wind, XRPL developer and Xaman Wallet contributor, addressed the case publicly. He stated that the setup was not a backdoor. He explained that the ledger permitted the structure.

Wind said the issue required a protocol amendment to enable recovery options. He noted that changes to XRPL rules depend on validator consensus. No single company can alter the protocol alone.

Validator Governance and Proposed Amendment

An amendment proposal has been submitted to the XRPL codebase. The proposal seeks to allow nested signatures in a recoverable format. Validators will review and vote on the change.

XRPL governance operates through decentralized validator approval. Ripple does not hold unilateral authority over amendments. Protocol updates require network agreement.

The current debate shows the separation between Ripple, wallet providers, and validator governance. Schwartz’s response reflected that separation during the wallet fee controversy.

As discussions continue, XRP community members are monitoring both wallet fee policies and the amendment process. The outcome will depend on validator decisions and software updates within the XRP Ledger ecosystem.