Exploration of Hypercore's breakthrough designs and capabilities, uncovering its gems that may be scattered across different github accounts (official and community-led), and learning to think from the "first principles" of P2P, while using the best Cloud, AI and blockchain have to offer.
Hypercore has an associated static Public / Private key pair. Private keys should never migrate between devices for security. When device is replaced, new keypair is created. Need
Proposed solution
Use Hypercore-multi-key module which allows to switch this Hypercore to a new keypair. We need to add code to sign the new key with the old one to establish safe handoff.
We need to verify this signature on receiving nodes so that they can prove to themselves the legality of key rotation. Perhaps this can be added as a hypercore extension?
After key is rotated, old key is revoked.
Not covered by this issue
Key loss and recovery schemes. This will be addressed by another issue
Problem
Hypercore has an associated static Public / Private key pair. Private keys should never migrate between devices for security. When device is replaced, new keypair is created. Need
Proposed solution
Use Hypercore-multi-key module which allows to switch this Hypercore to a new keypair. We need to add code to sign the new key with the old one to establish safe handoff.
We need to verify this signature on receiving nodes so that they can prove to themselves the legality of key rotation. Perhaps this can be added as a hypercore extension?
After key is rotated, old key is revoked.
Not covered by this issue
Key loss and recovery schemes. This will be addressed by another issue