This time, what’s truly worth noting isn’t $83 million, but rather:
Ripple also can’t freeze these XRP.
Bitget was previously hacked for about $387.5 million, with roughly 103 million XRP transferred to multiple addresses. Now, about 54 million XRP, worth roughly $83 million, has continued to be moved. (CoinDesk)
The reason is interesting:
For assets like USDT and USDC, the issuer can blacklist addresses and freeze assets; but XRP is a native asset of the XRP Ledger, and Ripple doesn’t have the authority to directly freeze it.
So this time, Circle and Tether can freeze part of the involved stablecoins, but XRP can only be stopped from flowing in afterward via exchanges. (CoinDesk)
In fact, this incident puts a big contradiction in the crypto world front and center:
If assets can’t be frozen, that’s a decentralization advantage. But once coins end up in the hands of hackers, it also becomes an obstacle to recovering the assets.
Not because it has been performing well recently, but because I value these points:
Over the past 30 days, Pons:
* DEX trading volume of about $2.46 billion * Protocol revenue of about $25.37 million * About $14.0 million used for value backflow / buybacks and burns * Current PONS market cap of about $425 million
When I choose a trading pair, I actually care most about two things:
1. Whether there is real trading volume If the trading volume is large enough, LPs will have a steady source of fee income.
2. Whether the token itself captures value PONS protocol revenue partially flows back to the token—not just relying on inflationary incentives to prop up the APY.
So for me, PONS isn’t about “betting it will rise,” but about:
Earning fees from trading volume + PONS having a buyback logic.
Of course, the risks are also clear: If trading volume drops quickly later on, the high yields you see now will fall along with it.
So I focus more on whether trading volume can be sustained, rather than the APY itself.