omnilaboratory/OmniBOLT-spec

alice private key,HD chain issue?

Open

#1 geöffnet am 27. März 2020

Auf GitHub ansehen
 (33 Kommentare) (0 Reaktionen) (1 zugewiesene Person) (8 Forks)auto 404
good first issue

Repository-Metriken

Stars
 (268 Stars)
PR-Merge-Metriken
 (Keine gemergten PRs in 30 T)

Beschreibung

bip44 defines the bip32 as follows for convention:

m / purpose' / coin_type' / account' / change / address_index

anything under account is not-hardened meaning a public key of account or higher + private key can lead to all private keys at change or under.

what temporary key is Alice's used to send to bob in your examples? Most wallets now are HD key based and so when an HD key is derived it will send that private key, so potentially any private keys can be found under the account level of Alice's hd chain if Bob finds out about Alice's pubkey one or more levels up from change in the HD chain strategy. Am I thinking about it the wrong way? Where is this key created I assume it would be an address where Alice owns some asset in which case it would be a key in the hd keychain likely.

particularly it seems change may be at risk if there is some in there.

Contributor Guide