Finoa Consensus Services: Allocate 250 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: 250 keys

Specification

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

    • operator: 0xFe26832d3580E0ADe4813F9e60E7C17b45E92cBa
    • depositDataMerkleRoot: 0x5c6d75ac13f2e9959d54ec0c47a8ab17a8553d1cf619ae7cce0d65d01a237764
    • depositDataMerkleProofs: /ipfs/QmXQG1uPUo2WDPqeQ5UTTG9paVABYJPqZzW1bkYNM7zkGa

  • DAO calls setOperator function of Roles contract with the following parameters:

    • account: 0xFe26832d3580E0ADe4813F9e60E7C17b45E92cBa
    • 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 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 250 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.

3 Likes
2

Deposit data verification:

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

Shards verification:

python stakewise_cli/main.py verify-shard-pubkeys --shards-count 5 --deposit-data-ipfs-hash /ipfs/QmXQG1uPUo2WDPqeQ5UTTG9paVABYJPqZzW1bkYNM7zkGa
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/QmNeBnaqKqGBurXzvYkTswn8z9WstgnC7AMJyeyhFnqy4N
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/QmWma7ZhAAoPPHiUdyo4BW8NjYvmtYS7zRA7gRGFE53UTt
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/Qma7s2Ly7NAFeUpti91r6DpaG9zmqMMkiAxmjCFBEVnatB
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/QmU4b6rQCdDSjVGJNd2N4ZmK6Rm3kGYLAJRftToUut8wN5
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/QmRJ9ro96MCbYKv8Qav34spbP3CsfbwSnn6yeqLJM4V8Hv
Reconstructing public keys from shards		  [####################################]  250
Successfully verified operator shards
1 Like