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

Unable to "Set Urbit networking keys" #56

Closed
bstro opened this issue Feb 21, 2019 · 13 comments
Closed

Unable to "Set Urbit networking keys" #56

bstro opened this issue Feb 21, 2019 · 13 comments

Comments

@bstro
Copy link

bstro commented Feb 21, 2019

I just installed the newest release (1.1.0) of Bridge. Upon accessing my ship for the first time, I am told that "Before you can issue child points or generate your Arvo keyfile, you need to set your Urbit networking keys." However, the link to "Set Urbit networking keys" is greyed out and unclickable. What should I do?

Thanks!

@jtobin
Copy link
Contributor

jtobin commented Feb 21, 2019

When you say you've accessed your ship, have you authenticated as either its owner or its management proxy? The action should be disabled precisely when you haven't authenticated as one of those.

Can you check that the breadcrumbs at the top of the app read something like Bridge > Main Network > <some address>, and that <some address> is the same as the one displayed under either the 'owner' or 'mgmt proxy' headers when you view your ship?

@bstro
Copy link
Author

bstro commented Feb 21, 2019

Interesting, <some address> is different than the owner proxy address. The keys to my addresses are stored on my Ledger and I'm using Bridge with that. I have access to the wallet keys to which my ships are bound... is there something else I have to do here?

@bstro
Copy link
Author

bstro commented Feb 21, 2019

I've double checked the derivation path as well, it should be able to see that I own three wallets at the derivation path (m/44'/60'/0') bound two three ships and verify that I am the owner.

@jtobin
Copy link
Contributor

jtobin commented Feb 21, 2019

I was just about to suggest checking your derivation path when I saw your most recent reply pop up.

If you authenticate with MyEtherWallet/MyCrypto/etc. do you see the expected address? MEW at least lists their default HD path as m/44'/60'/0', but in reality will derive addresses at m/44'/60'/0'/0, m/44'/60'/0'/1, etc.

Just on a hunch: if you authenticate to Bridge with HD path m/44'/60'/0'/0, do you get the expected address?

@bstro
Copy link
Author

bstro commented Feb 21, 2019

No points to display :(

@jtobin
Copy link
Contributor

jtobin commented Feb 21, 2019

Do you get the expected address if you authenticate with MyEtherWallet/MyCrypto?

@bstro
Copy link
Author

bstro commented Feb 21, 2019

Yes I do, and their UI lists the HD path as m/44'/60'/0' – I can see the wallet addresses that are bound to my ships from that path, but nothing shows up in Bridge when I use that path.

@bstro
Copy link
Author

bstro commented Feb 21, 2019

I FOUND it. m/44'/60'/0'/1 :)

@bstro
Copy link
Author

bstro commented Feb 21, 2019

Do you happen to know if there’s any way to find the correct derivation path for a wallet without guess-and-checking it?

@bstro bstro closed this as completed Feb 21, 2019
@jtobin
Copy link
Contributor

jtobin commented Feb 21, 2019

Nope -- the most likely path is usually the "first" one in the BIP44 sense, i.e. m/44'/60'/0'/0/0, but some applications use other defaults (e.g. MEW/MyCrypto and m/44'/60'/0'/0). Outside of using the usual default schemes as initial guesses or places to start looking, there's not much one can do.

@bstro
Copy link
Author

bstro commented Feb 21, 2019

Good to know, thanks for your help @jtobin !

@jtobin
Copy link
Contributor

jtobin commented Feb 21, 2019

No sweat!

@Fang-
Copy link
Member

Fang- commented Feb 21, 2019

To just chime in real quick:

their UI lists the HD path as m/44'/60'/0'
I FOUND it. m/44'/60'/0'/1 :)

The MyCrypto UI is a bit confusing there, as it appends the zero-based index of whatever address you select in their UI to the path it displays. So, when is displays m/44'/60'/0' and you select the second address, that's actually the address of m/44'/60'/0'/1.
(There may or may not be an off-by-one in that explanation, but you get the idea.)

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

No branches or pull requests

3 participants