Ripple moved a total of 310 million XRP across three transactions within minutes on Oct. 30 Beijing time, according to Whale Alert, with the transfers valued at about $389 million. One transaction involved Ripple sending out 120 million XRP worth roughly $151 million. The other two showed unknown wallets transferring 90 million XRP and 99,999,999 XRP to Ripple, valued at about $113 million and $126 million, respectively. Ripple has not explained the purpose of the transfers. The activity came after Ripple executives had confirmed the company was assisting with the handling of stolen XRP linked to the Binance hack and had frozen affected funds. The transfer pattern, combining one outbound transaction from Ripple and two inbound transactions to Ripple, drew attention because of the size and timing of the movements. The original report cited Whale Alert data and was carried by Techub, with U.Today referenced in the item.
Ripple moved 310 million XRP across three transactions within minutes on Oct. 30 Beijing time, according to Whale Alert, with the transfers valued at about $389 million.
One of the transactions showed Ripple sending out 120 million XRP worth about $151 million. The other two involved unknown addresses sending 90 million XRP and 99,999,999 XRP to Ripple, valued at about $113 million and $126 million, respectively.
Ripple has not disclosed the reason for the transfers.
Earlier, Ripple executives confirmed that the company was assisting in handling stolen XRP tied to the Binance hack and had frozen the affected funds.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
