Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Backport #6815 and #6829 #6837

Merged
merged 2 commits into from
Oct 20, 2017
Merged

Backport #6815 and #6829 #6837

merged 2 commits into from
Oct 20, 2017

Conversation

arkpar
Copy link
Collaborator

@arkpar arkpar commented Oct 20, 2017

No description provided.

arkpar and others added 2 commits October 20, 2017 11:59
While the standard defined by Trezor as the default derivation path here
https://blog.trezor.io/trezor-integration-with-myetherwallet-3e217a652e08
says that it should be `m/44'/60'/0`, in practice they don't have an
implementation of a wallet for Ethereum themselves and refer customers
to MEW.

MEW has a custom implementation of the path derivation logic that allows them to
generate multiple addresses by essentially adding `/0`, `/1` etc to the path.

In my initial implementation of Trezor I didn't take this into
consideration unfortunately and just used the keypath that Trezor
themselves recommended. However, given that it's seemingly standard
practice to append `/0` for a "sub-address" (and this is what we've done
for Ledger as well) it seems like a mistake on my part to not take that
into consideration.

Unfortunately, anyone who has used their Trezor device with Parity
previously would now see a different address when they connect the
Trezor device the next time. The only way they would have to access the
old address is to use an old version, or by going through MEW and
selecting the Ledger keypath.

Also see #6811
@arkpar arkpar added the A8-backport 🕸 Pull request is already reviewed well in another branch. label Oct 20, 2017
@arkpar arkpar merged commit 48c7e4a into beta Oct 20, 2017
@arkpar arkpar deleted the backporting branch October 20, 2017 10:51
@5chdn 5chdn added this to the Patch milestone Jan 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A8-backport 🕸 Pull request is already reviewed well in another branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants