Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: custom path derivation with known network #508

Merged
merged 3 commits into from
Jan 2, 2020

Conversation

hanwencheng
Copy link
Contributor

closes #507 .

It works as same as expected behaviour in the issue description.

Tbaut
Tbaut previously approved these changes Dec 27, 2019
Copy link
Contributor

@Tbaut Tbaut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small nit, looks good otherwise


const onPathDerivation = async () => {
if (!validateDerivedPath(derivationPath)) {
return setIsPathValid(false);
}
const seedPhrase = await unlockSeedPhrase(navigation);
console.log('complete path is', completePath, 'networkKey:', networkKey);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stray log

@hanwencheng hanwencheng merged commit d9e7e88 into master Jan 2, 2020
@hanwencheng hanwencheng deleted the hanwen-custom-path-prefix branch January 2, 2020 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Custom path derivation with a known network add an extra path
2 participants