# [BIP-910] Grant Permissions for New V3 Stable Pool and Weighted Pool Factories

- Space: [Aura Finance](https://snapshot.box/s:aurafinance.eth.md)
- Author: 0x021C5536bd60bCe9f15FB0E32746e332E3fbFAF4
- State: Closed
- Voting type: Weighted
- Start: 2026-02-13 19:00 UTC
- End: 2026-02-17 03:00 UTC
- Votes: 7
- Discussion: https://forum.balancer.fi/t/bip-910-grant-permissions-for-new-v3-stable-pool-and-weighted-pool-factories/6964
- Open in Snapshot: https://snapshot.box/#/s:aurafinance.eth/proposal/0x915a307de5a27d6debc28cc92797067bfe6d1950418edee87f24bb143dad97b6

## Results

- Yes, let's do it: 12,624,744.48 voting power, 100.0%
- No, this is not the way: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

## PR with Payload

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

## Summary

This proposal grants the necessary permissions for the newly deployed V3 pool factories across Mainnet, Arbitrum, Base, Avalanche, Plasma, HyperEVM, Optimism and Gnosis:

* `20260116-v3-stable-pool-v3` (StablePoolFactory)
* `20260115-v3-weighted-pool-v2` (WeightedPoolFactory)

Specifically, this BIP grants:

1. Omni Multisig (`0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e`): amplification parameter management permissions on the new StablePoolFactory
2. Emergency subDAO: factory disable permissions on both the new StablePoolFactory and WeightedPoolFactory

## Motivation

With the deployment of updated V3 pool factories (`20260116-v3-stable-pool-v3` and `20260115-v3-weighted-pool-v2`), the corresponding operational and emergency permissions need to be granted to ensure continuity of protocol operations.

## Specification

### Permissions to grant

#### Omni Multisig — `0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e`

From 20260116-v3-stable-pool-v3:

* `StablePool.startAmplificationParameterUpdate`
* `StablePool.stopAmplificationParameterUpdate`

#### Emergency subDAO

From 20260116-v3-stable-pool-v3:

* `StablePoolFactory.disable`

From 20260115-v3-weighted-pool-v2:

* `WeightedPoolFactory.disable`

### Networks

Mainnet, Arbitrum, Base, Avalanche, Plasma, HyperEVM, Optimism and Gnosis.

Emergency permissions are granted to the respective[ Emergency subDAO multisigs](https://docs.balancer.fi/concepts/governance/emergency.html#multisigs) on each network.

### Technical Details

On Mainnet, Arbitrum, Base, Avalanche, Optimism and Gnosis, the DAO multisig is admin and will call grantRoles on the respective Authorizer, passing the relevant action IDs and the target account (Omni or Emergency subDAO safe).

On HyperEVM and Plasma, the Omni multisig is admin and will directly grant roles to itself and the Emergency subDAO safe via the Authorizer.

The action IDs for each network can be verified in the[ balancer-deployments action-ids directory](https://github.com/balancer/balancer-deployments/tree/master/action-ids).

### Verification

* Deployment addresses:[ balancer-deployments address book](https://github.com/balancer/balancer-deployments/tree/master/addresses)
* Action IDs:[ balancer-deployments action-ids](https://github.com/balancer/balancer-deployments/tree/master/action-ids)
* Emergency subDAO safes:[ Balancer docs — Emergency subDAO](https://docs.balancer.fi/concepts/governance/emergency.html#multisigs)
* Payload builder:[ Permissions Payload Builder](https://balancer.defilytica.tools/payload-builder/permissions)

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

