I am curious if the current hotkey permission limitations exists for security purposes, or is just an early design choice, that has not yet needed to be changed? Based off the following comment, this choice was made for the sake of “simplicity”;
Is it possible to enable (remove limitations) a neuron to assign its’ hotkey additional permissions, specifically, Types; 5 (Disburse Neuron), 6 (Split Neuron), 8 (Disburse Maturity), & 9 (Stake Maturity) - or alternatively, open these features across the board, if choosing specific hotkey permissions it to complex from a UI standpoint.
Note that in the backend this could be different for each DAO:
on the NNS, hotkeys have a fixed set of permissions - this is also what is supported on the NNS dapp
on SNSs, each SNS can choose the maximum capabilities that can be given to a new key. Therefore, there can be SNSs where all permissions can be given to any key and others where this is not possible
If we wanted to support these permissions, then the NNS dapp would have to look slightly differently for each SNS - depending on what is and isn’t allowed.
This would add a lot of complexity for non-expert users (for which hotkeys might already be a concept that is hard to grasp).
Therefore, we don’t plan to add this to the frontend now - as we think we should rather strive to make the NNS dapp easier to understand for a larger audience.
open these features across the board, if choosing specific hotkey permissions it to complex from a UI standpoint.
I don’t quite understand what you mean here? Note that you can already build a frontend that would do this - it could just not be used with neurons that are controlled by a principal attached to the NNS dapp.