StakeWise Labs: Allocate 250 keys on the Ethereum Network


Operator description: StakeWise Labs
Servers geographical location: Europe
Consensus layer clients: Lighthouse
Execution layer clients: Geth
Number of keys requested: 250 keys


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

    • operator: 0xf91AA4a655B6F43243ed4C2853F3508314DaA2aB
    • depositDataMerkleRoot: 0x808ca6658fc769204a5d3ca548289acbbd93e5fcb2af59bb8bbc35471dacc05b
    • depositDataMerkleProofs: /ipfs/QmXahrbws86yYtTCDa8Gp8kuWsVtP8piDKxiXie2DZynLo
  • 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 0xf91AA4a655B6F43243ed4C2853F3508314DaA2aB address


! Please make sure to examine the operator overview here before voting!

Should the StakeWise DAO onboard StakeWise Labs as Node Operator with 250 keys on the Ethereum network?
  • Yes

  • No

0 voters


As always, we invite StakeWise DAO members as well as the members of the existing node operator set to share thoughts & comment on the proposal.


Let’s do this! Eat steak be wise!