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
{{ message }}
This repository has been archived by the owner on Jul 25, 2024. It is now read-only.
Hello! I am a customer support agent here at Ledger.
We often have customers that have sent their VET to their address derived from Ledger Live. This address follows the normal Ethereum address derivation path (m/44'/60'/0').
When customers make this mistake, they are unable to recover their VET without exposing their Ledger generated seed phrase.
I would like to make the suggestion that you give some advanced option to define a derivation path when importing your Ledger device into Sync. This would solve this sort of issue for people who rek themselves by sending their VET on the VeChain network to an address with the wrong derivation path (60 for coin type instead of 818 which is the default VeChain derivation path).
I hope this sort of thing can be implemented! It's nice to have the option for such a thing.
Thank you.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello! I am a customer support agent here at Ledger.
We often have customers that have sent their VET to their address derived from Ledger Live. This address follows the normal Ethereum address derivation path (m/44'/60'/0').
When customers make this mistake, they are unable to recover their VET without exposing their Ledger generated seed phrase.
I would like to make the suggestion that you give some advanced option to define a derivation path when importing your Ledger device into Sync. This would solve this sort of issue for people who rek themselves by sending their VET on the VeChain network to an address with the wrong derivation path (60 for coin type instead of 818 which is the default VeChain derivation path).
I hope this sort of thing can be implemented! It's nice to have the option for such a thing.
Thank you.
The text was updated successfully, but these errors were encountered: