[SIP5.13] Multi-chain Foundation Roles Setup

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.

1 Like

Thanks @chrisb for putting this together and @halaprix for bringing this proposal to vote (@Recognized_Delegates):

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.

1 Like