[SWIP-11] Onboard Finoa Consensus Services as Node Operator in StakeWise with 250 keys on the Ethereum Network

Proposals
#1

Summary

Operator description: here
Servers geographical location: Singapore
Consensus layer clients: Lighthouse, Prysm
Execution layer clients: GoEthereum, Nethermind
Number of keys requested: 250 keys

Specification

  • DAO calls addOperator function of PoolValidators contract with the following parameters:
    • operator: 0xFe26832d3580E0ADe4813F9e60E7C17b45E92cBa
    • depositDataMerkleRoot: 0xee7a12a080ce3e5014832a3f129af1d081cfbc26545a3a5f8bee9401fb4715cb
    • depositDataMerkleProofs: /ipfs/QmXLg4K6kyUUD6evZFYJPUPz6KrTWrSRnRKUkwdEKot9UH
  • 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 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
Finoa Consensus Services
#2

Deposit data verification:

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

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

1 Like
#4

Shards verification:

python stakewise_cli/main.py verify-shard-pubkeys --deposit-data-ipfs-hash /ipfs/QmXLg4K6kyUUD6evZFYJPUPz6KrTWrSRnRKUkwdEKot9UH --shards-count 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/QmWfDipkWteVgRZifvTxPTkvrty4Fwe6ezAUDmG1uHciut
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/QmNs2pSS2SDCQxpBtsWDbV4yvMUFDR1heBt1F9UM6Z7fKX
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/QmVoEpZYW8j4gXrcKDxnVTdqi6Guq7YgT1ZxGSDac6tr7m
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/QmcZ1ygDKxoFynxMgrLucStQETKHagp7e54p2JWkWBDTAy
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/QmejeB36zQNHw2V2DswmvgUMEt1Z56wypgz3PcCgnjR1HB
Reconstructing public keys from shards		  [####################################]  250
Successfully verified operator shards
1 Like