T-Systems MMS: Allocate 250 keys on the Ethereum Network

Proposals
1

Summary

Operator description: Forum Post

Servers geographical location: Germany

Consensus layer clients: Lighthouse; (Testing setup: Nimbus, Teku)

Execution layer clients: Geth; (Testing setup: Nethermind, Besu)

Number of keys requested: 250 keys

Specification

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

    • operator: 0x01f26d7f195A37D368cB772ed75eF70Dd29700f5

    • depositDataMerkleRoot: 0x3c1a3c771b5a2440f424228215ab1616a43a449e1e7a8e369b4f3a6be0c77386

    • depositDataMerkleProofs: /ipfs/QmVaF1LjKNCv4ec4XjaeKkHs52YwVacWwvEb7zu6XHZSsM

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

    • account: 0x01f26d7f195A37D368cB772ed75eF70Dd29700f5

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

2

Deposit data verification:

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

Shards verification:

python stakewise_cli/main.py verify-shard-pubkeys --shards-count 5 --deposit-data-ipfs-hash /ipfs/QmVaF1LjKNCv4ec4XjaeKkHs52YwVacWwvEb7zu6XHZSsM
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/QmQ1rioTABJdFLj73dzTg784cQ6yMdXnWMmXd2Fz6KBxiP
Enter committee member position number (index in stakewise.eth ENS record): 2
Enter the shard public keys IPFS hash for 2 committee member (2/5): /ipfs/QmRedkLTcrD71TWznjmeNQPux6GzknXFGtWWqem7w2ezdJ
Enter committee member position number (index in stakewise.eth ENS record): 4
Enter the shard public keys IPFS hash for 4 committee member (3/5): /ipfs/QmaLF7vsh54j1jiBgMEqX6SE9o5FKisx99GB3CvXZ6jGYn
Enter committee member position number (index in stakewise.eth ENS record): 1
Enter the shard public keys IPFS hash for 1 committee member (4/5): /ipfs/QmNdaKTaWVvtNS7txRLQaRzh7tAQR5oWKR4gK7jVLu78G4
Enter committee member position number (index in stakewise.eth ENS record): 3
Enter the shard public keys IPFS hash for 3 committee member (5/5): /ipfs/QmboZYL4QRPWKacYwJf45TUGquzfWTFpLiM1SMe542xsJS
Reconstructing public keys from shards		  [####################################]  250
Successfully verified operator shards
4

Per – Onboarding Process - StakeWise – VeriHash expects to see GNOSIS allocations before ETH allcoations. Given there has been no DAO vote for GNOSIS allocations we will unfortuantely have to vote again. We want to see T Systems come into the fold but we want to see them coming per the documented way.

5

Hi @bgraham-vh , we’re pushing T-systems to join us on Gnosis Chain as well. The process of adding a new chain is not that simple for them as it has to go through their internal corporate processes. In the onboarding process, it is stated that Gnosis comes as a bonus but is not mandatory for initiating a DAO vote.

2 Likes