Executed

SIP5.2: Multi-Chain AdmiralsQuarters Role Setup


Proposal ID

329887...0285

Proposed

Mar 11th, 2025

Result details

1 address

106.67M votes

106.67M

Final Votes

Quorum

106.67M of 39.06M

Majority support

Yes

For

106.67M

Against

0

Abstain

0

Actions

Type

Address

Details

Custom

0x6038...E861

grantAdmiralsQuartersRole(..)

Custom

Account

0x6038...E861

Method

grantAdmiralsQuartersRole(..)

Custom

0xd76a...8d0c

sendProposalToTargetChain(..)

Custom

Account

0xd76a...8d0c

Method

sendProposalToTargetChain(..)

Proposal

Summary

This proposal grants the ADMIRALS_QUARTERS_ROLE to newly deployed AdmiralsQuarters contracts across all active chains in the Lazy Summer Protocol ecosystem.

Motivation

The AdmiralsQuarters contract requires the ADMIRALS_QUARTERS_ROLE in the ProtocolAccessManager to operate properly. This role is necessary for the contract to unstake and withdraw assets from fleets on behalf of users.

Newly deployed AdmiralsQuarters contracts:

  • base: 0x08E19585548c8439E83239BBED99aFc8e28528C6
  • arbitrum: 0x8423c38AF6B70D27d613c17595e1110b25d3a983

Specifications

Actions

  1. On base:
    • Grant ADMIRALS_QUARTERS_ROLE to AdmiralsQuarters at 0x08E19585548c8439E83239BBED99aFc8e28528C6
  2. Send cross-chain proposal to arbitrum to:
    • Grant ADMIRALS_QUARTERS_ROLE to AdmiralsQuarters at 0x8423c38AF6B70D27d613c17595e1110b25d3a983

Technical Details

The ADMIRALS_QUARTERS_ROLE is defined in the ProtocolAccessManager contract and is specifically designed for the AdmiralsQuarters contract. This role enables the contract to perform unstaking and withdrawal operations from fleets on behalf of users.

When a user interacts with the AdmiralsQuarters interface to withdraw assets from fleets, the contract uses this role to execute the necessary transactions, ensuring a streamlined user experience while maintaining proper access controls.

Final Votes

Quorum

106.67M of 39.06M

Majority support

Yes

For

106.67M

Against

0

Abstain

0

Final Votes

1 address

106.67M votes

106.67M

Status

Tue Mar 11, 01:57 pm

Published onchain

Tue Mar 11, 01:58 pm

Voting period started

Tue Mar 11, 02:08 pm

Voting period ended

Tue Mar 11, 02:11 pm

Proposal queued

Tue Mar 11, 02:16 pm

Proposal executed