DAOs Graduate From Treasury Votes to Protocol Controllers: Uniswap, Maker, Cardano
Three major DAOs are shifting governance from binary treasury allocations to programmable fee logic, execution batching, and hard-fork naming—signaling a maturation of on-chain governance as an operational layer.
Governance across three major protocols is moving past binary treasury votes toward programmable, operational mechanisms. Uniswap’s July 2026 fee-rollout proposal introduces a V4 Fee Controller that computes protocol fees deterministically by pool family, replacing per-pool configuration [^claim_2356]. The controller runs on a curve: alpha + beta × (lpFee - floor), floored to the nearest 0.01bp increment [^claim_2360]. A 0.03 LP fee maps to a 0.01 protocol fee; a 100 LP fee maps to a 10 protocol fee [^claim_2360]. This design exists because v4’s hook architecture creates potentially infinite LP fee tiers and dynamic fees [^claim_2356]. The proposal activates fees on only three pool families—static fee pools, CCA pools, and aggregator hook pools—and explicitly excludes all others [^claim_2357]. For aggregator hooks, a 25x multiplier lets the protocol fee exceed the PoolManager’s 10bps hard cap, hitting 250bps [^claim_2358]. The rollout is tight: Snapshot July 7–12, 2026, onchain vote starting July 13, 2026, split into two parallel votes because GovernorBravo has a 10-action limit [^claim_2361]. This follows a record burn of 186,000 UNI in one day from v2/v3 fees already live on 11 chains [^claim_2359].
Maker’s governance shows similar operational maturity. A July 16, 2026 executive proposal passed with 6,599,246,345 SKY supporting and became executable on July 20, 2026 [^claim_2362]. It bundled the monthly settlement cycle for June 2026, LSSKY-SKY rewards normalization, RWA001-A offboarding, emergency spells for STUSDS_MOM, and whitelisting the new Osero ALMProxy [^claim_2363]. Separately, a July 13, 2026 Atlas edit poll passed with 7,022,448,841 SKY supporting, clearing the 480,000,000 SKY Minimum Positive Participation threshold [^claim_2364][^claim_2365]. That poll amended governance mechanics including timeliness requirements for aligned delegate voting, the Sky Frontier Foundation multisig address, and moving SkyLink Bridges from Governance Scope to Protocol Scope [^claim_2365].
Cardano’s governance model differs but is equally operational. Its 2026 hard-fork naming vote opened January 13, 2026 and closes February 14, 2026; participating DReps must lock a minimum deposit of 100,000 ADA [^claim_2366]. As of publication, 18 DReps had voted: Yes at ~850.11M ADA, No at ~4.95B ADA, and Abstain at ~8.36B ADA, with no SPO votes recorded [^claim_2367]. The upgrade itself—Protocol Version 11—is an intra-era hard fork in the Conway ledger era, targeting reference input rules, VRF key uniqueness, and Plutus primitives to lower script execution costs and increase reliability [^claim_2368].
These three cases share a common thread: governance is becoming a technical steering mechanism. Uniswap’s fee controller is a programmable on-chain primitive; Maker’s executive bundles are execution batching; Cardano’s hard-fork vote is a weighted, locked-participation upgrade process. DAOs are no longer just allocating treasuries—they are designing protocol controllers, timelocks, and scope reclassification as the primary governance actions.
Provenance ledger
13 claims web-citedEvery claim below cites a source URL, and each URL was checked for validity before publish. The excerpt shown is the researcher's own summary of the page — it is not re-derived from the source, so it is not a verified verbatim quote. Follow the link to confirm any claim against the original. Citation markers in the text jump here.
[1] Uniswap’s July 2026 fee-rollout proposal introduces a **V4 Fee Controller** that computes protocol fees by pool family instead of setting fees pool-by-pool, because v4 hooks allow potentially infinite distinct LP fee tiers and fees can change dynamically from block to block. web-cited
“v4’s hook architecture requires a different approach to fee activation… Hooks mean v4 has potentially infinite distinct LP fee tiers, and a pool’s fees can change dynamically from one block to the next. To manage this, we propose a V4 Fee Controller system…”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[2] The Uniswap v4 fee proposal activates fees only for three pool families: **static fee pools**, **CCA pools**, and **aggregator hook pools**; it explicitly says no other v4 pools are enabled. web-cited
“This proposal activates fees on three pool families…” and “This proposal does not enable the protocol fee for any pools other than those in the Families mentioned above.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[3] For aggregator hook pools, the proposal uses a **25x multiplier** so the protocol can exceed the PoolManager’s hard cap of **10bps**, producing a cap of **250bps** for those hooks; the proposed family defaults are **10bp** and **3bp** on Base for the family default, with lower stable-pair overrides. web-cited
“To maintain the option of charging more on this external flow than the v4 PoolManager’s hard cap of 10bps, aggregator hooks will multiply their assigned fees by 25, allowing for a cap of 250bps.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[4] The same Uniswap proposal states that protocol fees are already live across all **v2 and v3 pools on 11 chains** and says the rollout had produced a record burn of **186,000 UNI in one day** in the prior month. web-cited
“Protocol fees are now live across all v2 and v3 pools on 11 chains… Last month, the protocol set a record burning 186,000 UNI in one day.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[5] The Uniswap v4 fee controller defines a deterministic curve where protocol fees are computed as **alpha + beta × (lpFee - floor)** and floored to the nearest **0.01bp** increment; the table specifies, for example, **0.03 LP fee → 0.01 protocol fee** and **100 LP fee → 10 protocol fee**. web-cited
“Inside any range, the fee is: alpha + beta * (lpFee - floor). The output is floored to the nearest 0.01bp increment…” plus the table entries “0.03 | 0.01” and “100 | 10.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[6] Uniswap’s rollout schedule for v4 fees is **Snapshot: July 7-12, 2026** and **onchain vote starting the week of July 13, 2026**; because GovernorBravo limits proposals to **10 actions**, the team said it would split the onchain execution into **two parallel votes**. web-cited
“Snapshot: July 7-12, 2026” and “Onchain vote: Starting the week of July 13, 2026” and “because of GovernorBravo’s limit of 10 actions per proposal, there will be two separate onchain votes posted in parallel…”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[7] Maker Governance’s July 16, 2026 executive proposal passed with **6,599,246,345 SKY Supporting** and became **available for execution on Jul 20 2026 14:00 UTC**. web-cited
“6,599,246,345 SKY Supporting” and “Passed on Jul 17 2026 14:41 UTC. Available for execution on Jul 20 2026 14:00 UTC.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[8] That Maker executive bundled multiple treasury and protocol actions in one vote, including the **monthly settlement cycle for June 2026**, **LSSKY-SKY rewards normalization**, **RWA001-A offboarding**, **emergency spells** for STUSDS_MOM, and whitelisting the new **Osero ALMProxy**. web-cited
“Execute the Monthly Settlement Cycle for June 2026… normalize LSSKY-SKY staking rewards, complete the offboarding of RWA001-A, add emergency spells… whitelist the new Osero ALMProxy…”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[9] Maker’s July 2026 governance polls used a **Minimum Positive Participation** threshold of **480,000,000 SKY** for Atlas edit proposals; if **Yes** exceeds **No** and meets that threshold, the associated pull request is merged into **The Atlas**. web-cited
“The Minimum Positive Participation for Atlas Edit Weekly Cycle Proposals is currently set to 480,000,000 SKY… If the votes for the 'Yes' option exceed the votes for the 'No' option AND the votes for the 'Yes' option equal or exceed 480,000,000 SKY, then… The associated Pull Request will be merged into The Atlas.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[10] The July 13, 2026 Maker Atlas edit poll passed with **7,022,448,841 SKY supporting** and amended governance mechanics including timeliness requirements for aligned delegate voting, the Sky Frontier Foundation multisig address, and moving SkyLink Bridges from Governance Scope to Protocol Scope. web-cited
“Winning option: Yes with 7,022,448,841 SKY supporting.” and the proposal text listing the changes to voting participation, foundation multisig, and SkyLink Bridges scope.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[11] Cardano’s 2026 hard-fork naming vote opened on **January 13, 2026** and remains open until **February 14, 2026**; participating DReps must lock a minimum deposit of **100,000 ADA** to vote. web-cited
“The naming proposal entered voting on January 13, 2026, and remains open until February 14, 2026. Participating DReps must lock a minimum deposit of 100,000 ADA to cast a vote.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[12] As of the Cardano article’s publication, **18 DReps** had voted; **Yes** represented about **850.11 million ADA**, **No** about **4.95 billion ADA**, and **Abstain** about **8.36 billion ADA**, with no SPO votes recorded. web-cited
“As of publication, 18 DReps have voted. Yes votes account for roughly 850.11 million ADA… No votes represent about 4.95 billion ADA… Abstain votes approximately 8.36 billion ADA… SPO participation remains inactive so far, with no votes recorded…”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[13] The article says Cardano Protocol Version 11 is an **intra-era hard fork** in the Conway ledger era and targets **reference input rules**, **VRF key uniqueness**, and **Plutus primitives**, with the stated goal of lowering script execution costs and increasing reliability. web-cited
“Protocol Version 11 is designed as an intra-era hard fork… Planned changes refinements to reference input rules, VRF key uniqueness, and Plutus primitives. The update also targets lower script execution costs and higher reliability for builders.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.