maxyz.xyz posted BIP-936 to the Balancer forum on 20 October 2026, spelling out the exact multisig calls, pauses and fee changes that execute the shutdown BAL holders had already approved a month earlier under BIP-928. Its Snapshot vote closed 27 October 2026 with effectively all voting power For.
Voting power, not people: 30 votes cast.
maxyz.xyz posted [BIP-936] Onchain Wind-down of Protocol: Specs to the Balancer forum on 20 October 2026, laying out the multisig calls, pause steps and fee changes that carry out the shutdown of Balancer that BAL holders had already approved a month earlier. Its Snapshot vote closed 27 October 2026 with about 6.3 million BAL of voting power For; the No option drew 0.005 BAL. The wind-down itself was decided separately: BIP-928, Orderly Winddown of Balancer and Distribution of the Treasury, posted by Marcus on 14 September 2026 and approved by Snapshot vote running 25 to 29 September 2026. BIP-936 does not reopen that decision; it specifies how the pauses, fee changes and permission revocations BIP-928 called for are actually executed onchain, which matters because it is the mechanism that moves Balancer from a running protocol to a paused one with no privileged access left.
0x4BC8121278056BFCaC2BD14D455659224d6dDf48.BIP-936 itself carries no rationale beyond the steps it lists; the case for the wind-down was made in BIP-928. There, Marcus argued that holding the line further only cost the treasury without changing the outcome: "That treasury belongs to BAL holders. The question is whether what remains reaches holders while it is still substantial, or is spent first on a path that has already been tried." The same post describes the restructuring that preceded this proposal: "With a working product suite, a lean structure and full effort from everyone who stayed, the traction the plan required did not come."
The Snapshot vote on BIP-936 ran 23 to 27 October 2026 and closed with about 6,306,479 BAL of voting power For, 0.005 BAL against and none abstaining, from 30 votes, against a quorum of 5,000,000 BAL. The first dated steps fall on 30 October 2026, which is both the day v2 protocol fees are set to zero under BIP-936 and the withdrawals-only date BIP-928 named. After that comes the 30 November 2026 pause of the v3 Vault and its buffers, followed by the permission revocations and the first treasury redemption round, which BIP-928 opens on 31 May 2027.
This page was researched from Alphaday’s DAO proposal and governance forum feeds. They are open: free, no signup, no key.
Start building with the DAO proposals API
A 15-minute recipe: forty lines and a cron entry.
The same feeds as tools, for Claude, Cursor and any MCP client.
The discussion threads that come before the votes.
Stage and vote as read on 28 October 2026. Proposals move after a page is written; the forum thread and the vote have the current state. Quotes are from the posts linked beside them.