• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
BalancerBalancerby0x7c2eA10D3e5922ba3bBBafa39Dc0677353D2AF17zen-maxi.eth

[BIP-660] Revise LayerZero Fraxtal Wire Up

Voting ended over 1 year agoSucceeded

https://github.com/BalancerMaxis/multisig-ops/pull/1156

Motivation:

When wiring up cross chain boosts in the past LayerZero would handle the OmniVotingEscrowChild, but in the case of Fraxtal it was not wired up as intended. This proposal is meant to transparently invoke the Maxi LM multisig on Fraxtal to set the trusted remote address on the child chain to accept messages from the mainnet OmniVotingEscrow contract. Once this is completed, veBAL holders, and wrappers, will be able to sync their balances to Fraxtal to reap the benefits of cross chain BAL incentives boosts.

Technical Specification:

The Balancer Maxi LM multisg on fraxtal:0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e will interact with the OmniVotingEscrowChild 0xE241C6e48CA045C7f631600a0f1403b2bFea05ad by writing the function setTrustedRemoteAddress with the following arguments:

_remoteChainId (uint16): 101

_remoteAddress (bytes): 0xE241C6e48CA045C7f631600a0f1403b2bFea05ad

Chain Id is verifiable here for Ethereum.

Off-Chain Vote

Yes, let's do it
2.58M veBAL100%
No, this is not the way
0 veBAL0%
Abstain
0 veBAL0%
Quorum:129%
Download mobile app to vote

Discussion

Balancer[BIP-660] Revise LayerZero Fraxtal Wire Up

Timeline

Jul 10, 2024Proposal created
Jul 11, 2024Proposal vote started
Jul 15, 2024Proposal vote ended
Feb 19, 2025Proposal updated