Santiment says XRP added 7,934 wallets a day after Binance breach
XRP recorded its sixth-highest daily wallet count of 2026 on 1 Nov, which Santiment linked to users possibly moving to self-custody after the Binance hack.
Key points
- Santiment reported 7,934 new XRP wallets on 1 Nov, the sixth-highest daily total of 2026, with XRP trading near $1.25.
- Santiment said growth above roughly 4,000 wallets a day plus a reclaim of $1.30 would make the setup more constructive.
Santiment says XRP wallet growth accelerated after the Binance breach, with 7,934 new wallets created on 1 Nov, the sixth-highest daily total of 2026. The analytics firm reported the figure on 2 Nov and linked the timing to the hack, suggesting some users may have moved towards self-custody and fresh wallets. The count measures new addresses, not how many separate people joined the network.
The breach involved XRP directly. Investigators found five Binance wallets sent 233.46 million XRP to an address controlled by an attacker in about four minutes on 29 Oct, leaving each sender with only its minimum balance. Binance said on 31 Oct that XRP and nine other cryptocurrencies were fully backed after it replaced stolen assets with company resources, and it reported covering about 95% of the affected amount. A phased withdrawal plan scheduled an initial reopening window for 1 Nov.
The attacker moved the stolen XRP into six new wallets on 2 Nov, after the assets had sat largely untouched for about 80 hours. UTC redistributed roughly 233.45 million XRP.
What to watch: Santiment's conditions remain open: wallet growth above roughly 4,000 a day and a reclaim of $1.30, or a drop below $1.20 with growth under 3,000.
Live updates on NewsFeeds:AltcoinsDesk editor: Keshav Aggarwal (accountable for this page; this summary was not edited by hand)
How this was produced: an AI model wrote this summary of Bitcoin.com News’s report, which we credit and link above. Read our Editorial and AI policy. Spotted a mistake? See Corrections.
Not investment advice. Read the risk disclaimer.