SETUP-11 - Accept Ownership of both ProtocolStaking contracts

Summary

This proposal accepts ownership, ie DEFAULT_ADMIN_ROLE, on both instances of ProtocolStaking contracts (the Coprocessor and the KMS instances).

Motivation & Context

This proposal accepts ownership, ie DEFAULT_ADMIN_ROLE, on both instances of ProtocolStaking contracts (the Coprocessor and the KMS instances).

Proposed Changes

The following on-chain action(s) execute when the proposal is approved and executed (Ethereum mainnet):

Action 1: call acceptDefaultAdminTransfer on PROTOCOL_STAKING_COPROCESSOR (0x7147485b892158f2B875f7aC5Ea48A9937C66AE8)

Action 2: call acceptDefaultAdminTransfer on PROTOCOL_STAKING_KMS (0xe9b176CCaA8840DC3b3567bb83e2cD2a6c36F4Ab)

Technical Details

  • Network: Ethereum mainnet
  • Proposal: SETUP-11
  • Proposal plugin: SETUP_MULTISIG 0xBc860b6a4C860C5424B84A056E53ACFb2C99a38F (Aragon OSx Multisig, 3/5)
  • Creation transaction (ProposalCreated): 0x57f4d7b1afd085dd056b254ba27b6e61a4647dc5316a6623883de6408776e0a6 — block 24226038, 2026-01-13
  • Target contract(s):
  • 0x7147485b892158f2B875f7aC5Ea48A9937C66AE8 — PROTOCOL_STAKING_COPROCESSOR (ethereum, protocol_staking)
  • 0xe9b176CCaA8840DC3b3567bb83e2cD2a6c36F4Ab — PROTOCOL_STAKING_KMS (ethereum, protocol_staking)
  • Addresses verifiable in the protocol-registry.

Other considerations

Single-chain governance action; effects apply once the proposal is executed on Ethereum mainnet. Independently verify each target address and decoded call against the protocol-registry and the on-chain proposal.

Resources