Summary: Quarterly Reporting of DAO Budget Expenditures
Proposal:
Implement quarterly reporting of DAO reserve spending by the Community Council, complemented by an annual audit conducted by an independent third party.
Rationale:
The Term 2 Budget Request (Op PIP 101), approved on April 17, 2026, allocated 8,000,000 PYTH tokens (~$328,000) over 12 months to support the Content Program, Hackathons, Pythentity, and Role Stipends.
Given that DAO reserves represent community earnings and dividends, transparency in fund allocation is critical. Detailed quarterly reporting will allow community members and investors to monitor how funds are distributed, enhancing trust and accountability.
Implementation:
Quarterly reports (starting July 17, 2026) will include:
-
Content Program (6,000,000 PYTH): Recipient name, wallet address, and amount distributed.
-
Ongoing Hackathon (400,000 PYTH): Project/individual name, wallet address, and amount distributed.
-
Pythentity (200,000 PYTH): Wallet address and amount distributed.
-
Role Stipends (560,000 PYTH): Name and Role, wallet address, and amount distributed.
Conclusion:
Regular reporting and annual auditing will provide transparency, strengthen community confidence, and ensure accountability in DAO budget management.
1 Like
Thanks for putting this together, transparency is a value we all share, and I appreciate the effort behind this proposal. That said, I find myself unconvinced that this is the right mechanism, and here’s why:
1. Operational overhead vs. actual accountability gain
The Community Council is already accountable through on-chain visibility, every wallet transfer is publicly verifiable in real time. Mandating formatted quarterly reports adds significant administrative burden without meaningfully improving the information available to the community. We’d essentially be paying staff time (funded by the same DAO reserves) to repackage data that is already public.
2. Privacy and security risks
Publicly linking individual names to wallet addresses and specific token amounts in official DAO reports creates a real-world security risk for contributors. This is particularly concerning for Role Stipend recipients and individual hackathon participants, people who are not necessarily public figures and did not consent to that level of exposure. This proposal could unintentionally deter talented contributors from participating.
3. The annual audit already covers this
The proposal itself includes an independent annual audit, which is the appropriate tool for catching misuse of funds. A proper third-party audit provides far stronger accountability guarantees than self-reported quarterly summaries produced by the same body being scrutinized. Doubling up with quarterly reports doesn’t add a layer of oversight, it just adds paperwork.
4. Scope mismatch with budget size
The total allocation is 8,000,000 PYTH (~$328K) over 12 months. The compliance infrastructure this proposal would require, standardized reporting templates, review cycles, public disclosure processes, is disproportionate for a budget of this scale. This level of reporting might make sense for a nine-figure treasury; it’s overkill here.
4 Likes
This is a disingenuous take. From your earlier conversations, you said “Someone creating YouTube video content or retweeting on X is not going to incentivize big institutions to pay 10,000 per month; rather, the quality of the price feed will.” This looks like you consider adoption to mean that the token spirals to the sky, but it rather signifies that real adoption compounds into revenue, credibility, and long-term demand, the kind that sustains value, not spikes it.
In another of your conversations, you said that the DAO spending caused price to fall. That is incorrect. Price falls because of market buy and sell pressure, and the state of the market. More than 60% of crypto went down the same way too since last year. Unlike most of these coins, Pyth has actual utility which creates and drives its adoption. You could have led with the unlocks, and your points might have held water.
The backbone of any project is total decentralization, which you, with this proposal, are trying to upend. I am personally opposed to a third-party audit, however, if the audit proposal is to be accpeted, it should be subject to a vote by the community, and the criteria of audit should also be put to a vote again. In my opinion, Auditing should be done by the team half-yearly to reduce the burden on the councillors. I would suggest that they be made public one month after the end of six months (a suggestion, of course).
Just my thoughts.
1 Like
I totally get the intent here we’re talking about roughly $328,000 { 8M pyth } in community funds, so wanting to know where every pyth goes is natural. But honestly, forcing this specific reporting structure feels like overkill.
Here’s why I’m not sold on it:
• The CC has earned our trust: These guys have a solid track record. Mandating heavy reporting before they’ve even finished deploying the funds feels like we’re bracing for a problem that hasn’t happened. Let’s let them focus on execution, not red tape.
• Transparency is already “on”: This is a DAO. Every cent moved is visible on chain for anyone to see. We don’t need to build a manual spreadsheet on top of a permanent, public ledger.
• Privacy is a safety issue: Forcing contributors to link their real names to their wallets is a huge security risk. We’ll end up scaring away talents if we put a target on their backs just for a report.
• Impact over paperwork: I’d much rather the CC spend their time finding the best devs and creators than acting as data-entry clerks or hiring expensive auditors.
3 Likes