VeriHash: Allocate an additional 4000 keys on the Gnosis Chain Network

Proposals
1

Summary

Operator description: VeriHash Operator Link

Servers geographical location: EU

Consensus layer clients: Lighthouse, Prysm-GBC

Execution layer clients: Nethermind, OpenEthereum

Number of keys requested: 4000 keys

Specification

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

    • operator: 0xE11E57383312BE71B0589e1a3529FeC2A524975C
    • depositDataMerkleRoot: 0x35266b0a3b4e47e5a03cea8302bd22a55f6418dfb94a9f01431efc2849c19fad
    • depositDataMerkleProofs: /ipfs/QmSUFBzkBeB6uqn9aV8kwBTMoeMgLUSBaKfXbXsjADAUie

  • 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

Share the encrypted validator key shares with the committee members through Telegram:

  • @kiriyha1: /home/bgraham/code/operatorcli/stakewise-cli-v1.1.4-linux-amd64/committee/kiriyha1-e11e5738-2.shard
  • @gleb0x: /home/bgraham/code/operatorcli/stakewise-cli-v1.1.4-linux-amd64/committee/gleb0x-e11e5738-2.shard
  • @ali_run: /home/bgraham/code/operatorcli/stakewise-cli-v1.1.4-linux-amd64/committee/ali_run-e11e5738-2.shard
  • @ottodv: /home/bgraham/code/operatorcli/stakewise-cli-v1.1.4-linux-amd64/committee/ottodv-e11e5738-2.shard
  • @tsudmi: /home/bgraham/code/operatorcli/stakewise-cli-v1.1.4-linux-amd64/committee/tsudmi-e11e5738-2.shard

Vote

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

Should the StakeWise DAO add to VeriHash’s allocation on the Gnosis Chain network with an additional 4,000 keys?

  • 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.

4 Likes
2

New key allocation deployed – validators spot checked and functioning as expected.

2 Likes
3

Shards verification:

Enter IPFS hash for operator deposit data to verify: /ipfs/QmSUFBzkBeB6uqn9aV8kwBTMoeMgLUSBaKfXbXsjADAUie
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/QmNNU3iDREdq5w52tAJPjSeFWJs3J478C7PxTR33Eatm98
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/QmQXsKKbfZBDDA9BAuzzSU1NmUHHdNQRKMKiTPAugEiAz4
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/QmZQJWGDEYtUmh39vqCGx27nirjmecmABAPqyhzVjGeec5
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/QmZ8AMWPjy2PXKpZsBEdS9WzMRqPS3aPnKdJqjvxvt1KCc
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/QmcyqELBPebGwztaGY3PJdwSXBCDkGpp48CNSyqTBwYbjj
Reconstructing public keys from shards		  [####################################]  4000
Successfully verified operator shards
1 Like