Payload PR - BIP-289
The Gauge Adder v3 was deployed some time ago but only now has become usable after the introduction of the Authorizer Wrapper. This proposal grants the Maxi LM Multisig two roles - one for calling
addGnosisGauge and one for calling
addZksyncGauge. Note that we are not fully deployed on zkSync yet.
This will remove the need to involve the DAO Multisig when adding new gauges.
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.|
||For each change with changes, a transaction builder json named after said chain exists to apply the changes described in the tables.|
More information about the various Balancer Multisigs and their functions can be found in the multisig-ops repo
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.
For record, the contents of results_address_sorted.md are printed here:
This BIP is routine operation for provisioning a new factory. The new factories are themselves a risk mitigation.