[BIP-430] Enable Layer Zero Cross Chain Boosts on Base

Governance General Proposal
1

PR with Payload

Motivation

With the recent move to enable the first wave of gauges on Base, it makes sense for cross chain boosts to be active on the network. As Base picks up steam, users will have an interest in receiving boost which will increase demand for veBAL. This also meets the status quo for all networks Balancer is deployed on, making the tokenomics homogenous for all network deployments.

Specification:

The DAO Multisig Base:0xC40DCFB13651e64C8551007aa57F9260827B6462 will interact with the Authorizer 0x809B79b53F18E9bc08A961ED4678B901aC93213a calling grantRole with the following arguments:

role: 0x033f3ebfdc58141797e7786a8115159707118fe37ae8f6d7b98929e4465349fb

which corresponds to the role for calling setDelegation on the l2-ve-delegation-proxy, verifiable here.

account: 0xC40DCFB13651e64C8551007aa57F9260827B6462

This grants the ability for the DAO Multisig to call that function.

The DAO Multisig Base:0xC40DCFB13651e64C8551007aa57F9260827B6462 will interact with the l2-ve-delegation-proxy 0xD87F44Df0159DC78029AB9CA7D7e57E7249F5ACD calling setDelegation with the following argument:

0xE42FFA682A26EF8F25891db4882932711D42e467

which corresponds to the l2-veboost-v2 contract.

The DAO Multisig Base:0xC40DCFB13651e64C8551007aa57F9260827B6462 will interact with the Authorizer 0x809B79b53F18E9bc08A961ED4678B901aC93213a calling renounceRole with the following arguments:

role: 0x033f3ebfdc58141797e7786a8115159707118fe37ae8f6d7b98929e4465349fb

which corresponds to the role for calling setDelegation on the l2-ve-delegation-proxy, verifiable here.

account: 0xC40DCFB13651e64C8551007aa57F9260827B6462

This removes the ability for the DAO Multisig to call that function.

1 Like
2

https://snapshot.org/#/balancer.eth/proposal/0x2d9b6dd5a4156d59f5f2fa18ecd549c0b16f987517714874ba1c1542191ae394

3

LayerZero had transferred ownership to the Maxi LM Multisig after the Base launch. This means for the messages to be properly passed from mainnet to base to permit veBAL balance syncing an additional transaction needed to be executed. In order to honor the timeline of the proposal this was done here. Typically this was not done through governance, as the dao was not in control of the contract, but proposals will be made for future networks.

The LM Multisig 0xc38c5f97B34E175FFd35407fc91a937300E33860 wrote the OmniVotingEscrow contract 0xE241C6e48CA045C7f631600a0f1403b2bFea05ad

Function: setTrustedRemoteAddress
remoteChainId: 184
remoteAddress: 0xE241C6e48CA045C7f631600a0f1403b2bFea05ad

1 Like