2025-12-31 07:22:25

I have been mistaken about the FLOW project from the very beginning. I still remember when it was worth a little over twenty dollars, and I had some expectations for it. But the development of events was completely unexpected—the price kept declining, and the underlying reason pointed to the decision-making issues of the founding team.

The data is there: from its all-time high to now, the decline has exceeded 450 times. Recently, it’s been even more outrageous, with a single-day drop of 50%. Even so, the project’s market cap remains in the hundreds of millions, and according to the current trend, it could drop another tenfold.

What’s truly disappointing is the project team’s attitude towards handling crises. Whenever problems arise, most reliable projects would prioritize minimizing user losses. But this team? They offer a bunch of self-justifications, reasons one after another, all sounding like they are defending the project from their own perspective.

Users’ eyes are sharp. Projects lacking transparency and putting user interests last will eventually be educated by the market. Let’s wait and see how it develops.

FLOW-6,84%

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.

12 Likes

Reward
12
5
Repost
Share

Comment

0/400

CommunityWorker

· 18h ago

Another scam project, it should have died long ago --- Flow was hyped up so much back then, now it's crashing so badly, serves them right --- The team’s morale has collapsed, there's no hope --- No transparency at all, yet they still want to survive, hilarious --- A tenfold drop isn't enough, it must be wiped out completely --- Just looking at how they shift blame makes me sick, they treat users' hard-earned money as a joke --- Anyone who trusted them initially should reflect on it, the project team clearly has no regard for users

View OriginalReply0

SelfCustodyIssues

· 18h ago

I'll say it directly, the Flow incident is just the team shooting themselves in the foot. I saw it when it was over 20 bucks, but once I saw their crisis management skills, I just left. --- A 450x drop and still arguing? Truly impressive. --- Basically, they don't take users seriously, and they'll be liquidated sooner or later. --- That's why I only deal with projects that have genuine governance now. The attitude of the Flow team guarantees it's hopeless. --- A 50% daily drop with a market cap in the hundreds of millions? That valuation is just absurd. --- It's high time to see clearly: no matter how bad a project is, it can be hyped up; only by crashing the price can people be awakened. --- If the team really cared about users, they wouldn't have a bunch of excuses. Now it's all about self-protection and old tricks.

View OriginalReply0

AirdropHunterKing

· 18h ago

I wish I had gone all-in at $20 when I first knew about it. That would have been the real sheep-shearing. This team really doesn't get it. During a crisis, they are still justifying themselves. Just like when I saw contract vulnerabilities while farming and they refused to admit it—same kind of project team. I've never seen a 450x decline; how capable are they... If it drops another ten times, I might consider bottom fishing. The key issue is transparency. Every interaction requires repeatedly verifying wallet addresses to avoid being exploited. Trust is long gone. Projects like this that can't even handle airdrops shouldn't be touched. Gas fees are wasted. Next time I encounter something like this, I'll just pass.

View OriginalReply0

TokenTaxonomist

· 18h ago

per my analysis, flow's governance architecture was taxonomically incorrect from day one. a 450x drawdown isn't volatility—it's evolutionary dead-end behavior, statistically speaking. the team's crisis response? let me pull up my spreadsheet... actual data suggests they prioritized narrative over token phylogenetics. classic mistake.

Reply0