# \[BIP-289\] Grant Maxis Permissions to Add Gnosis & zkSync Gauges

**URL:** <https://forum.balancer.fi/t/bip-289-grant-maxis-permissions-to-add-gnosis-zksync-gauges/4756>\
**Category:** General Proposal\
**Created:** [May 10, 2023, 11:17am UTC](https://forum.balancer.fi/t/bip-289-grant-maxis-permissions-to-add-gnosis-zksync-gauges/4756 "2023-05-10T11:17:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![solarcurve](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/solarcurve/32/1487_2.png) [@solarcurve](https://forum.balancer.fi/u/solarcurve)\
**Post date:** [May 10, 2023, 11:17am UTC](https://forum.balancer.fi/t/bip-289-grant-maxis-permissions-to-add-gnosis-zksync-gauges/4756/1 "2023-05-10T11:17:37Z")

</div>

## [Payload PR - BIP-289](https://github.com/BalancerMaxis/multisig-ops/pull/174)

## Background

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.

## English Specification

The transaction details were generated by [this script](https://github.com/BalancerMaxis/multisig-ops/blob/main/tools/python/gen_add_permissions_payload.py) with inputs and outputs in [this directory](https://github.com/BalancerMaxis/multisig-ops/tree/staging/BIPs/BIP-289)

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

| Filename | Description of Contents |
| --- | --- |
| [inputs.json](https://github.com/BalancerMaxis/multisig-ops/blob/staging/BIPs/BIP-289/inputs.json) | The inputs to the script mapping functions and deployments to target addresses that can execute them. |
| [results\_address\_sorted.md](https://github.com/BalancerMaxis/multisig-ops/blob/staging/BIPs/BIP-289/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](https://github.com/BalancerMaxis/multisig-ops/blob/staging/BIPs/BIP-289/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](https://github.com/BalancerMaxis/multisig-ops/blob/staging/BIPs/BIP-289/function_descriptions.md) | A table that describes what each function that is being granted privileged access to allows. |
| [`chainname`.json](https://github.com/BalancerMaxis/multisig-ops/tree/staging/BIPs/BIP-289/) | 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](https://github.com/BalancerMaxis/multisig-ops/blob/staging/multisigs.md)_

# 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](https://github.com/BalancerMaxis/multisig-ops/tree/staging/BIPs/BIP-183/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](https://github.com/balancer-labs/balancer-v2-monorepo/tree/master/pkg/deployments/action-ids).

For record, the contents of [results\_address\_sorted.md](https://github.com/BalancerMaxis/multisig-ops/tree/staging/BIPs/BIP-289/results_address_sorted.md) are printed here:

| deployment | chain | function | role | target | target\_address |
| --- | --- | --- | --- | --- | --- |
| 20230109-gauge-adder-v3 | mainnet | addGnosisGauge(address) | 0xe818738e338905496f604a2a26c7ca754558870a3810786cfbb89ae28d262dc5 | lm | 0xc38c5f97B34E175FFd35407fc91a937300E33860 |
| 20230109-gauge-adder-v3 | mainnet | addZKSyncGauge(address) | 0x010cab59e1860b78f8f67210e267d2c06d77c17b4529f007c7c8acee11ea2fe0 | lm | 0xc38c5f97B34E175FFd35407fc91a937300E33860 |

## Risk Assessment

This BIP is routine operation for provisioning a new factory. The new factories are themselves a risk mitigation.

## References

[Monorepo Deployment Addresses](https://github.com/balancer-labs/balancer-v2-monorepo/tree/master/pkg/deployments)

---

<div class="post-metadata">

**Author:** ![solarcurve](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/solarcurve/32/1487_2.png) [@solarcurve](https://forum.balancer.fi/u/solarcurve)\
**Post date:** [May 10, 2023, 7:47pm UTC](https://forum.balancer.fi/t/bip-289-grant-maxis-permissions-to-add-gnosis-zksync-gauges/4756/2 "2023-05-10T19:47:02Z")

</div>

[https://snapshot.org/#/balancer.eth/proposal/0x23f6e8f79a88c7a94ada7b303a6d74aca1318b15f4e0def8910b8052f0bfc694](https://snapshot.org/#/balancer.eth/proposal/0x23f6e8f79a88c7a94ada7b303a6d74aca1318b15f4e0def8910b8052f0bfc694)