DAO Governance Weekly — 2026-09-21
This week's biggest governance story is Cardano's DReps rejecting Input Output's request to withdraw 12.29 million ADA from the community treasury, a landmark vote on treasury control. Lido DAO is moving forward on a contingent 7.5M LDO market-making mandate, while Cratos DAO votes on reward distribution parameters. The theme emerging this week: DAOs are increasingly willing to say "no" to core teams seeking treasury funds.
DAO Governance Weekly — 2026-09-21
Cardano: DReps Reject Pogun Treasury Withdrawal
- Status: Rejected ❌
- What it does: Cardano's delegated representatives voted down a request to withdraw 12.29 million ADA from the community treasury to fund Input Output's "Pogun" Bitcoin DeFi product.
- Votes: 35.67% of DRep voting power in favor, 64.33% opposed, per the final Koios summary.
- Why it matters: This is a significant assertion of treasury control by Cardano's delegated representatives — funds remain in the community treasury while Input Output rethinks its approach. It signals DReps are willing to exercise real fiscal oversight over core-development spending.
Lido DAO: Contingent 7.5M LDO Market-Making Mandate
- Status: On the table 🗳️
- What it does: Lido DAO is voting on a contingent 7.5 million LDO mandate for market-making services.
- Why it matters: Treasury deployments to market-making remain among the more scrutinized allocations in major DAOs; the contingent structure itself reflects governance efforts to reduce open-ended treasury commitments.
Active Proposals to Watch
| DAO | Proposal | Stage | Deadline | Estimated Impact |
|---|---|---|---|---|
| Cratos DAO | Adjust user reward distribution parameters and calculation periods within its Vote-to-Earn (V2E) mobile app ecosystem | Voting | Voting ends Sept. (per CoinDesk's Week Ahead, published Sept. 14) | Changes incentive economics for V2E app users |
| Lido DAO | Contingent 7.5M LDO market-making mandate | Onchain vote | In progress | Treasury deployment for LDO liquidity support |
Treasury & Financial Moves
- Cardano: The 12.29 million ADA withdrawal for Input Output's Pogun was rejected, keeping the funds in the community treasury while IOG rethinks its first major policy request to DReps.
- Lido DAO: A contingent mandate of 7.5 million LDO for market making is under vote this week.
Governance Trends & Analysis
The Cardano Pogun rejection stands out as the week's defining governance moment: a major ecosystem foundation asked for treasury funding, and its delegated representatives said no with nearly two-thirds against. It's precisely the kind of contested fiscal vote that tests whether DAO treasuries genuinely belong to communities rather than core teams.
Structural commentary this week also focused on governance legitimacy itself. A piece from MconnectDAO.eth Research argues that DAOs "must change these rules before community trust collapses," reflecting ongoing anxiety that token-weighted voting and slow proposal cycles erode the credibility decentralized governance was built to deliver.
Against the backdrop of DAOs collectively holding over $26B in treasuries, contested spending votes like Cardano's are likely to become the norm rather than the exception — with DRep-style delegated voting structures giving communities sharper tools for fiscal accountability.
What to Watch Next Week
- Cratos DAO's V2E reward-distribution vote is closing — a small but representative example of DAOs fine-tuning economics via governance
- Whether Input Output returns with a revised Pogun funding request after the rejection
- The final outcome of Lido's contingent 7.5M LDO market-making vote
Reader Action Items
- 🗳️ Vote: Cratos DAO's V2E reward parameter proposal is in its final days — check the CoinDesk Week Ahead tracker for the exact close
- 📖 Read: "DAOs Must Change These Rules Before Community Trust Collapses" for a candid critique of current governance design
- 👀 Monitor: Cardano governance — Input Output's next move after the Pogun rejection could reshape core-team funding on the network
This content was collected, curated, and summarized entirely by AI — including how and what to gather. It may contain inaccuracies. Crew does not guarantee the accuracy of any information presented here. Always verify facts on your own before acting on them. Crew assumes no legal liability for any consequences arising from reliance on this content.
Powered by
