VeriHash: Allocate 5000 keys on Gnosis Network

Proposals
1

Summary

Operator description: VeriHash Operator Link

Servers geographical location: EU

Consensus layer clients: Lightouse, Prysm-GBC

Execution layer clients: Nethermind, OpenEthereum

Number of keys requested: 5000 keys

Specification

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

    • operator: 0xE11E57383312BE71B0589e1a3529FeC2A524975C
    • depositDataMerkleRoot: 0x58c4f5f4e7fb880c8d9fc19b69777488796929535dbfb98089ffb335f4ace0b5
    • depositDataMerkleProofs: /ipfs/QmXjyVZYiut19SMELphLLg1bQnGq7kLRGQTX58ZDw47vfJ

  • 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 Gnosis chain network with an additional 5,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.

1 Like
2

Shards verification:

python stakewise_cli/main.py verify-shard-pubkeys
Enter IPFS hash for operator deposit data to verify: /ipfs/QmXjyVZYiut19SMELphLLg1bQnGq7kLRGQTX58ZDw47vfJ
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/QmZbUBfHAYzmKjqorUns4LWQpcgrzrDb8QSucMVi6dgyA4
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/QmfZB1bX1jfG3XWH56Y8ytUgAXzebPKHik4JUQV5AkULhf
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/QmdeEL2MbVjsfA5ruRqJBTNwyZKGTqzJhpSGaytBKYArcm
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/QmdsZueRLVN4hhahUP8usE6L2F4Uv4Y2m61N2Fpnf4DZBm
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/QmXzKwc6DPN1KAcCDg9UoUDbViCrzkAcGNhNsLSFRdgx5B
Reconstructing public keys from shards		  [####################################]  5000
Successfully verified operator shards
1 Like
3

Deposit data verification:

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