Finoa Consensus Services: Allocate 5000 keys on the Gnosis Chain Network

Proposals
1

#Summary
Operator description: Finoa Consensus Services
Servers geographical location: Singapore
Consensus layer clients: Lighthouse
Execution layer clients: Nethermind
Number of keys requested: 5000 keys

Specification

  • DAO calls addOperator function of PoolValidators contract with the following parameters:
    • operator: 0xFe26832d3580E0ADe4813F9e60E7C17b45E92cBa
    • depositDataMerkleRoot: 0x059a8487a1ce461e9670c4646ef85164ae8791613866d28c972fb351dc45c606
    • depositDataMerkleProofs: /ipfs/QmfPnyNojfyqoi9yqS3jMp16GGiTQee4bdCXJC64KqvTgc
  • 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 0xFe26832d3580E0ADe4813F9e60E7C17b45E92cBa address

Vote

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

Should the StakeWise DAO onboard Finoa Consensus as Node Operator with 5000 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.

2

./stakewise-cli verify-deposit-data --ipfs-hash /ipfs/QmfPnyNojfyqoi9yqS3jMp16GGiTQee4bdCXJC64KqvTgc
Please choose the network name (mainnet, goerli, harbour_mainnet, harbour_goerli, gnosis) [mainnet]: gnosis
Enter the expected merkle root of the deposit data: 0x059a8487a1ce461e9670c4646ef85164ae8791613866d28c972fb351dc45c606
Enter the expected number of keys in deposit data: 5000
Verifying deposit data from /ipfs/QmfPnyNojfyqoi9yqS3jMp16GGiTQee4bdCXJC64KqvTgc… [####################################] 5000/5000
Verifying validators are not registered… [####################################] 5000/5000
The deposit data from /ipfs/QmfPnyNojfyqoi9yqS3jMp16GGiTQee4bdCXJC64KqvTgc has been successfully verified

1 Like
3

./stakewise-cli verify-shard-pubkeys --shards-count 5 --deposit-data-ipfs-hash /ipfs/QmfPnyNojfyqoi9yqS3jMp16GGiTQee4bdCXJC64KqvTgc
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/QmX9kBY9yTMRHpeSHM22AFEvSrNkXLZQzoPPVtVks2Nc4K
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/QmYrjdix18VCkBEnXmafib6dkVPTvUE27ixM32jC8GkmEh
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/QmPVjSpd5ALB4A9LDuL45gDag7uAH4ECLGp2nXbyQpUro5
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/QmPT9ngxM57ey1bfQqGZ2cqF9SquJL1JWqiuB8Hdm3sAtR
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/Qma6tFoSy6ghGzH3cX7V9ShK9HmWB795AhU2D5KhT4Xmgc
Reconstructing public keys from shards [####################################] 5000
Successfully verified operator shards

1 Like
4

Snapshot Vote here:

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

Starts at noon (12:00) CST today (JUN-15-2022) and voting will be open for three days.

1 Like