# $HFT Catalyst Posts & Social Intelligence Recap — July 21, 2026 > **Asset:** $HFT > **Date:** 2026-07-21 (July 21, 2026) > **Canonical URL:** https://cryptitalk.com/tokens/hft/2026-07-21 > **Token Profile:** https://cryptitalk.com/tokens/hft.md > **Market Rankings:** https://cryptitalk.com/rankings.md --- ## Curated Viral Posts & Community Evidence ### Post #1 by @WakiyamaP > **Author:** 脇P(jinP) ([@WakiyamaP](https://x.com/WakiyamaP)) > **Metrics:** 11 likes · 3 retweets · 1 comments · 1.5K views > **Posted:** 2026-07-21T10:59:33+00:00 > **Source Link:** [https://x.com/WakiyamaP/status/2079521657128120528](https://x.com/WakiyamaP/status/2079521657128120528) > **Visual Note:** A screenshot of a Twitter/X page from @hashflow showing their pinned tweet "The IPQ liquidity is now available on..." circled in red, along with their hashflow NFT profile and a pinned post about bridging hashflow across MAT quotes on Polygon/USDC. The post references a potential rug pull involving Hashflow, and the image shows the official Hashflow Twitter account highlighting NFT-related liquidity announcements, which may have been used to promote legitimacy before any alleged exit. > > "Hashflow might have pulled a rug pull. Be careful." ### Post #2 by @hashflow > **Author:** hashflow ([@hashflow](https://x.com/hashflow)) > **Metrics:** 1 likes · 1 retweets · 1 comments · 645 views > **Posted:** 2026-07-21T16:14:46+00:00 > **Source Link:** [https://x.com/hashflow/status/2079600983554867655](https://x.com/hashflow/status/2079600983554867655) > > "Incident Update: DNS Disruption & Discord Invite Link Over the past day, Hashflow experienced two unrelated issues. Both have been fully resolved, and at no point were Hashflow’s smart contracts, protocol infrastructure, or user funds compromised. Below, we provide more detail" ### Post #3 by @hashflow > **Author:** hashflow ([@hashflow](https://x.com/hashflow)) > **Metrics:** 0 likes · 0 retweets · 0 comments · 185 views > **Posted:** 2026-07-21T16:17:24+00:00 > **Source Link:** [https://x.com/hashflow/status/2079601645713760479](https://x.com/hashflow/status/2079601645713760479) > > "Thank you for flagging. We've posted communications around these issues. The official discord is now linked and verification is working properly. The DNS issue is also resolved." ### Post #4 by @hashflow > **Author:** hashflow ([@hashflow](https://x.com/hashflow)) > **Metrics:** 0 likes · 0 retweets · 0 comments · 15 views > **Posted:** 2026-07-21T16:40:23+00:00 > **Source Link:** [https://x.com/hashflow/status/2079607430976041434](https://x.com/hashflow/status/2079607430976041434) > > "Thank you for flagging. All issues have now been resolved." --- *Generated by Context Pilot Social Intelligence Engine.*