ledger-live-desktop VS ledger-live-common

Forgot to actually answer your question. The answer, like most things is "in the manual". This page leads you to this page which leads to this page, which leads to this page

I see that this has been a request since at least2018

I use a virtual drive. See here: https://github.com/LedgerHQ/ledger-live-desktop/issues/3086 and https://www.reddit.com/r/ledgerwallet/comments/km29on/i_discovered_an_extremely_dangerous_attack_vector/

Your old Nano S won't work with the latest Ledger Live and is probably too old to update in one shot for the new firmware. You may need to grab an old version of Ledger Live from github: https://github.com/LedgerHQ/ledger-live-desktop/releases

Uninstall the updated version and install older 2.42.0 version. https://github.com/LedgerHQ/ledger-live-desktop/releases

You are correct. I found and installed 2.42. 'https://github.com/LedgerHQ/ledger-live-desktop/releases' and got it working again. .... Thanks!

Hello, thank you for reaching out. When you have set up your Ledger, your device has created a seedphrase. Based on the seedphrase your public and private address are calculated. The derivation path is the way how your private and public keys are derived from your Seedphrase. Here you can learn more about HD derivation paths https://medium.com/myetherwallet/hd-wallets-and-derivation-paths-explained-865a643c7bf2 and https://github.com/LedgerHQ/ledger-live-common/blob/master/docs/derivation.md. Here you can learn more about managing Terra (LUNA) https://support.ledger.com/hc/en-us/articles/360017698979-Terra-LUNA-?docs=true. Here you can learn how to access your accounts via Terra station https://support.ledger.com/hc/en-us/articles/4729005570205?docs=true

The mnemonic you get for recovering your ledger doesn't directly code for the private keys of the accounts. It's a "parent" seed from which multiple other seeds are derived. Read about it here.

You can read about it here, it's a bit complicated https://github.com/LedgerHQ/ledger-live-common/blob/master/docs/derivation.md

Been seeing posts regarding hardware wallet supports, but I got confused as to which side (Chia Network or the manufacturer e.g. Ledger) would need to work on it. Last I saw (which is probably out-of-date) was this closed Ledger github issue: https://github.com/LedgerHQ/ledger-live-common/issues/1185.

Ledger: https://github.com/LedgerHQ/ledger-live-common/pull/1449

good question, and I actually don't know the answer off the top of my head. Browsing through the code it looks like both desktop and mobile both reference a shared common CounterValues library (https://github.com/LedgerHQ/ledger-live-common/tree/12f8258ea4811b5023fc16899221f45612180694/src/countervalues) It's possible though the app calls the API less frequently, and uses a cached version whenever possible. Not totally sure tbh.

Thanks for the link. I see it was closed Apr 19. Timing suggests it is that issue I linked previously, should have been fixed in Ledger Live v2.29.0 (bug mentioned in an internal library release v19.10.0).

Going through Ledger Live is an option. Another one is to start a websocket proxy in a terminal (from https://github.com/LedgerHQ/ledger-live-common/blob/master/cli/src/commands/proxy.js or rewrite your own). Yet another one is to modify Metamask to use webusb (https://github.com/terra-project/station is another Chrome extension working with webusb, so that's doable)

however this time the usual website for checking signatures has changed from http://ledger-live-tools.now.sh/lld-signatures it is now redirecting to this https://ledger-live-tools.vercel.app/lld-signatures