PR with Payload
Motivation
The previous checkpointer contract automated the process which should ensure L2 BAL is bridged promptly every week going forward. Since then the new gauge factories on L2s have required manual interaction in order to facilitate the actions. A new gauge checkpointer is proposed to be given the proper permissions to handle all different root gauge factories, add new gauges as needed, and perform multiple checkpoints in a single call.
Specification
If approved, the DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will initiate a transaction to interact with the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 calling grantRole with the following arguments:
role: 0x3f63974a377ba4713661ede455bceda6686a0395f8b8ed8701ad1f13bb926c4d
which corresponds to the role for calling checkpoint on the gauges, verifiable here.
account: 0x0C8f71D19f87c0bD1b9baD2484EcC3388D5DbB98
which corresponds to the address for the l2-gauge-checkpointer-v2 verifiable here .
Additionally, to ensure backwards compatibility with any gauges created from old factories the Maxi LM Multisig will be granted the role to call addGaugesWithVerifiedType on the l2-gauge-checkpointer-v2. It’s not likely this will be needed though since the L2 migration should have brought everything up to the latest version.
The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will initiate a transaction to interact with the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 calling grantRole with the following arguments:
role: 0x54f43cdb53a74c7bd91359b21ad8cd82a6a41b6ff8718aea74f1d2b9292c6b41
which corresponds to the role for calling addGaugesWithVerifiedType on the checkpointer, verifiable here .
account: 0xc38c5f97B34E175FFd35407fc91a937300E33860
which corresponds to the Maxi LM Multisig.