This is currently now allowed by design as:
- pool operator cannot be changed in staking pool
- each pool's vote is stored, voting power is computed at sigle wallet/smart-wallet level and not aggregated level (i.e. pool operator).
However, we should develop a test to assert that a change in the pool operator won't affect ability to vote and won't allow double voting. This is relevant in the case we will query staking pool data from registry and pool, instead of initializing the staking pool, for gas efficiency (this will however affect ability to set staking pal, which is a feature which is not particularly requested anyway).
This is currently now allowed by design as:
However, we should develop a test to assert that a change in the pool operator won't affect ability to vote and won't allow double voting. This is relevant in the case we will query staking pool data from registry and pool, instead of initializing the staking pool, for gas efficiency (this will however affect ability to set staking pal, which is a feature which is not particularly requested anyway).