• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Stake DAO BALStake DAO BALby0xb4542526AfeE2FdA1D584213D1521272a398B42a0xb454…B42a

[BIP-749] Grant `add_reward` Permissions to Maxis’ Omnichain Multisig

Voting ended over 1 year agoFailed

PR with Payload

https://github.com/BalancerMaxis/multisig-ops/pull/1612

Motivation

The action of whitelisting a custom reward token on a gauge is permissioned. Doing it through the DAO multisig for every partner/gauge/token is not feasible, hence BIP-387 requested permission for calling add_reward through the authorizer from the Maxis’ multisig.

The Maxis are however in the process of migrating their multisig to the so-called omnichain multisig, a multisig that has the same address on all chains. Over time it will replace the old one. In a lot of cases it already has replaced it; this permission is one of the last things that keeps the Maxis from moving over fully.

Specification

On Ethereum, the DAO multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will call grantRole(bytes32,address) on the authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 with the following arguments:

  • role: 0x3bf29175652a3f0fac5abb715d0b7fe2e7b597e2e2eff555dac6b21a20a7c83e (ref)
  • account: 0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e (ref)

It will perform the same action on all other chains where the omnichain multisig is deployed and does not have these permissions yet: Arbitrum, Avalanche, Base, Gnosis, Optimism and Polygon.

Off-Chain Vote

Yes, let's do it
0 sdBAL0%
No, this is not the way
0 sdBAL0%
Abstain
0 sdBAL0%
Download mobile app to vote

Timeline

Dec 19, 2024Proposal created
Dec 19, 2024Proposal vote started
Dec 21, 2024Proposal vote ended
Dec 21, 2024Proposal updated