When I judge whether a project is truly doing serious work, I actually pay less attention to “how much is left in the treasury,” and more to how the treasury funds are used and what milestones are produced after the spending. In plain terms, it’s: expenditure → deliverables → whether the user journey has become shorter. For example, for things like account abstraction or payments: the treasury being spent on audits, SDKs, wallet integrations, and merchant pilots—ultimately, whether it can help me sign one fewer time and jump one fewer page is the most direct indicator.

Recently, everyone has been watching large on-chain transfers and unusual movements between exchanges’ hot and cold wallets as “smart money.” I’ll take a look too, but what I care about more is whether there’s corresponding follow-through afterward—such as the team’s releases, documentation updates, governance proposals actually being implemented, or adjustments to the fee structure. Just transferring funds without delivering anything is prone to turning into noise.

My simple method: treat every spend as a node, then track it for the next two or three weeks to see whether I can map out a closed-loop flowchart. If I can’t, or if the milestones are always “next quarter,” then I’ll wait and observe for now—at the end of the day, it’s not like this one transaction is irreplaceable.