wigy

If you are a long-time holder, your problem could be related to #327 because as I understand older Ledger versions were not BIP44 compliant.

I think so far the BIP32 tab is the "advanced" level "I know what I am doing" tab on the screen, but it is not labelled as such. BIP44 is...

Have you tried BIP32 derivation path `m/44'/60'/0'` already? So that the 1st key itself is `m/44'/60'/0'/0`? Ledger wallet is "special" and they are not 100% compatible with BIP44 separating receiving...

@silverwind Could you please have a peek on this PR whether you also think code styling gets better from it?

@dtolnay I could find the documentation for `transparent`, `from` and `into` as [container attributes](https://serde.rs/container-attrs.html), but the `field_identifier` and `variant_identifier` are still missing. Would you please shed some light on their...

@mpfau @bedhub Maybe you are not reading this, so I mention you so you can give a proper answer here.

Oh, this is great to implement as an opt-in feature, although an advanced user one. And then you could even store the derived master key instead of the seed phrase...

That is a nice workaround, thanks. In the middle of a stressful release I did not want to dig up my VSCode, so I have not even tried the suggestion...

Okay, I will try to extract anything related to `client/network/src/schema/api.v1.proto` into a new crate `sc-network-sync` under `client/network-sync`

I am learning a lot about the Substrate libp2p integration as I slowly crawl with this PR. I wanted to do too much refactoring at first, but got some intermediate...