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

Proposals
1

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

Summary

Operator description: CryptoManufaktur
Servers geographical location: The infrastructure is located in AWS us-east-2 for the validator client in Kubernetes as well as OVH baremetal, US East, US West and Canada East for the Gnosis EL and CL clients (Execution Layer and
Consensus Layer).
Consensus layer clients: Lighthouse; Prysm and Nimbus in testing
Execution layer clients: Nethermind, OpenEthereum
Number of keys requested: 1,000 keys

Specification

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

    • operator: 0x59eCf48345A221E0731E785ED79eD40d0A94E2A5
    • depositDataMerkleRoot: 0x5a473e866a3d8889df7e9d2b433871b54a31e10cfc37eaa23ea22ae8ca84ec25
    • depositDataMerkleProofs: /ipfs/QmdJKjDshXFv8AUiKx42Ap4MJN8tFCBbjnJpda9tEthYAh

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

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

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

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

Vote

N/A as this operator is already live.

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 verifications:

  1. kiriyha1: /ipfs/QmXhfa9f4NPK55jfJWaCwrJsjBrQiYo12n9J2mP7cA7SHM
  2. gleb0x: /ipfs/QmQ3YhLhhPC5VUkjuyDuNX5Ahe3hRe3c3UJYyELxqnBJrh
  3. ali_run: /ipfs/QmUBrKNvXMQWz4XzR5gSiQyi3j6QeBnUJXTjsXADS1fxgX
  4. ottodv: /ipfs/QmczRncva194sqjz5MgmeTy29Ut4gEmCYJHp92DoGnPruQ
  5. tsudmi: /ipfs/QmeGXZmZ41dwrENw4yRgbiJTPqJK1dv1tZtcYe75QdCZMM
Enter IPFS hash for operator deposit data to verify: /ipfs/QmdJKjDshXFv8AUiKx42Ap4MJN8tFCBbjnJpda9tEthYAh
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/QmXhfa9f4NPK55jfJWaCwrJsjBrQiYo12n9J2mP7cA7SHM
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/QmQ3YhLhhPC5VUkjuyDuNX5Ahe3hRe3c3UJYyELxqnBJrh
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/QmUBrKNvXMQWz4XzR5gSiQyi3j6QeBnUJXTjsXADS1fxgX
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/QmczRncva194sqjz5MgmeTy29Ut4gEmCYJHp92DoGnPruQ
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/QmeGXZmZ41dwrENw4yRgbiJTPqJK1dv1tZtcYe75QdCZMM
Reconstructing public keys from shards		  [####################################]  1000
Successfully verified operator shards
1 Like