Payload PR - BIP-253

Background

The v4 Weighted Pool Factory and the v4 Composable Stable Pool Factory were deployed to allow the use of create2 instead of create. The v2 Managed Pool Factory allows using create2, adds reentrancy protection, and has various other improvements. Some initial “wire-up” of permissions is required to bring them into standard function. This BIP lays out these changes and requests permission to apply them.

English Specification

The transaction details were generated by this script with inputs and outputs in this directory

The following files can be found both linked below and in the payload PR linked above:

Filename	Description of Contents
inputs.json	The inputs to the script mapping functions and deployments to target addresses that can execute them.
results_address_sorted.md	The resulting changes printed in a table sorted by target chain and target address. (to easily understand permisisons granted)
results_deployment_sorted.md	The resulting changes printed in a table sorted by target chain and target deployment. (for verification against action ids)
function_descriptions.md	A table that describes what each function that is being granted privileged access to allows.
chainname.json	For each change with changes, a transaction builder json named after said chain exists to apply the changes described in the tables.

In the tables above:

The “emergency” caller group:

• maps to the Balancer Emergency DAO Multisig as defined in this vote.

The “feeManager” caller group:

• maps to the feeManager multisig controlled by the Balancer Maxis on all chains except mainnet.
• On mainnet a special feeSetter multisig exists to manage a-factors and a gautletFeeSetter contract that allows bulk changing of fees.
• The maxi’s functionally control all contracts that make up the feeManager target group.

More information about the various Balancer Multisigs and their functions can be found in the multisig-ops repo

Specification

As described in the payload json, the authorizer will be called to grant the roles as described.

The change can be reviewed by the below by comparing the results_deployment_sorted.md file to the source of truth, which should match the order found in the source of truth for actionIds on the balancer-v2-monorepo.

The overview table can be consulted on the Balancer forum (based on the snapshot character limit)