You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Got roughly this error reported from users, and I can replicate. If you have expert mode off on the cosmos ledger app, you can't create keys with index > 100.
osmosisd keys add --ledger --index="102" test_102
Error: failed to generate ledger key: failed to recover pubkey: [APDU_CODE_CONDITIONS_NOT_SATISFIED] Conditions of use not satisfied: address rejected for path m/44'/118'/0'/0/102
We should make a more friendly error message in such cases, informing the user to enable expert mode.
Cosmos SDK Version
0.47
How to reproduce?
Connect a ledger. Open cosmos app, ensure expert mode is off. Run:
$DAEMON keys add --ledger --index="102" test_102
You will see:
Error: failed to generate ledger key: failed to recover pubkey: [APDU_CODE_CONDITIONS_NOT_SATISFIED] Conditions of use not satisfied: address rejected for path m/44'/118'/0'/0/102
Enable expert mode, it will work.
The text was updated successfully, but these errors were encountered:
Normally, scanning balances occurs sequentially: 0, 1, 2, ... N. Please note that this process can be time-consuming. As part of a security measure, Expert mode is required to retrieve an {address, pubkey} with a large index (greater than 100). If a compromised wallet uses a high index and you are unaware of it, you (temporarily) might lose access to funds sent there.
Is there an existing issue for this?
What happened?
Got roughly this error reported from users, and I can replicate. If you have expert mode off on the cosmos ledger app, you can't create keys with index > 100.
We should make a more friendly error message in such cases, informing the user to enable expert mode.
Cosmos SDK Version
0.47
How to reproduce?
Connect a ledger. Open cosmos app, ensure expert mode is off. Run:
You will see:
Enable expert mode, it will work.
The text was updated successfully, but these errors were encountered: