Quarterly reporting of Budget expenditures

[Pythian_151]

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.

[Kirito.sol]

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.

[theretardedadrian]

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.

[0xhinkah]

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.

[Pythian_151]

First of all Thank you every one for taking the time to read and reply to my proposal.

I’ll try to address the points that have been raised. This is my personal opinion.

1. On-chain data shows movement, not meaning

It’s true that all transfers are visible—but what we actually see is wallet A → wallet B, not the reason behind that transfer or the value delivered.

A community member looking at raw transactions cannot answer:

• Was this payment for a high-quality research thread or a low-effort post?
• Did a hackathon participant ship a working product or just register?
• Is this a one-off reward or part of a recurring stipend?

Without context, transparency is superficial.

On-chain data provides proof of payment, but not proof of work. Reporting bridges that gap by connecting transfers to outcomes.

This isn’t about duplicating data—it’s about making it interpretable and meaningful for governance

2. Privacy can be preserved with pseudonymous attribution

The concern around exposing real identities is valid—but it’s not a blocker. It just means the implementation needs adjustment.Instead of real names, reporting can include:

• Twitter / X handles
• YouTube channels
• Discord usernames
• Or other public-facing contributor identities

paired with wallet addresses.This actually improves accountability in a more DAO-native way:

• Contributors are evaluated based on their public work and reputation
• Community members can independently assess whether output matches compensation
• No requirement to expose legal identity.

The goal isn’t to tie payments to real-world identities, but to link compensation to observable contributions. Pseudonymous handles achieve this while preserving individual privacy

3. Scope of work: this is not new data, just structured disclosure

The idea that this creates significant overhead is overstated.

The key point:

• The transfers already happen
• The recipients are already known internally
• The allocation categories (Content, Hackathons, etc.) are predefined

So the proposal is not asking the Council to create new information, but simply to organize and disclose what already exists in a consistent format.This isn’t additional operational work—it’s lightweight reporting on decisions and distributions that have already been made and tracked internally.

4. Why this matters for the DAO specifically

DAOs rely more heavily on transparency than traditional orgs because:

• Token holders are effectively stakeholders
• Contributors are often remote and pseudonymous

That makes contextual transparency (not just raw data)

Without structured reporting, the community is left to interpret isolated transactions. With it, they can evaluate whether treasury spending aligns with actual contributions and ecosystem growth.

[theretardedadrian]

Firstly, I don’t think any community member actually has the time to go through all of the posts to determine if they were high quality or low quality posts. It would take a lot of time, energy, and effort. This is why the community council goes through the posts on our behalf and filters them accordingly. In the new budget proposal, they also introduced voting by the community councillors which can be monitored in discord now. That seems transparent enough in comparison to other projects.

Secondly, back to the hackathon, the data of the winner, the work of the other contestants, the judging metric, and the process of how the winner was chosen was explained by chop already on discord and even on twitter ((1) Community Hackathon Judging / X). The judging was even done publicly. I would also think that’s transparent enough.

Thirdly, Privacy is, in fact, my main concern about your proposal. Your reason for privacy are far-fetched because:

1, Contributors have always been evaluated based on their public work and reputation—this was already happening back in the days of kaito.

2, Community members independently assessing whether output matches compensation is a myth because, as I earlier stated, I think that no one actually goes through thousands of posts trying to see if a contributor is deserving.

In conclusion, your scope of work states that “the recipients are known internally” which is false and portrays the council in a fraudulent light—it assumes that the council is laundering community funds. The recipients are not known internally, they consist of consistent contributors. Anybody is free to join and would be judged accordingly.

[Joy]

I fully agree. In particular, I believe that the expenditure details of the allocated DAO budget must be disclosed transparently and in great detail. This is a matter of course for any company. Furthermore, this is a matter shared with the members. It does not undermine decentralization.

[0xhinkah]

I understand what you’re trying to do with this adding more context to spending so people don’t just see wallet-to-wallet transfers but actually understand the impact behind them. That makes sense in principle.

But I still think this pushes the DAO in the wrong direction.

The moment we start trying to attach detailed “meaning” to every transaction, we open the door to micromanagement. People will naturally start questioning whether a specific post, video, or art was worth the payout, and that turns into noise very quickly. That’s exactly why the Community Council exists in the first place. If we don’t trust their judgment on what qualifies as valuable work, then the issue isn’t reporting it’s governance. We should be judging them on overall results, not individual line items.

On the pseudonymous point, I get the idea, but it doesn’t really remove the risk. Linking a public handle to a wallet that’s receiving funds still exposes contributors in a real way. In Web3, that kind of visibility can make people targets for phishing or social engineering. Even without real names, you’re still tying identity to financial activity, and that’s not something everyone will be comfortable with.

And on the “lightweight” reporting this almost never stays lightweight in practice. Organizing the data, formatting it, publishing it, then answering follow-up questions from the community… it adds up. Over time, it shifts the CC’s role toward explaining decisions instead of actually executing them.

We also shouldn’t ignore the cost side of this. Bringing in third-party auditors means additional expenses, and that money will likely come directly from the DAO budget. That’s funding that could otherwise go into actual ecosystem growth. If there isn’t a clear issue right now, it’s hard to justify adding that layer of cost.

At the end of the day, the strongest proof of work isn’t a report it’s results. If the ecosystem is growing, integrations are increasing, and the network is being used more, then the funds are doing what they’re supposed to do. If not, the community can step in and hold the Council accountable.

Right now, this feels like adding structure, cost, and overhead before we’ve even seen a real problem. I’d rather we keep things flexible, trust the CC to do their job, and rely on on-chain transparency and outcomes. If gaps show up later, then we can revisit stronger reporting with a clearer reason for it.

[Pythian_151]

Thank you 0xhinkah for your reply, I understand your point of view as well.

[Pythian_151]

Thank you, Adrian the Retard for your response. I’d like to clarify some points regarding your previous statement:

1. I have been a long-term investor and community member in the PYTH network since April 2024. My focus is not on short-term price movements, but on broader adoption, which is ultimately reflected in token value. Proper reporting is essential for transparency and accountability.

2. You mentioned that I claimed “the DAO spending caused price to fall.” This is incorrect and misleading. What I actually said was:
   “From April 2025 to March 2026, we spent 3,670,655 PYTH on all marketing programs. How can we state that this has led to greater adoption when the token price has fallen from approximately $0.40 to $0.04? Now we are asking for 8,000,000 PYTH from the DAO for marketing—specifically, 6,000,000 PYTH for content creators, equating to the entire current DAO reserve.”

My point was to question the efficacy and justification of the proposed budget, not to assign causality for price movements.

3. You stated that I suggested “the recipients are known internally,” implying fraud. I want to clarify that I am not making any allegations of fraud. If funds are being sent to contributors , the council already are aware of their public-facing contributor identities (Discord, YouTube, X) otherwise how would the scope of their work be judged.

   Thank you again Adrian the retard for your reply.

[theretardedadrian]

The efficacy and justification of the budget has already been explained in details by Chop in the previous post, where he outlined the reason why this type of marketing was adopted. I think that was a reply to you too. Gracias.

[Pythian_151]

Yes… I was addressing your allegation of DAO spending to price movement.

[Clyde]

I understand your reasons, but I completely disagree for two reasons.

1, The council has shown consistent transparency since elected, and I don’t think there is any reason to add to their burden in the name of “regular reporting”.

2, This is against decentralization and Exposing wallet address of contributors is in no way ensuring accountability.