Finoa Consensus Services: Allocate 250 keys on the Ethereum Network

With 6 yes votes and 0 no votes, putting this to a DAO vote:

Forum Link: https://forum.stakewise.io/t/finoa-consensus-services-allocate-250-keys-on-the-ethereum-network/763

Summary

Operator description: Read the operator description on the forum post. Servers geographical location: Singapore Consensus layer clients: Lighthouse, Prysm Execution layer clients: GoEthereum, Nethermind Number of keys requested: 250 keys Specification

DAO calls addOperator function of PoolValidators contract with the following parameters:
    operator: 0xFe26832d3580E0ADe4813F9e60E7C17b45E92cBa
    depositDataMerkleRoot: 0xee7a12a080ce3e5014832a3f129af1d081cfbc26545a3a5f8bee9401fb4715cb
    depositDataMerkleProofs: /ipfs/QmXLg4K6kyUUD6evZFYJPUPz6KrTWrSRnRKUkwdEKot9UH
DAO calls setOperator function of Roles contract with the following parameters:
    account: 0xFe26832d3580E0ADe4813F9e60E7C17b45E92cBa
    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 0xFe26832d3580E0ADe4813F9e60E7C17b45E92cBa address

Vote: Please make sure to examine the operator overview embedded in the forum before voting.