Uniswap Governance Executes Unleashed Treasury Proposal With 60.4M Yes Votes

“Uniswap Unleashed” Execution on the Record

Treasury tokens at Uniswap do not move because holders vote yes. A community vote is one step in a chain that ends with an executed on-chain transaction, and the record for the 2025 “Uniswap (UNI) Unleashed” proposal shows exactly where that chain stands. The governance vote record lists 60,416,652 votes in favor and 4,405,601 against, a spread wider than 13 to 1, and the proposal is marked as executed. The same record shows what the measure was built to do: its payload contains calls to the UNI token's transfer function, each naming a recipient wallet address and a quantity of UNI to send. The proposal text set out a budget request for the foundation's grants and operating costs, so the disbursement question comes down to whether those transfer calls ran and to which addresses the tokens went. That is a mechanical check, not an interpretive one. The executed transaction has to be opened and its recipients and amounts compared line by line against the proposal text, because the vote tally alone authorizes rather than pays. On-chain explorers make that comparison public: every executed call resolves to a destination and a token amount, both of which can be checked against the proposal before any payout is reported as fact. A yes result tells the protocol what it may do; it does not tell an observer that tokens left the treasury. Uniswap (UNI) holders supplied the votes, but the treasury contract holds the tokens, and only its own functions release them. Uniswap itself is the largest DEX by trading volume, running as an AMM, an automated market maker that prices swaps against pooled balances, with concentrated liquidity shaping how positions are organized inside each pool. None of that market machinery moves treasury funds on a ballot. The only path out is the transfer function the proposal calls, and the only proof of payment is the execution receipt attached to a specific transaction.

Forum Post, Temperature Check, Timelock

The route a Uniswap proposal travels is fixed by the protocol's governance documentation. It starts in public discussion: the author posts the draft on the governance forum and collects feedback there before anything else happens. The next gate is the temperature check, an off-chain vote run through snapshot that measures whether the community wants the item to advance at all. Whatever its result, it moves no tokens; its job is to decide whether the idea reaches the on-chain stage. Execution rights attach only to that stage. The proposal submitted on-chain carries the code meant to run, and when the yes count clears the required threshold the action enters a queue, where it waits out a delay before anyone can trigger it. Only then does the transaction execute, which is why the process documents treat approved, passed and executed as three separate states rather than synonyms. That separation is what makes verification possible in the first place. The check runs in a fixed order: the recipient addresses and amounts written into the proposal, confirmation that the on-chain vote passed, then the executed transaction record. A canceled payout at Ampleforth DAO shows why the last step cannot be skipped. That proposal carried a payout figure in its own text and was withdrawn without a vote or any movement of funds, leaving the allocation as words on a page. Allocated and executed are different numbers, and only the second one describes money that moved. The same discipline applies to any protocol treasury, including this one. Our earlier reporting tracked the demand side of the network from another angle: growth at a 4-year high with 2,295 new UNI wallets. Participation of that kind raises the number of eyes on governance, but it changes none of the mechanics above: votes authorize, the queue delays, and the transaction alone disburses.

Our reading: the 60,416,652 to 4,405,601 result makes passage unambiguous, but the vote is the middle of this story, not the end. What the proposal authorized and what each budget line actually received are separate facts, and only the executed transfer record separates them. The treasury sits behind an exchange protocol whose hooks link 7 external liquidity sources across 3 networks. The milestone also lands with Uniswap (UNI) down more than 20% from its $10.22 Sept 22 peak; readers tracking the market side can follow our UNI technical analysis. The outstanding item on the governance side is narrow: match the executed transaction's recipient addresses and UNI quantities against the proposal text. Until that comparison is published, the disbursement stands exactly as filed, executed on the record and unverified in payment.