-
Notifications
You must be signed in to change notification settings - Fork 56
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
Feature request: display Ledger key connected to specific HD Path #371
Comments
@alexauroradev Where would you expect to find this command? It sounds like a good candidate for a dedicated As a workaround, you can use
It will ask for HD Path, and then in the further steps, it will create a transaction for you to sign where the public key will be printed. |
@frol Can we somehow utilise |
@alexauroradev We already have CLI extensions support, so when you install We may consider adding extensions installing command in the future as well |
Is there any progress on this? Are you considering adding this feature to the NEAR CLI RS (or a separate extension) in the future? |
There is no capacity at the moment to address this feature request, sorry. I also cannot find a good place for this functionality in near-cli-rs, so a separate extension might be justified. Also, old near-cli-rs 0.1.16 actually had "helpers" section:
Consider installing the old version for the time being: https://github.com/near/near-cli-rs/releases/tag/0.1.16 |
At the moment, NEAR CLI RS does not have the way to display the public key corresponding to a specific Ledger HD Path. However, this might be helpful, especially in cases when managing ledger keys of the existing contracts / accounts:
Such functionality is usually missing for other protocols, so not limiting HD paths to "44'/397'/0'/0'/*'" may be appreciated by people who use other protocols, especially Aurora developers.
The text was updated successfully, but these errors were encountered: