SIP5.1: Multi-Chain TipJar Update
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.
Newly deployed TipJar contracts:
base: 0xAd30bc7E40f13d88EDa608A5729d28151FcAA374
arbitrum: 0xBeB68a57dF8eD3CDAE8629C7c6E497eB1b6b1C47
mainnet: 0x2d1A2637c3E0c80f31A91d0b6dbC5a107988a401
Specifications
Actions
On base:
Register TipJar address with ConfigurationManager
Configure tip streams with corrected allocation values
Send cross-chain proposal to arbitrum to:
Register TipJar address with ConfigurationManager
Configure tip streams with corrected allocation values
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, Allocation 30000000000000000000 (30%), Min Term 63072000 seconds (730.00 days)
Stream 2: Recipient 0xB0F53Fc4e15301147de9b3e49C3DB942E3F118F2, Allocation 20000000000000000000 (20%), Min Term 7776000 seconds (90.00 days)
Stream 3: Recipient 0xeaef8fb615a7d5ab6a356dec0549fd749460e970, Allocation 20000000000000000000 (20%), Min Term 31536000 seconds (365.00 days)
1 Like
Hey, thanks for this proposal. Could anyone please point to some documentation around the recipients?
0x6e7aE26175F9972e266B0e39288108597C152604
- summer.fi / oazo
0xB0F53Fc4e15301147de9b3e49C3DB942E3F118F2
- lazy summer foundation
0xeaef8fb615a7d5ab6a356dec0549fd749460e970
- block analitica
1 Like
Great, thanks. What happens to the remainder? 30 + 20 + 20 = 70. Does that stay inside the TipJar?
The remainder is routed to the treasury (timelock) on a given chain.
amount = withdrawnAssets.applyPercentage(allocation);
}
if (amount > 0) {
underlyingAsset.safeTransfer(recipient, amount);
totalDistributed += amount;
}
}
// Transfer remaining balance to treasury
uint256 remaining = withdrawnAssets - totalDistributed;
if (remaining > 0) {
underlyingAsset.safeTransfer(treasury(), remaining);
}
emit TipJarShaken(address(fleetCommander), withdrawnAssets);
}
/**
* @notice Shakes multiple fleet commanders
* @param fleetCommanders An array of fleet commander addresses to shake
1 Like
The TipJar tip stream correction proposal is now live.
As stated above. The initial streams were incorrectly configured at launch. This proposal corrects that error.
It replaces the existing TipJar’s on Base, Arbitrum and Mainnet and correctly configures tip streams on each.
Tip stream recipients are as follows:
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)