-
Notifications
You must be signed in to change notification settings - Fork 318
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,7 +2,7 @@ | |
| CIP: 1853 | ||
| Title: HD (Hierarchy for Deterministic) Stake Pool Cold Keys for Cardano | ||
| Authors: Rafael Korbas <[email protected]> | ||
| Comments-URI: <TBD> | ||
| Comments-URI: https://forum.cardano.org/t/stake-pool-cold-keys-hd-derivation/43360 | ||
| Status: Draft | ||
| Type: Standards | ||
| Created: 2020-12-14 | ||
|
|
@@ -15,7 +15,7 @@ License: CC-BY-4.0 | |
|
|
||
| ## Motivation | ||
|
|
||
| (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. | ||
| (Hierarchical) deterministic derivation of stake pool cold keys enables their restorability from a seed and most importantly, their management on hardware wallet devices. This 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. | ||
|
|
||
| ## Specification | ||
|
|
||
|
|
@@ -35,7 +35,7 @@ Given that stake pool cold keys are cryptographically the same as wallet keys al | |
|
|
||
| ### Why introducing a new purpose? | ||
|
|
||
| Stake pools are not wallets and the core concept of "accounts" is not applicable to them, nor are they supposed to be related to user's wallet in any meaningful way. Therefore treating stake pool cold keys as another "chain" within CIP-1852 specification would rather be a deviation from CIP-1852 than its logical extension. Hence we establish a separate purpose and path structure for stake pool cold keys, having their specifics and differences from standard "wallet" keys in mind. | ||
| Stake pools are not wallets and the core concept of "accounts" is not applicable to them, nor are they supposed to be related to a user's wallet in any meaningful way. Therefore treating stake pool cold keys as another "chain" within CIP-1852 specification would rather be a deviation from CIP-1852 than its logical extension. Hence we establish a separate purpose and path structure for stake pool cold keys, having their specifics and differences from standard "wallet" keys in mind. | ||
|
|
||
| ### Why keeping `coin_type` in the path? | ||
|
|
||
|
|
||