Everyone wake up! Our so-called "King of Cross-Border Payments" XRP has recently been performing in the ETF circle like a scene of "mutual fighting"! I just finished reviewing last week's (4.27-5.1) ledger, and although the overall interruption was only 35.2k, which sounds small, I shivered at the drizzle, but there's more drama behind it: "Player scumbag" Bitwise: This guy led the withdrawal last week, pulling out a total of 35.2k. But don't rush to criticize, their total historical inflow still has 422 million at the bottom, probably made some small gains and took the profit first. "Warm guy" Canary: When someone withdraws from the pyramid, someone else tops up! Canary (XRPC) trend is counter-bottoming, with a net inflow of 2.2018 million. The total historical inflow has skyrocketed to 424 million, rivaling Bitwise. Solid backing: Despite the ups and downs in a week, the total net asset value of XRP ETF remains stable at 1.06 billion. The most impressive is the total cumulative net inflow, which has reached 1.29 billion! What does this mean? Although big players occasionally adjust their positions, the chips in their hands are tightly held. Honest thoughts from the blogger:


XRP right now is like a backup reserve sitting on the bench, although it’s not as clear as Bitcoin, but the "supply funds" behind it haven't decreased at all. As long as this red line of total net assets keeps rising, Ripple's loyal supporters can stay strong! Today's interaction:
Do you believe in Canary’s contrarian accumulation, or are you worried about Bitwise’s withdrawal signals? Tell me in the comments, what do you think XRP is missing for the next explosion? 👇
BTC1.15%
XRP0.14%
ZEC2.6%
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pin