Lately, reading proposals has been a bit exhausting, but I’m still at it… To put it plainly, to judge whether the project team is serious, I first watch how the treasury is spent: if all the money goes into big words like “we’ll talk about it later,” I get alert; meanwhile, those that are broken down into small milestones, with deliverables that can be accepted and verified (even if they’re a bit plain—like open-source progress, audit receipts, monthly operations reports), feel more like they’re actually doing work. What I fear most is when they want to release funds while writing the acceptance as something mystical like “the community perception is good.”

Over the past couple of days, after the main public chain upgrade/maintenance, people in the group have been speculating whether the ecosystem will migrate, and I can’t help but laugh at it: whether they migrate or not, don’t rush to take sides. Check whether they have a migration contingency plan, whether the budget has a line item for “emergency/migration costs,” and whether there’s a clearly identified person responsible and a concrete delivery timeline. If not, it’s probably just migration talk, with everything falling apart in practice. Either way, before I vote, I look at the attachments first—I don’t follow emotions.