Former Ripple CTO Responds to Backlash Over Xaman Wallet’s High Fees!

• Ripple CTO responds to Xaman Wallet’s unexpected high transaction fees.
• Xaman Wallet’s multisignature issue causes frustration within the XRP community.
• Developer clarifies nested multisig setup, offers protocol amendment proposal.

The XRP community recently found itself in a heated debate following criticisms surrounding the Xaman Wallet. Reports surfaced claiming that the wallet’s transaction fees were unexpectedly high, even surpassing Ethereum’s gas fees for small transfers. A post from a user on X highlighted that Xaman’s fees were worse than Ethereum’s, especially when trading amounts greater than $3. This sparked a wave of frustration among XRP users, many of whom expressed their dissatisfaction online.

Concerns Over Xaman’s Fees and Transparency

Also Read: Big News: XRP About to be Added to Official State Digital Asset Reserve – Details

Amidst this backlash, David “JoelKatz” Schwartz, Ripple’s former CTO, was tagged in social media posts addressing the issue. His response was swift but brief. In a tweet, Schwartz simply wrote, “What did I do?” This remark came after a post that directed the criticism towards him, asking, “Shame on you.”

Schwartz’s response appeared to distance him from the issue, as he clarified that he was not involved in the operational decisions of third-party wallet providers like Xaman. Despite Schwartz’s attempt to remain neutral, the focus shifted to concerns about Xaman’s use of nested multisignature setups under XLS-103d.

Developer Clarifies Multisignature Issues

Critics raised concerns that nested multisignature setups under XLS-103d could lock users out of their accounts or introduce hidden approval paths. This sparked frustration among the community, especially as some users reported being unable to resolve multisig structures, effectively freezing their funds.

Wietse Wind, a developer with Xaman and the XRP Ledger, addressed these issues, explaining that the problem stemmed from a configuration allowed by the XRP Ledger protocol. He clarified that this was not due to a backdoor or malicious intent but an unintentional error by a user. To resolve this, a proposal has been submitted to amend the protocol, enabling recoverable nested multisignatures, pending validator review and approval. This highlights the decentralized nature of XRP Ledger, where protocol changes require consensus from validators.

Also Read: “Pundit to XRP Holders: ‘The Clarity Act Administration Policy Is a Blueprint of Ripple’s Financial Infrastructure’ – Here’s How”

The post Former Ripple CTO Responds to Backlash Over Xaman Wallet’s High Fees! appeared first on 36Crypto.