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

Tweaked snapshot sync threshold #6829

Merged
merged 1 commit into from
Oct 20, 2017
Merged

Tweaked snapshot sync threshold #6829

merged 1 commit into from
Oct 20, 2017

Conversation

arkpar
Copy link
Collaborator

@arkpar arkpar commented Oct 19, 2017

Tweaked snapshot sync to start when falling back more than 30k blocks. Given that block times has decreased 2x and snapshot sync still has to download all the historical blocks again this seems appropriate.

@arkpar arkpar added A0-pleasereview 🤓 Pull request needs code review. B0-patch M4-core ⛓ Core client code / Rust. labels Oct 19, 2017
@rphmeier rphmeier added A8-looksgood 🦄 Pull request is reviewed well. and removed A0-pleasereview 🤓 Pull request needs code review. labels Oct 20, 2017
@arkpar arkpar merged commit 3a01068 into master Oct 20, 2017
@arkpar arkpar deleted the tweak-snapshot-sync branch October 20, 2017 06:18
arkpar added a commit that referenced this pull request Oct 20, 2017
* Tweaked snapshot sync threshold

* Change keypath derivation logic (#6815)

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
@5chdn 5chdn added this to the 1.9 milestone Jan 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A8-looksgood 🦄 Pull request is reviewed well. M4-core ⛓ Core client code / Rust.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants