Summary

This proposal updates TipJar configurations across all active chains in the Lazy Summer Protocol ecosystem by registering updated TipJar instances with each chain's ConfigurationManager and setting up proper tip streams.

Motivation

Properly configured TipJars are essential for the protocol's revenue distribution mechanisms. This proposal corrects the tipstream allocations that were set too low during the initial launch, ensuring that revenue distribution operates as intended.

Newly deployed TipJar contracts:

• base: 0xAd30bc7E40f13d88EDa608A5729d28151FcAA374
• arbitrum: 0xBeB68a57dF8eD3CDAE8629C7c6E497eB1b6b1C47
• mainnet: 0x2d1A2637c3E0c80f31A91d0b6dbC5a107988a401

Specifications

Actions

1. On base:
   • Register TipJar address with ConfigurationManager
   • Configure tip streams with corrected allocation values
2. Send cross-chain proposal to arbitrum to:
   • Register TipJar address with ConfigurationManager
   • Configure tip streams with corrected allocation values
3. Send cross-chain proposal to mainnet to:
   • Register TipJar address with ConfigurationManager
   • Configure tip streams with corrected allocation values

Tip Streams Configuration

• Stream 1: Recipient 0x6e7aE26175F9972e266B0e39288108597C152604 (SUMMER.FI / OAZO), Allocation 30000000000000000000 (30%), Min Term 63072000 seconds (730.00 days)
• Stream 2: Recipient 0xB0F53Fc4e15301147de9b3e49C3DB942E3F118F2 (LAZY SUMMER FOUNDATION), Allocation 20000000000000000000 (20%), Min Term 7776000 seconds (90.00 days)
• Stream 3: Recipient 0xeaef8fb615a7d5ab6a356dec0549fd749460e970 (BLOCK ANALITICA), Allocation 20000000000000000000 (20%), Min Term 31536000 seconds (365.00 days)