LIP-37: Execution Delegation Framework (EDF)

Proposals The LIP - Lido Improvement Proposal - Process
13

Operator: Staking Facilities
Seat: DSM guardian
DelegationContract: 0x35506190Ca6df385aA6Bc4a970646dd4f49426c1
Owner multisig: 0x3d49967d09637B83E465Cc32b1C5d968e3d34eA8
Delegate EOA: 0x06d6c4F26354aA1426c0Abd79A5f18A5d5fF684f

  • I have read the EDF Operator Key Custody Policy and my setup follows it
  • I created a dedicated owner multisig, at least 2-of-3, with signers held by different people
    on different devices
  • The multisig is used for nothing except this delegation contract
  • I deployed my DelegationContract from the official DelegationFactory, with a 48-hour
    (172800 s) cooldown
  • I verified on-chain that owner(), getDelegate(), getCooldown() and isTerminated() are what I
    intended
  • I set up 24/7 alerts on DelegateNominated, DelegateRevoked and Terminated

Operator: Staking Facilities
Seat: Lido Oracle
DelegationContract: 0xc7442d4d8F3FfEa0fA4a18Ad3062c8137cE21749
Owner multisig: 0x035AcCF7E230f32028a1134134A035dda567C86e
Delegate EOA: 0x7abC999C7E1f22a7E12b2A1024bC17676FE18b4b

  • I have read the EDF Operator Key Custody Policy and my setup follows it
  • I created a dedicated owner multisig, at least 2-of-3, with signers held by different people
    on different devices
  • The multisig is used for nothing except this delegation contract
  • I deployed my DelegationContract from the official DelegationFactory, with a 48-hour
    (172800 s) cooldown
  • I verified on-chain that owner(), getDelegate(), getCooldown() and isTerminated() are what I
    intended
  • I set up 24/7 alerts on DelegateNominated, DelegateRevoked and Terminated
1 Like