(Hierarchical) deterministic derivation of cold keys allows for their restorability from a seed and most importantly, their management on hardware wallet devices which in turn mitigates man-in-the middle attacks to which pool operators would otherwise be vulnerable if they managed their stake pool cold keys on a device not specifically hardened against alteration of the data to be signed/serialized without operator’s explicit consent.
This is a great idea, though in its current form I wonder if it leaves many existing SPO’s behind. Many of us have already generated our cold keys without this standard, and are thus unable to implement CIP-1853.
Perhaps we could use an addition to this CIP (or a completely new CIP), that allows us to transfer ownership of a stake pool from one pair of cold keys to another. That way, for the many of us who already have stake pools, we can migrate our pools to this new standard.
@zhekson@Rafael_Korbas we are trying to decide whether there have been any implementations of this, as per this (mostly status review & formatting) update:
Not that I know of - as far as I can tell, any potential solutions to this would introduce a lot of new complexity to the ledger.
This is probably not worth it for the few operators it would apply to (such as myself), who are ok with doing low level things manually. Kind of reminds me of the whole Icarus-Trezor key derivation debacle.
Apologies for not updating my thoughts on the relevant SPO Transfer CIP - I can do that now, or just close it if necessary.