Hey everyone - and thank you to everyone who engaged with V3.2 since it went live on May 6th. The thread, the delegate calls, and the direct messages have all been genuinely useful. We read every comment.
Below is a transparency note on what we’re incorporating into V3.3. The full updated post will replace this one once it’s finalized — but we want to be upfront about what’s changing and why before it goes live.
V3.2 → V3.2.2 | Incoming Patch
1. Demand Validation → new pre-screening requirement
We’re adding a mandatory Demand Validation section to the off-chain proposal template. The evidence required will vary by sector: a named integrator LOI for dev tooling and infrastructure, waitlist or MVP usage data for consumer apps, counterparty signoff for payment integrations. This converts what has historically been a delegate-level question at review time into a hard gate at the application stage, consistent with V3.2’s overall posture of measurability before funding.
2. Terminal Milestone → ~30% post-completion holdback
We’re introducing a final tranche (~30% of total grant value) that is released only after a post-completion impact review against the targets committed to in the approved proposal. This closes the gap where the last disbursement currently has no delivery gate beyond it. The “verified delivery” principle in V3.2 now extends to the full grant lifecycle.
3. Cross-Funding Transparency → mandatory disclosure! (as discussed on Delegates Coffee)
Builders will be required to disclose any concurrent or prior funding from other DAOs, protocols, or institutions for the same project or overlapping scope. This is a transparency requirement, not an exclusion criterion - it helps the community make better-informed decisions and surfaces potential attribution gaps early.
4. Standardized Monthly Reporting Template
Monthly Activity Reports will follow a required structure to ensure comparability across grantees and grant waves. The template will cover: on-chain metrics (TVL delta, tx count, new wallets), off-chain milestone progress, and a short narrative. The two-missed-reports trigger for automatic funding review remains in place.
5. FES for Non-DeFi Verticals For projects outside DeFi, builders are required to propose their own FES metrics as part of the off-chain proposal. These will be reviewed and approved or challenged by delegates during the community discussion period. Once approved, they become the binding measurement framework for that grant.
6. Positive Performance Incentives
V3.2 is enforcement-forward - which is right for accountability. But the framework should also reward builders who meaningfully outperform their targets. We’re working on a recognition and incentive layer for high-FES grantees: this includes priority consideration in future waves,public spotlights, opportunities for co-marketing, and a fast-track pathway into the Collective Builders program!
Thread is still open!
If you have input on any of the above, the thread is open until next week. If we all agree on these 6 points, the full post will be added by the end of next week as the new implemented and revised v3.2.2