• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
StakeWiseStakeWiseby0xE7EE3D4Ea937F112E772B3dc5a212545869dfFABbrianchilders.eth

Allocate an additional 800 keys on the Ethereum Network to Verihash

Voting ended almost 4 years agoSucceeded

Description and discussion about the proposal are available here:

https://forum.stakewise.io/t/verihash-allocate-an-additional-800-keys-on-the-ethereum-network/751

Summary Operator description: VeriHash Operator Link

Servers geographical location: US, Oregon

Consensus layer clients: Lighthouse, Teku

Execution layer clients: Nethermind, Erigon

Number of keys requested: 800 keys

Specification

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

operator: 0xE11E57383312BE71B0589e1a3529FeC2A524975C depositDataMerkleRoot: 0x3b6666739c2aaa5aef786f579a4ccb5418962c6e663623c3e1489d7ffdf58411 depositDataMerkleProofs: /ipfs/QmYK2jGDF4reS3qVogyWQS1TJqBq6s9KdXVBafgD9zmx5M 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 0xE11E57383312BE71B0589e1a3529FeC2A524975C address

Off-Chain Vote

Yes
9.39M SWISE100%
No
0 SWISE0%
Download mobile app to vote

Discussion

StakeWiseAllocate an additional 800 keys on the Ethereum Network to Verihash

Timeline

May 04, 2022Proposal created
May 04, 2022Proposal vote started
May 07, 2022Proposal vote ended
Dec 11, 2025Proposal updated