RFC: https://forum.summer.fi/t/rfc-operational-realignment-for-the-transition-period/875
1. Overview:
Revoke (or retarget to the Timelock) the onchain TipJar streams paying non-Treasury recipients (Foundation, Block Analitica, Labs, and Guardians) across all chains, so that 100% of any protocol tips accrue to the DAO treasury (the Timelock). This operationalizes the TipJar-consolidation direction flagged in https://forum.summer.fi/t/rfc-operational-realignment-for-the-transition-period/875, executed as a single-purpose treasury action with fully-decoded, Guardian-reviewed calldata.
Note: All tipJars have been shaken with the last accrual of the tips.
2. Motivation:
https://forum.summer.fi/t/rfc-operational-realignment-for-the-transition-period/875 set the transition thesis to stop paying for outcomes the DAO can no longer produce, and bring the flows and assets it still holds under the Timelock. It also explicitly parked one item for a dedicated proposal. Retargeting any non-Timelock tip stream is a genuine consolidation action that belongs in a treasury SIP, not in that RFC, and it asked for the live per-chain TipJar configuration (Ethereum, Base, Arbitrum, Sonic, HyperEVM) to be read and published first, checking each stream's recipient and any lockedUntilEpoch constraint. This SIP is that follow-up.
The rationale specific to the service-provider streams:
- Tip rates have already been zeroed on the offboarded Vaults, but the TipStream recipient configuration still exists onchain. Leaving standing streams to Foundation, @BlockAnalitica, Labs Co, and Guardians configured means any residual or future tip inflow would still be split away from the treasury.
- Each of these splits was designed for a growing, staffed protocol. Labs is winding down; the other mandates are being reviewed or restructured as part of the transition. Consolidating tips to the Timelock is consistent with the treasury-consolidation posture the DAO is already adopting.
- With any update/relaunch of the protocol the DAO can reinstate any/all relevant tipStreams again.
3. Specification:
| Parameter | Value |
|---|
| Action | Revoke / retarget non-Treasury tip streams to the Timelock |
| Recipients affected | Foundation, @BlockAnalitica, Labs, Guardians |
| Networks | Ethereum, Base, Arbitrum, Sonic, HyperEVM |
| Treasury (Timelock) | 0x447BF9d1485ABDc4C1778025DfdfbE8b894C3796 |
| Contract | TipJar per chain (see below) |
| Function | <remove/retarget TipStream |
| Lock handling | Respect lockedUntilEpoch; streams still locked are scheduled or handled in a follow-up (DAO Risk Managed Fleets) |
| Net effect | 100% of protocol tips accrue to the Timelock |
| Risk level | Low (config change; no user funds; no role grants) |
3.1 Execution
For each non-Timelock recipient stream identified in the published config, on each chain where it exists, submit the TipJar's stream removal/retarget call so the recipient is removed (or its share redirected to the Timelock). Two constraints to encode correctly:
- Lock epochs. Any stream with an unexpired
lockedUntilEpoch cannot be revoked/retargeted until it unlocks. Such streams are either scheduled for execution at unlock or carved into a follow-up sub-SIP; they are called out explicitly rather than silently skipped.
- This applies to DAO TipJar which is locked until 18th of February 2027.
3.2 Tip Stream Configuration
4. Risk Assessment:
- Technical: Removing or retargeting a stream is a configuration change on the TipJar; no user or vault funds are moved and no approvals are involved.
- Governance/security: Single-purpose, no role grants.
- Economic: Redirects a fee split back to the treasury; no market action, no depositor impact.
5. Voting:
If YES - Revoke / retarget the non-Treasury tip streams (Foundation, Block Analitica, Labs, Guardians) across all chains so 100% of protocol tips accrue to the Timelock, per the published per-chain TipJar config and decoded calldata, respecting lockedUntilEpoch constraints.
If NO - Leave the tip streams configured as they are.
