Balancer

PR with Payload

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

Summary

• Grant administrative privilege permissions to the Balancer Registry Initializer V2 contract to register and manage Balancer contracts in the registry
• Enable proper initialization of the Balancer Contract Registry on Avalanche, Optimism, and HyperEVM networks

Motivation

The Balancer Contract Registry is a critical infrastructure component that maintains a canonical list of all Balancer contracts and their aliases across different networks. This registry is essential for the proper functioning of the Balancer ecosystem, particularly for the deployment of LBP v2 pools.

The BalancerContractRegistryInitializer V2 has been deployed to networks where the initializer was not previously available (Avalanche, Optimism, and HyperEVM). These networks require a properly initialized registry to support LBP v2 deployments. To prevent circular dependencies, LBP contracts have been temporarily excluded from the initial registry population and will be added in subsequent updates.

The initializer contract requires specific permissions to populate the registry with the core Balancer contracts and establish proper contract aliases. Without these permissions, the registry cannot be initialized, blocking the deployment of new pool types and other ecosystem components.

Technical Specification

The respective DAO multi-sig on each chain will call the AuthorizerAdaptorEntrypoint and grant the following roles to the BalancerContractRegistryInitializer V2 contract:

• AVAX
• Optimism
• HyperEVM

Permissions to be granted:

• registerBalancerContract - Allows the initializer to register new Balancer contracts in the registry
• addOrUpdateBalancerContractAlias - Allows the initializer to create and update contract aliases for easier reference

Once permissions are granted, the initializer contract will execute its initialize() function to populate the registry with the core Balancer contract deployments for each respective network.

This permission grant is temporary and specific to the initialization process. After successful initialization, the standard governance processes will manage future registry updates