A recent portfolio problem involving an attempt at 10,000 XRP transactions caused controversy in the XRP community, which prompted confusion and speculation. The stranded transaction, reported on XRPL as payment of “Xaman service costs”, presented itself during a routine swap operation. Although the transaction has not passed due to insufficient funds, the significant amount has raised immediate concerns.
The reported transaction appeared during a routine exchange operation, where a user would have been billed which seemed to be service fees of 10,000 XRP.
You might also love
The transaction has shown a failing status labeled “not funded_payment”, which means that the shipment account had no sufficient balance – excluding reserve requirements – to complete the transfer. Despite this failure, the size of the attempted attempt triggered an immediate alarm.
In the midst of increasing concerns, Ripple's CTO, David SchwartzWho is also the architect of XRP Ledger, intervened to clarify. He explained that the problem was not intentional or malicious, but rather a rare side case that the system was not put in place to manage. According to him, the problem has now been fixed and no funds have been lost because the transaction has never succeeded.
You might also love
Users have expressed their concern about the possibility of poor software behavior or handling, some considering the occurrence as the reflection of deeper reliability problems with the Xaman portfolio. A user has even raised alarms suggesting that this could be a coordinated attempt to damage the reputation or target specific vocal companies in their criticism of the management of XRPL.
Some have gone further, which suggests that the problem could be more than a simple bug – perhaps even a targeted decision against developers or projects in the XRP ecosystem. This speculation spreads quickly, nourishing distrust and frustration.
