Summary

This proposal configures LayerZero endpoints to enable secure cross-chain communication between Base and Sonic. Additionally, this proposal connects the following newly deployed Fleet(s) on Sonic to the Lazy Summer Protocol:

Fleet Deployments on Sonic

This proposal connect both Sonic and the following newly deployed Fleet(s) to the Lazy Summer Protocol:

Fleet: LazyVault_LowerRisk_USDCe

• Fleet Commander: 0x507A2D9E87DBD3076e65992049C41270b47964f8
• Buffer Ark: 0x809a0C98fac68a0c4319f3a3E864540C772562af
• Number of Arks: 3
  • Deposit Cap: 0
  • Minimum Buffer Balance: 100000000
  • Rebalance Cooldown: 600
  • Tip Rate: 1000000000000000000
• Ark Addresses:
  • 0x4D00D0dc44c4D6352C2bCb2228f2863e48cd53f4
  • 0xDa50CE93aaE2c764532E5B11Dc6378Af3330a817
  • 0x3002A7c8d5dC5CFaf81E747120B54D44bfAD5935

Motivation

Setting up these LayerZero routes is necessary to enable protocol governance and operations across chains, allowing for token bridging and cross-chain governance actions.

Specifications

Technical Details

• Hub Chain: base
• New Chain: sonic
• Deployer Address: 0xb0f758323d3798a6a567c1601d84f30d1bcaaa0b
• Number of Configurations: 4

Why These Configurations Matter

These LayerZero configurations establish the security parameters and message routing infrastructure that enable secure omnichain operations by:

1. Setting up trusted message libraries for cross-chain communication
2. Configuring Decentralized Verifier Networks (DVNs) for message integrity
3. Establishing appropriate gas parameters for message delivery

DVN Configuration

Each OApp will use LayerZero Labs DVN and Stargate DVN for cross-chain message verification. Learn more about LayerZero Security.

Configuration Summary

Configuration 1: Summer Token on Sonic

• OApp Address: 0x194f360D130F2393a5E9F3117A6a1B78aBEa1624
• Send Library: 0xB5320B0B3a13cC860893E2Bd79FCd7e13484Dda2
• Receive Library: 0xc70AB6f32772f59fBfc23889Caf4Ba3376C84bAf

Configuration 2: Summer Governor on Sonic

• OApp Address: 0xBE5A4DD68c3526F32B454fE28C9909cA0601e9Fa
• Send Library: 0xB5320B0B3a13cC860893E2Bd79FCd7e13484Dda2
• Receive Library: 0xc70AB6f32772f59fBfc23889Caf4Ba3376C84bAf

Configuration 3: Summer Token on Mainnet

• OApp Address: 0x194f360D130F2393a5E9F3117A6a1B78aBEa1624
• Send Library: 0xbB2Ea70C9E858123480642Cf96acbcCE1372dCe1
• Receive Library: 0xc02Ab410f0734EFa3F14628780e6e695156024C2

Configuration 4: Summer Token on Arbitrum

• OApp Address: 0x194f360D130F2393a5E9F3117A6a1B78aBEa1624
• Send Library: 0x975bcD720be66659e3EB3C0e4F1866a3020E493A
• Receive Library: 0x7B9E184e07a6EE1aC23eAe0fe8D6Be2f663f05e6

Peering Configuration

Peering Configuration

This proposal also configures the existing chains to peer with the new sonic chain:

• Token Peers: 3
• Governor Peers: 1

The peering is necessary to enable cross-chain message passing between existing chains and the newly deployed chain.

Security Considerations

• These configurations maintain the security of cross-chain communications
• All parameters have been carefully reviewed and tested
• Changes will execute through governance with the standard timelock period