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

Voting ended over 3 years agoSucceeded

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

Off-Chain Vote

For

10.31M SWISE100%

Against

1.07K SWISE0%

Abstain

0 SWISE0%

Download mobile app to vote

Discussion

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

Timeline

Sep 26, 2022Proposal created

Sep 26, 2022Proposal vote started

Sep 29, 2022Proposal vote ended

Nov 30, 2024Proposal updated