Motivation
Since the launch of veBAL there has been weekly manual actions required to “checkpoint” L2 root gauges and trigger the bridging of BAL. This contract automates that process which should ensure L2 BAL is bridged promptly every week going forward.
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: 0x343688C5cB92115a52cA485af7f62B4B7A2e9CcC
which corresponds to the address for the l2-gauge-checkpointer 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. 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: 0x1b6c47bfcba58391eb7c8e74ea3c377e0d6c62825a6184d59c4478e225110fd4
which corresponds to the role for calling checkpoint on the gauges, verifiable here.
account: 0xc38c5f97B34E175FFd35407fc91a937300E33860
which corresponds to the Maxi LM Multisig.