Goal account list -w "wallet" for Ledger device only lists first account

mstuderMartin StuderJul 15, 2021

Hi,

when I use goal account list -w "wallet" having connected a Ledger device with multiple accounts, I can only see the “first” account. This makes it impossible to use goal clerk sign ... --signer "second-account-address" since that will fail with the error “Couldn’t sign tx with kmd: key does not exist in this wallet”.

Any idea on how to work with multiple Algorand accounts on a Ledger device? Is this supported?

Thanks & Best regards,
Martin

fabriceFabrice BenhamoudaJul 15, 2021

Unfortunately, it’s still an open issue:

github.com/algorand/go-algorand

Add goal support for multiple Ledger Nano accounts

opened 04:25AM - 28 Feb 21 UTC

pbennett

Team Carbon-11

## Is your feature request related to a problem? Please describe. The Ledger …Nano supports multiple accounts for every coin I've used with it. For Algorand, Ledger Live supports this for Algorand as well. However, the goal CLI which supports the Ledger well, does NOT support multiple accounts. It only supports account 0. Trying to add a new account yields: ``` > goal wallet new -w Ledger-Nano-X-0001-XXXXXXX Error processing command: operation not supported by wallet ``` ## Describe the solution you'd like. Just like you can create a new wallet with a seed and create the same accounts from that seed, the ledger works the same way. Any accounts added via Ledger Live should all be visible via Goal. This is required in particular for signing 'online/offline' transactions. I'll often use goal for sends as well via goal clerk send. The key is, all the normal operations should work cleanly, list, new, and use of the accounts at a minimum.

Please up-vote the issue.

mstuderMartin StuderJul 15, 2021

Thanks @fabrice - upvoted the issue. My use case is exactly as described, for taking part in consensus and signing online/offline transactions.

aojjazzPatrickJul 19, 2021

Upvote this while you’re at it.

github.com/algorand/go-algorand

Add ability to recover from Ledger BIP39 seed and get Algorand compatible wallet.

opened 10:00PM - 01 May 21 UTC

pbennett

external contribution new-feature-request

## Is your feature request related to a problem? Please describe. See this re…ddit post for an example of the issue: https://www.reddit.com/r/ledgerwallet/comments/mcn7rs/psa_if_you_use_algo_with_your_ledger_be_aware/gs4t3fk/ The issue is that Algorand's choice to use a non-standard key mechanism and not BIP39 means that the 24-word BIP39 seed for a Ledger device and the Algorand accounts it generates are ONLY usable with and by a Ledger only. If your ledger is lost, and another Ledger is not available (or no longer exists) you can't recover your funds. ## Describe the solution you'd like. Algorand should either provide a utility to accept a 24-word BIP39 and provide the Algorand 25-word mnemonics for each indexed account (could specify which account index to export. Since Algorand created the Algorand Ledger app, knowledge of what derivation path is used is known and this should be doable. Another alternative is to allow goal wallet new -r to accept a bip39 option. It could then seed the kmd/goal wallet correctly so goal account new with that wallet generates each algorand account (0, 1, etc.) correctly and users could goal account export those individually as desired. Algorand created this situation and is doing Ledger users a bit of a disservice to be honest. I like my Ledger, but if something were to happen to the device and I didn't have a backup device (or they were no longer made) then I'd be out of luck for Algorand, but not any other crypto.

bluelinesNov 17, 2024

↩ in reply to fabrice

Was this issue resolved? Ran into this issue for the same use case as @mstuder mentioned.

aojjazzPatrickMay 15, 2025

No and I doubt goal ever gets any new love. Best to just use other wallets. If you’re just wanting to sign node key registrations use something like https://algotools.org/