The project team keeps talking about "milestones" every day, but who are they really for? I myself now care more about how the treasury funds are spent, whether there’s anything reusable left after spending.

To be honest, the budget isn’t about saving as much as possible; it’s about aligning expenses with deliverables: hiring, auditing, infrastructure, validator incentives—once spent, you should see the rhythm. It’s not about posting progress updates every now and then while the on-chain activity remains silent. The simplest approach for me is to focus on a few small things: whether payments are itemized clearly, whether there are verifiable deliverables (code, audit reports, deployment records) when milestones are reached, and whether reasons for delays are clearly explained and what the next steps are.

Recently, there’s been a heated debate about privacy coins/mixing compliance boundaries. It also reminds me: when dealing with sensitive areas, whether you dare to openly discuss fund flows and decision-making processes often reveals more about whether you’re serious about your work than slogans do. Anyway, I prefer a slower pace if it means not cutting corners, especially for projects like mine that lean toward staking.