VeriHash: Allocate 1000 keys on the Gnosis Network

Proposals
1

Summary

Operator description: Operator Information

Servers geographical location: Ireland (AWS)

Consensus layer clients: Lighthouse, Prysm-GBC

Execution layer clients: Nethermind, Openethereum

Number of keys requested: 1000 keys

Specification

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

    • operator: 0xE11E57383312BE71B0589e1a3529FeC2A524975C
    • depositDataMerkleRoot: 0x935836b6044c3eb868ca6d2a1965e974fc3627d58400ee89b3a4ecbdd2af871f
    • depositDataMerkleProofs: /ipfs/QmXsic1MXE8bdJirQAdcpCC2EVfSGPaT6rPKTr7achZ7c9

  • DAO calls setOperator function of Roles contract with the following parameters:

    • account: 0xE11E57383312BE71B0589e1a3529FeC2A524975C
    • revenueShare: 5000

  • 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

Vote

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

Should the StakeWise DAO onboard VeriHash as Node Operator with 1000 keys on the Gnosis Chain network?

  • Yes

  • No

0 voters

Discussion

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.

1 Like
2

Shards verifications:

  1. kiriyha1: /ipfs/QmPaxCKUqWrFXCK7XmEM36ADsTFs9jgpR722z8QDedxAnu
  2. gleb0x: /ipfs/QmPd1KDmkuzHbsd2kR5D8uTMKbtA2ri35GyVcVZ7toE2Z4
  3. ali_run: /ipfs/QmeFRqYcms5PZus8swQzxgScokKiCc8gYEwD3eun6BSiLA
  4. ottodv: /ipfs/Qmb2PMnToLva2ykZRnif6ptqosRnR9qrrKhy5Xh1J5hC74
  5. tsudmi: /ipfs/QmTg1SwqK9gnKe4D9XHHaBSNo22yJFhmYVaAWAianbu2yn
Enter IPFS hash for operator deposit data to verify: /ipfs/QmXsic1MXE8bdJirQAdcpCC2EVfSGPaT6rPKTr7achZ7c9
Enter total number of shards to verify: 5
Enter committee member position number (index in stakewise.eth ENS record): 0
Enter the shard public keys IPFS hash for 0 committee member (1/5): /ipfs/QmPaxCKUqWrFXCK7XmEM36ADsTFs9jgpR722z8QDedxAnu
Enter committee member position number (index in stakewise.eth ENS record): 1
Enter the shard public keys IPFS hash for 1 committee member (2/5): /ipfs/QmPd1KDmkuzHbsd2kR5D8uTMKbtA2ri35GyVcVZ7toE2Z4
Enter committee member position number (index in stakewise.eth ENS record): 2
Enter the shard public keys IPFS hash for 2 committee member (3/5): /ipfs/QmeFRqYcms5PZus8swQzxgScokKiCc8gYEwD3eun6BSiLA
Enter committee member position number (index in stakewise.eth ENS record): 3
Enter the shard public keys IPFS hash for 3 committee member (4/5): /ipfs/Qmb2PMnToLva2ykZRnif6ptqosRnR9qrrKhy5Xh1J5hC74
Enter committee member position number (index in stakewise.eth ENS record): 4
Enter the shard public keys IPFS hash for 4 committee member (5/5): /ipfs/QmTg1SwqK9gnKe4D9XHHaBSNo22yJFhmYVaAWAianbu2yn
Reconstructing public keys from shards		  [####################################]  1000
Successfully verified operator shards
1 Like
3

The keys were added as part of the Gnosis Chain deployment.

1 Like