VeriHash: Allocate an additional 800 keys on the Ethereum Network

Proposals
1

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

Vote

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

Should the StakeWise DAO add to VeriHash’s allocation on the Ethereum network with an additional 800 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.

1 Like
2

Vote Here: Snapshot

3

Deposit Data verification:

python stakewise_cli/main.py verify-deposit-data --ipfs-hash /ipfs/QmYK2jGDF4reS3qVogyWQS1TJqBq6s9KdXVBafgD9zmx5M
Please choose the network name (mainnet, goerli, perm_goerli, gnosis) [mainnet]:
Enter the expected merkle root of the deposit data: 0x3b6666739c2aaa5aef786f579a4ccb5418962c6e663623c3e1489d7ffdf58411
Enter the expected number of keys in deposit data: 800
Verifying deposit data from /ipfs/QmYK2jGDF4reS3qVogyWQS1TJqBq6s9KdXVBafgD9zmx5M...		  [####################################]  800/800
Verifying validators are not registered...		  [####################################]  800/800
The deposit data from /ipfs/QmYK2jGDF4reS3qVogyWQS1TJqBq6s9KdXVBafgD9zmx5M has been successfully verified
4

Shards verification:

python stakewise_cli/main.py verify-shard-pubkeys
Enter IPFS hash for operator deposit data to verify: /ipfs/QmYK2jGDF4reS3qVogyWQS1TJqBq6s9KdXVBafgD9zmx5M
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/QmPymqTVv629VVs3QLzfkxb2eH1w4QenLnMNpi71s7wrn3
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/QmUw5ZMgoHAkM6embthCbyTevNZxXAZ1jnvsYz64Dp4e73
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/QmQirpXgsUWcjd3bbEbbxdS11i7gXyeF4bobJrE6gSTT3p
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/Qme21vua439P5smGBz35DKvzhUNp3ZBPjg5MhXag3gAwLP
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/QmUQn5AZVKDH23vro6NFTkeTJgHLotqNYYpYSo3NWCNuqe
Reconstructing public keys from shards		  [####################################]  800
Successfully verified operator shards