VeriHash: Allocate 250 keys on the Ethereum Network

Proposals
1

Summary

Operator description: Operator Information

Servers geographical location: Oregon, USA (AWS)

Consensus layer clients: Lighthouse, Teku

Execution layer clients: Nethermind, Erigon

Number of keys requested: 250 keys

Specification

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

    • operator: 0xE11E57383312BE71B0589e1a3529FeC2A524975C
    • depositDataMerkleRoot: 0x81cb61ee13adf99bca42ccb60556bdbc360dbc690737e64cd9ddd71f26e5688e
    • depositDataMerkleProofs: /ipfs/QmPSZhwqmCje4CCAtkGGQweqbTmw2NpAW2FrE7EA4fsvMs

  • 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 250 keys on the Ethereum 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:

Enter IPFS hash for operator deposit data to verify: /ipfs/QmPSZhwqmCje4CCAtkGGQweqbTmw2NpAW2FrE7EA4fsvMs
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/QmPS8cmexyx9iTAb6FgKwfr1rUAu1f1aa1jFRpbJzfADgn
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/QmUwoqqei9D6B91RRgLu6kUrG9DqS1uQ3Zo5DeHaqpnX8Q
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/QmSLMKEngh3LF8aGACaWMhQ4BRGfrc1RWx188aW1o2iQ2W
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/QmNNAmqSmiJ8cGfmGz6G5jLrkrxZV59rB6fP1Q218BGKmJ
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/QmPMdh23PCVxSx7kZkkSWY8wdT5s4FmrrDc3PasRu2qhRf
Reconstructing public keys from shards		  [####################################]  250
Successfully verified operator shards
1 Like
3

https://vote.stakewise.io/#/proposal/0x48c49bb8fd8b2649e16e9861d78c2e74432ec51f5858f92ea0c389674d07da6f

1 Like
4

Let’s do this! Eat steak be wise! Looking forward to VeriHash being a node operator. :slight_smile: