I see that the project team is working seriously, but they don't first check how lively Twitter is; instead, they look at the treasury expenditures: where the money is spent, how frequently, and whether it matches the milestones. To put it simply, ongoing small expenses (development, audits, operations) plus periodic large expenses (like mainnet launches/upgrades) are considered normal; the worst are those who send a lump sum to "partners/market" and then start making promises, with milestones always on the horizon...

Recently, the cross-chain bridge was hacked again, which is exhausting to watch, so I am now especially concerned about whether the treasury has a "security budget" and whether the upgrade permissions are well-controlled. Also, after oracle prices go awry, everyone is shouting "wait for confirmation"; if the project team truly understands, they would clearly specify emergency switches and risk control thresholds, rather than posting long explanations afterward.

There are many tutorials, but I prefer those that visualize permissions/upgrades/oracles in a single diagram, along with the treasury flow, so I don't have to sift through details one by one... Anyway, I’d rather be slow than help friends clean up a mess again.