I’m now checking whether a project is serious or not—I’m actually less concerned with the milestones they draw up on paper. Instead, I look first at treasury spending: where the money goes, whether the pace is steady, and whether it’s just going “KPI-chasing” in short, bursty sprints. To put it bluntly, fixed-frequency costs for development, audits, and infrastructure—paired with delivery traces you can see on-chain (contract updates, permission tightening/convergence, documentation/frontend iterations)—gives me way more confidence than a roadmap ever will.

Lately, cross-chain bridges have been hacked again, and oracles have returned abnormal quotes. Everyone’s started to default to “wait for confirmation” before they act, which is also a kind of vote with your feet: if you usually save money by putting it into security, and something goes wrong, then users are the ones who end up paying the time cost. And then there’s treasury spending where more than half goes to “market partnerships/ecosystem incentives,” but the floors and order walls look hollow—so I don’t believe that either. In any case, I’d rather the project moves a bit slower, as long as the books and the deliverables line up.