# ssv architecture questions ### networking > "a subnet of peers consists of operators that are responsible for multiple committees, reusing the same topic to communicate on behalf of multiple validators" -> how is a operator assigned to a subnet? are operators partial keys constant or do they change in time? > Validator's public key is mapped to a subnet using a hash function, which helps to distribute validators across subnets in a balanced, distributed way: >`hash(validatiorPubKey) % num_of_subnets` -> isn't this problematic? if only input determining subnet is `validatiorPubKey` than an attacker can choose validator keys to fund to basically pick the subnet subnet, seems that might be undesirable. ### Validator Share > Committee: An array of Nodes that constitute the SSV validator committee. -> What are the committee dynamics? a commitee x is always a subset of subnet x correct? How are Operators assigned to a specific commitee? ### Node > NodeIDs are extremely important as they are used when splitting a validator key via Shamir-Secret-Sharing, later on they are used to verify messages and reconstruct signatures. Into how many shares is a validator split? what is is the *m/n* in this schema? From my understanding it seems that network assigns shares to specific operators is this so? -> if so is there any schema for reshuffeling / reassigning Validator Shares after certain number of rounds? -> how to deal with unresponsive Validators? -> What is the protection / fallback against operators going offline due to internet blackout or ddos attack? ### Tokenomics -> Operators are paid in SSV token, but their operational expenses are in USD(or other fiat), is there a way for them to hedge this risk? Perhaps DAO could provide Put options at a reasonable price for operators. -> Are there incentives other than SSV token / reputation to keep Operators validating? what if SSV price suddenly tanks are there other incentives to keep operators in check?