BlockchainCommons / BlockchainCommons/GordianSeedTool-iOS
Add Text to Crypt-Requests for Keys
- Dominant language
- Swift
- Stars
- 51
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
This is suggested text to add to crypto-requests for keys, based on what the key derivation is.
My general suggested format is:
```
Another device is requesting a [public|private] key from this device with this derivation:
[derivation]
[derivation explanation]
[if there is a description:]
The device has included the following description to explain their request:
[description]
```
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.
Contributor guide
Assessment
This issue has not been assessed yet.