I’m making this post for future references to provide more context behind why some neurons within Personal DAO are proxied neurons and what the implications are for having a proxied neuron. here goes:
Originally, when I creating the functionality that allows Personal DAOs’ treasury canisters to control neurons, I did so by utilizing tECDSA signed HTTPS outcalls from the treasury canister to the NNS governance canister. Controlling a neuron via such means requires the subnet that hosts the treasury canister to sign the HTTPS outcall before it may be sent. This is more expensive as tECDSA signatures cost extra cycles, however this method of controlling a neuron may become preferred in the future considering there are tentative plans to disincentivize canister-controlled neurons in the event that they become plentiful enough to pose a security risk to the network( as discussed in this thread ). Neurons controlled via tECDSA signed HTTPS outcall are indistinguishable from neurons controlled by human actors. As a result, such neurons, although more costly, are less exposed to risk of future adjustments to the NNS governance that would have an adverse impact.
Recent growth within the ICP ecosystem has revealed some scalability challenges that may require a solution in which canisters are able to move freely from one subnet to another in order for the internet computer’s horizontal scaling functionality to play a meaningful role in scaling the ecosystem. With this being the case, neurons controlled via tECDSA signed HTTPS outcalls are challenged by the fact that such tECDSA signatures are specific to the subnet that hosts a canister. If a canister is required to migrate to another subnet, it is possible that it will lose its ability to directly manage its neurons that were created via tECDSA signatures.
In order for a canister to migrate across subnets while maintaining control of their neurons that were created via tECDSA signed HTTPS outcalls, such neurons must be managed via a proposal from a proxy neuron where the proxy neuron has been created via a direct inter canister call from the controlling canister to the NNS governance canister rather than having been created using tECDSA signed HTTPS outcalls.
The proxy neuron must be the sole followee of the neuron that it proxies. For more details, and an example, look here
NOTE: neurons managed via a proxy neuron may NOT be disbursed by such means. But all other neuron management functionality relevant to the operations of Personal DAO’s is available.