HYPE: 954,400 tokens set to hit spot within 24 hours; top three receiving wallets to take in $55.4M

According to Huo Mars Finance, TradingBeats data as of Aug. 26 shows roughly 954,400 HYPE tokens are expected to finish their seven-day unstaking cooldown over the next 24 hours and move into spot accounts. At current prices, that flow is valued at about $78.094 million. About 3.2252 million HYPE tokens remain in the withdrawal queue, worth roughly $264 million. Under Hyperliquid's rules, staked HYPE must wait seven days before it can be transferred back to a spot balance. Over the next 24 hours, the three largest receiving addresses are set to take in a combined ~676,900 HYPE (about $55.382 million), representing around 70.9% of the expected inflow: - 0x0f99: ~300,700 HYPE due early tomorrow morning, worth about $24.598 million. Its staked balance has been almost fully drawn down. - 0x393d: ~206,500 HYPE expected around noon tomorrow, worth about $16.899 million. This wallet is the Kinetiq StakingManager, and the transfer appears more consistent with protocol redemption and liquidity management. - 0x82b0: ~169,700 HYPE due tomorrow afternoon, worth about $13.885 million. Its staked balance has also been reduced to zero. The roughly $78 million moving into spot over the next day should not be viewed purely as immediate sell pressure. Part of the flow is tied to protocol-related activity, while 0x0f99 and 0x82b0 have effectively zeroed out their staked balances after unstaking, making subsequent movements from these wallets worth monitoring. Separately, a wallet beginning with 0x16a initiated two additional transfers from staked balances to spot yesterday evening totaling about 124,900 HYPE. Including earlier requests, it now has around 244,900 HYPE (approximately $20.035 million) in the seven-day queue, scheduled to be released to spot accounts on Aug. 30 and Sept. 1. Primary withdrawal addresses: 0x0f991873aab3e14191978946d48f30f624ae9867 0x82b02bd42b8a837228181ea34bf0679a51a37e39 0x16a4814e8eb502c56cebd73f9c8ac7fdee29c042 Protocol address: 0x393d0b87ed38fc779fd9611144ae649ba6082109