Everyone gets it: whether the project team is really doing solid work comes down to this—don’t look at the PPT; look at where the money goes. I recently went through the treasury spending of a few DAOs, and the simplest takeaway is: the money goes into “things that can be delivered,” or it goes into “things that just look busy.” Milestones may be written beautifully, but half the budget goes to marketing, advisors, and all sorts of co-branded sponsorships. Meanwhile, code updates and audits end up dragging their feet. So I’ll quietly reduce my position a bit—I’m not trying to make things harder on myself.

And about this whole “stacking yields” setup with additional staking and shared security—it’s not that it can’t be done. The key is whether the treasury covers the risks upfront: are audits, insurance/emergency funds, and bug bounties actually backed by real money? If something goes wrong, who’s responsible? To put it simply, only if they’re willing to spend money on “before things go wrong,” not “PR after things go wrong,” will I dare to slowly simmer away. In the end, less fuss means more sleep.