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:

1. Alice and Bob are building the application together.
2. They want to improve the robustness of the application by deploying two Ledger full access keys to the smart contract account.
3. One of these keys is used by Alice while creating the account and deploying the contract.
4. Another one should be provided by Bob to Alice.
5. ???

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.