Research brief

Do DAO treasuries actually follow their published spending plans?

18 Oct 2026, 13:24 UTC

On Arkiv

Checking hash in your browser…Read-onlyAnyone can extend its lifeLive from Arkiv
Entity
0x440351329f78fa2349a0c128acb455ee0342036515c6ed189dab1258b36a7309
Content SHA-256
0xd080d68e46c61aaf86154f8150128f523293aee4005d1b44952ffa180487bc8b
Written by ($creator)
0x441aB97848BB539187D93EF3eF7125D1FbABbf27
Lives on Arkiv until
… (block 16508094)
Download recordVerify a copyRe-run as a revisionOpen in the standalone reader

From your own wallet

Challenge this brief, or keep it alive, signed by your wallet on Arkiv's Tiramisu testnet. Stet never holds your key.

Challenges

Filed from any wallet. Each lives on Arkiv under its challenger's address, not Stet's, so Stet can't remove it.

From the command line instead
CHALLENGER_PRIVATE_KEY=0x… npm run challenge -- --run fbe386f2-f39c-4e2d-8c40-bbe0ebca8b61 --target C1 --text "…"
KEEPER_PRIVATE_KEY=0x… npm run extend -- --run fbe386f2-f39c-4e2d-8c40-bbe0ebca8b61 --days 90
medium confidencethesis weakened by the stress test

The safest conclusion is that DAO treasuries are not guaranteed to follow published spending plans exactly, because the supplied evidence shows multiple ways governance, execution, and reporting can break down. However, the record does not establish how common exact adherence or deviation is across DAOs, and the Gitcoin materials do not clearly prove a binding-plan mismatch rather than a revised, partial, or differently scoped budget cycle.

The mechanism evidence is fairly consistent that DAO treasury execution can fail or diverge from intent, but the stress test shows the key empirical gap: there is no representative compliance rate, and the concrete Gitcoin example is not clearly comparable enough to prove noncompliance. That supports a qualified answer, not a broad generalization.

What changed?

7 challenges raised

First answer

medium confidence

The evidence supports a limited but clear thesis: DAO treasuries do not reliably follow published spending plans exactly, because governance approval, execution, and post-spend reporting can break down, and at least one concrete budget example shows a gap between a published plan and actual spending. However, the evidence is not strong enough to say this is universal across all DAOs or all treasury cycles.

After the stress test

medium confidence

The safest conclusion is that DAO treasuries are not guaranteed to follow published spending plans exactly, because the supplied evidence shows multiple ways governance, execution, and reporting can break down. However, the record does not establish how common exact adherence or deviation is across DAOs, and the Gitcoin materials do not clearly prove a binding-plan mismatch rather than a revised, partial, or differently scoped budget cycle.

Why it changed

  1. DAO treasuries do not reliably follow published spending plans exactly.

    → DAO treasuries may fail to translate published spending plans into actual spending in some cases, but the evidence does not establish that they generally do not follow plans exactly.

    The mechanism evidence remains relevant, but the concrete example and generalization claims were weakened by missing comparability, binding-intent, and representative-rate evidence.

  2. The Gitcoin example shows a gap between a published plan and actual spending.

    → The Gitcoin materials show a published budget and reported spending, but do not clearly establish a mismatch between plan and execution.

    The supplied evidence does not prove the figures are directly comparable or that the budget was binding and intended for full execution in the same cycle.

  3. Published spending plans are intended to be executed as written, so deviations from them count as not following the plan exactly.

    → Published spending plans may be binding in some cases, but the evidence does not show that this is always true for DAO budgets.

    The evidence supports authorization through governance, but not a universal rule that all published plans are meant to be followed exactly.

Next steps to validate

  1. Collect a small representative sample of DAO budgets and compare published plans to onchain or reported disbursements for the same cycle.

    Settles: Whether exact adherence is common or rare across DAOs.

  2. Inspect the Gitcoin 2025 budget request and any follow-up reports to determine whether the budget was binding, revised, or only partially intended for execution.

    Settles: Whether the Gitcoin example actually shows a mismatch between plan and execution.

  3. Look for independent audits or research that measure approved budget amounts against actual treasury outflows across multiple DAOs.

    Settles: Whether the conclusion is supported by stronger, less biased evidence than company/blog claims.

Still uncertain

  • How often DAO treasuries execute published spending plans exactly versus partially or not at all is not established.
  • The Gitcoin budget example may reflect timing, revision, or category differences rather than execution failure.
  • The evidence base is weighted toward company/blog sources, so it is weak for estimating a representative rate of compliance across DAOs.
  • It is unclear whether published DAO spending plans are always intended as binding execution schedules rather than flexible authorizations.