# \[SIP5.13\] Multi-chain Foundation Roles Setup **URL:** \ **Category:** Summer Improvement Proposals \[SIPs\]\ **Tags:** sip5, governance, governor, foundation\ **Created:** [November 5, 2025, 6:29pm UTC](https://forum.summer.fi/t/sip5-13-multi-chain-foundation-roles-setup/452 "2025-11-05T18:29:47Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![chrisb](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/chrisb/32/28_2.png) [@chrisb](https://forum.summer.fi/u/chrisb)\ **Post date:** [November 5, 2025, 6:29pm UTC](https://forum.summer.fi/t/sip5-13-multi-chain-foundation-roles-setup/452/1 "2025-11-05T18:29:47Z")
### 1. Overview: This proposal grants core governance roles to the ‘Lazy Summer Foundation’ multisig at `0xB0F53Fc4e15301147de9b3e49C3DB942E3F118F2` across all active chains in the Lazy Summer Protocol ecosystem. Secondly, it is asking the Lazy Summer Foundation to use it’s governance role to Whitelist the new Staking Contract on the SUMR token contract on the Base Network, in order to enable the new SUMR staking module. * * * ### 2. Motivation: As part of the RFC to upgrade Governance and Staking to new versions, in order to prepare for the transferability of SUMR, we would like to propose giving the Lazy Summer Foundation governance roles via their multisig to act as a fallback and to create a more efficient upgrade process. The Foundation multisig requires specific roles to manage protocol governance and timelock operations: - GOVERNOR\_ROLE in ProtocolAccessManager for protocol-wide governance - PROPOSER\_ROLE, EXECUTOR\_ROLE, CANCELLER\_ROLE, and DEFAULT\_ADMIN\_ROLE in SummerTimelockController for timelock management ## Target Address Foundation Multisig: 0xB0F53Fc4e15301147de9b3e49C3DB942E3F118F2 * * * ### 3. Specification: ### Actions 1. On base: - Grant GOVERNOR\_ROLE in ProtocolAccessManager - Grant PROPOSER\_ROLE in SummerTimelockController - Grant EXECUTOR\_ROLE in SummerTimelockController - Grant CANCELLER\_ROLE in SummerTimelockController - Grant DEFAULT\_ADMIN\_ROLE in SummerTimelockController 1. Send cross-chain proposal to arbitrum to: - Grant GOVERNOR\_ROLE in ProtocolAccessManager - Grant PROPOSER\_ROLE in SummerTimelockController - Grant EXECUTOR\_ROLE in SummerTimelockController - Grant CANCELLER\_ROLE in SummerTimelockController - Grant DEFAULT\_ADMIN\_ROLE in SummerTimelockController 1. Send cross-chain proposal to mainnet to: - Grant GOVERNOR\_ROLE in ProtocolAccessManager - Grant PROPOSER\_ROLE in SummerTimelockController - Grant EXECUTOR\_ROLE in SummerTimelockController - Grant CANCELLER\_ROLE in SummerTimelockController - Grant DEFAULT\_ADMIN\_ROLE in SummerTimelockController 1. Send cross-chain proposal to sonic to - Grant GOVERNOR\_ROLE in ProtocolAccessManager - Grant PROPOSER\_ROLE in SummerTimelockController - Grant EXECUTOR\_ROLE in SummerTimelockController - Grant CANCELLER\_ROLE in SummerTimelockController - Grant DEFAULT\_ADMIN\_ROLE in SummerTimelockController ## Technical Details **GOVERNOR\_ROLE** : Grants protocol-wide administrative privileges in the ProtocolAccessManager **PROPOSER\_ROLE** : Allows proposing operations to the TimelockController **EXECUTOR\_ROLE** : Allows executing operations in the TimelockController **CANCELLER\_ROLE** : Allows cancelling operations in the TimelockController **DEFAULT\_ADMIN\_ROLE** : Grants admin privileges in the TimelockController, allowing role management" * * * ### 4. Risk Assessment: - The main risk here is providing a multisig with sweeping governance powers during the transition from Governance V1 to V2. * * * ### 5. Voting: By voting YES to this SIP, you will be voting FOR granting core governance roles, as decribed above, to the Lazy Summer Foundation multisig. As well as granting roles, you will also be using the grant of roles to further instruct the Lazy Summer Foundation to use it’s newly granted governance rights to whitelist the new SUMR staking contract on the SUMR Token contract on the Base Network, thus enabling the new SUMR staking contract. ---
**Author:** ![jensei](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/jensei/32/69_2.png) [@jensei](https://forum.summer.fi/u/jensei)\ **Post date:** [November 6, 2025, 2:16pm UTC](https://forum.summer.fi/t/sip5-13-multi-chain-foundation-roles-setup/452/2 "2025-11-06T14:16:58Z")
Thanks @chrisb for putting this together and @halaprix for bringing this proposal to vote ([@Recognized\_Delegates](https://forum.summer.fi/groups/recognized_delegates)): > **[Lazy Summer DAO (Official) | SIP5.13: Multi-Chain Foundation Roles Setup](https://gov.summer.fi/dao/proposal/21490739281147922902088463375166555840623351539479880598861065048657134510999)** > > SIP5.13: Multi-Chain Foundation Roles Setup This makes sense as a transitional step while the the upgrade to Governance V2 is finalized. Having the Foundation multisig as a fallback coordinator across chains helps prevent upgrade deadlocks and ensures the new staking module can actually go live. Well done! As a followup, can you publish a transparency log or multi-sig action summary so the Lazy Summer DAO can follow how these powers were used? I would suggest this being done after all the necessary actions are executed and the role revoked. If needed, I can help compile these actions. ---
**Author:** ![jensei](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/jensei/32/69_2.png) [@jensei](https://forum.summer.fi/u/jensei)\ **Post date:** [March 11, 2026, 3:18pm UTC](https://forum.summer.fi/t/sip5-13-multi-chain-foundation-roles-setup/452/3 "2026-03-11T15:18:42Z")