• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
BalancerBalancerby0x7c2eA10D3e5922ba3bBBafa39Dc0677353D2AF17zen-maxi.eth

[BIP-707] Kill Shezmu Gauges

Voting ended over 1 year agoSucceeded

PR with Payload https://github.com/BalancerMaxis/multisig-ops/pull/1381

Motivation

On Friday the 20th of September the Shezmu protocol was hacked and shezUSD was drained by a collateral minting exploit allowing the hacker to borrow an arbitrary amount of shezUSD. As a result shezETH trading was paused by the Emergency SubDAO.

Given both tokens have been victims of exploits we propose to kill the corresponding gauges:

Network Pool Gauge
Mainnet sDAI:ShezUSD 0xa71adac76a2e34f8f988fa6992e3bdad08d92c01
Mainnet ShezETH:wstETH 0xb002073210698b0852e34da6a5e432a04d299205

Technical Specification

The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using 0xab8f0945 for the data(bytes) argument and 0xa71adac76a2e34f8f988fa6992e3bdad08d92c01 as well as 0xb002073210698b0852e34da6a5e432a04d299205 as the root gauge addresses for the sDAI:ShezUSD and ShezETH:wstETH pools.

Off-Chain Vote

Yes, let's do it
2.98M veBAL100%
No, this is not the way
0 veBAL0%
Abstain
0 veBAL0%
Quorum:149%
Download mobile app to vote

Discussion

Balancer[BIP-707] Kill Shezmu Gauges

Timeline

Sep 26, 2024Proposal created
Sep 26, 2024Proposal vote started
Sep 30, 2024Proposal vote ended
Feb 19, 2025Proposal updated