• © Goverland Inc. 2026
  • v1.0.5
  • Privacy Policy
  • Terms of Use
StakeWiseStakeWiseby0x7F910AE96d839e96c265bD479d35EaC25dDc072Etsudmi.eth

Extend StakeWise Labs operator with 200 keys

Voting ended about 4 years agoSucceeded

Discussion about this Snapshot: https://forum.stakewise.io/t/extend-stakewise-labs-operator-with-200-keys/615

Introduction

While the core team is finalizing the last missing parts to start onboarding new operators, we need to have some allocation of the validator keys for the existing ether to start staking.

Extend the only node operator in the network, Stakewise Labs, with 200 more keys for the deposited ether to start staking.

Specification

  • DAO calls addOperator function of PoolValidators contract with the following parameters:

    • operator: 0x5fc60576B92c5cE5c341C43e3B2866eb9E0cdDD1
    • depositDataMerkleRoot: 0x6f7be760fb7bf7160300dde3214e2de28c9a4e409a15897d8cb3e1f1b7635d14
    • depositDataMerkleProofs: /ipfs/QmZEhxAhp4ymeoNZ6L3wdM2pxCAo9R8MJ8aa7hDG7Km3ZZ
  • If the proposal will be approved, the operator must perform the following steps:

    • Call operator-cli sync-vault or operator-cli sync-local with the same mnemonic as used for generating the proposal
    • Create or update validators and make sure the new keys are added
    • Call commitOperator from the 0x5fc60576B92c5cE5c341C43e3B2866eb9E0cdDD1 address

Off-Chain Vote

Yes
7.86M 100%
No
0 0%
Download mobile app to vote

Timeline

Feb 02, 2022Proposal created
Feb 02, 2022Proposal vote started
Feb 04, 2022Proposal vote ended
Oct 26, 2023Proposal updated