Allocate an additional 800 keys on the Ethereum Network to CryptoManufaktur

Forum and discussion about this proposal can be found here:

https://forum.stakewise.io/t/cryptomanufaktur-allocate-800-keys-on-ethereum-mainnet/752

Summary

Operator description: CryptoManufaktur Servers geographical location: Kubernetes in AWS ap-southeast-2 (Sydney); consensus and execution clients in Servers Australia baremetal in Sydney-1, Sydney-2 and Melbourne Consensus layer clients: Lighthouse,Teku Execution layer clients: Erigon, Besu Number of keys requested: 800

We are currently running three load-balanced CL:EL combinations for 250 keys.

Specification

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

operator: 0x59eCf48345A221E0731E785ED79eD40d0A94E2A5 depositDataMerkleRoot: 0xbf92e48c858ddcb68a48b1e4f093dae0f9fe5560e0c144a5508544e5932daf30 depositDataMerkleProofs: /ipfs/QmWeVNemCfiZwJrHBV83e5Nme2UWPRaWvtjRPnExCsNX9D

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-2-mainnet.shard @gleb0x: /home/ubuntu/committee/gleb0x-59ecf483-2-mainnet.shard @ali_run: /home/ubuntu/committee/ali_run-59ecf483-2-mainnet.shard @ottodv: /home/ubuntu/committee/ottodv-59ecf483-2-mainnet.shard @tsudmi: /home/ubuntu/committee/tsudmi-59ecf483-2-mainnet.shard