Open shannona opened 2 years ago
I like in general, but use of “current” doesn’t seem quite right. It is our opinion of the best practice. Not sure how to express.
I've tried substituting in best-practice; see what you think.
Looks good. Reading it again the only other thing is I think we should explicitly say these are keys for bitcoin, and if it is testnet or not.
At some point we’ll need to do similar research into describing common requests for other major paths of non-Bitcoin derivations.
This is suggested text to add to crypto-requests for keys, based on what the key derivation is.
My general suggested format is:
My suggested derivation explanations are:
48'/0'/0'/2' This requests a [public|private] key for use in a multisig, using the best-practice Segwit methodology.
84'/0'/0' This requests a single-sig [public|private] key, using the best-practice Segwit methodology.
48'/0'/0'/1' This requests a Nested Segwit [public|private] key for use in a multisig. This style of key is outdated, but still in use on some older wallets.
49'/0'/0' This requests a single-sig [public|private] key. This style of key is outdated, but still in use on some older wallets.
45' or 48'/0'/0'/0' This requests a [public|private] key for use in a multisig. It is a request for a very outdated Legacy key rather than a modern Segwit key.
44'/0'/0' This requests a single-sig [public|private] key. It is a request for a very outdated Legacy key rather than a modern Segwit key.
Master This requests a [public|private] Master Key for your seed. Be aware that this will provide [watch-only access|total access] to your entire HD wallet.
86'/0'/0' This requests a single-sig [public|private] key using the new Taproot protocol. Be aware that this is a very new methodology and there may be some dangers associated with its usage as a result.