CryptoManufaktur: Allocate 5,000 keys on Gnosis Network

Proposals
1

CryptoManufaktur: Allocate 5,000 keys on the Gnosis Chain Network

Summary

Operator description: CryptoManufaktur
Servers geographical location: Kubernetes in AWS us-east-2; consensus and execution clients in OVH baremetal in US-East, US-West, Canada-East
Consensus layer clients: Lighthouse
Execution layer clients: Nethermind, OpenEthereum
Number of keys requested: 5,000 keys

We are currently running three load-balanced CL:EL combinations for 5,000 keys. We will add additional servers as dictated by load.

Specification

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

    • operator: 0x59eCf48345A221E0731E785ED79eD40d0A94E2A5
    • depositDataMerkleRoot: 0x28b6bab52ea04459bdafd0619ffde6b25f6ba0de6fb80f16b45919b84b7a8b5a
    • depositDataMerkleProofs: /ipfs/QmQSpMek1XWEsqcLLsc3X4f8hZJA2t659eZjM9zK1EDVo5

  • 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 0x59eCf48345A221E0731E785ED79eD40d0A94E2A5 address

Share the encrypted validator key shares with the committee members through Telegram:

  • @kiriyha1: /home/ubuntu/committee/kiriyha1-59ecf483-3.shard
  • @gleb0x: /home/ubuntu/committee/gleb0x-59ecf483-3.shard
  • @ali_run: /home/ubuntu/committee/ali_run-59ecf483-3.shard
  • @ottodv: /home/ubuntu/committee/ottodv-59ecf483-3.shard
  • @tsudmi: /home/ubuntu/committee/tsudmi-59ecf483-3.shard

Vote

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

Should the StakeWise DAO add to CryptoManufaktur’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/QmQSpMek1XWEsqcLLsc3X4f8hZJA2t659eZjM9zK1EDVo5
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/QmY8hbh1gSHQxByLcySsPWvRLKAGZ6kyW6Gsy3SeJu4QD1
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/QmPktR4VqnG124b9VyLFejS1LcaUDVT27GwKCrTmawJT5V
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/QmcAKVVM3WxC7WYB2MzyYyDanaCj1SRRi1PDTqe85dEGxV
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/Qmc1jcPRstdJ3hfm4Vt5CKKbv9xoSdCWrtK641dr5Z4XA2
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/QmNMikXHMqgmmCz3r7HoPySYEi3tmJRn2No2LJeEaSkqot
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/QmQSpMek1XWEsqcLLsc3X4f8hZJA2t659eZjM9zK1EDVo5
Please choose the network name (mainnet, goerli, perm_goerli, gnosis) [mainnet]: gnosis
Enter the expected merkle root of the deposit data: 0x28b6bab52ea04459bdafd0619ffde6b25f6ba0de6fb80f16b45919b84b7a8b5a
Enter the expected number of keys in deposit data: 5000
Verifying deposit data from /ipfs/QmQSpMek1XWEsqcLLsc3X4f8hZJA2t659eZjM9zK1EDVo5...		  [####################################]  5000/5000
Verifying validators are not registered...		  [####################################]  5000/5000
The deposit data from /ipfs/QmQSpMek1XWEsqcLLsc3X4f8hZJA2t659eZjM9zK1EDVo5 has been successfully verified
1 Like