Currently, there is a discrepancy between the derivation paths used during wallet generation and those used during the import process. This leads to a situation where the same mnemonic phrase results in different addresses and inner-hash values depending on the action performed (Create vs. Import).
Problem:
Inconsistency: User gets different addresses for the same seed phrase.
UX Issue: Users cannot reliably restore their wallets if the derivation logic differs from the creation logic.
Data Integrity: The inner-hash calculation is tied to the derivation path, causing mismatches in local database indexing.
Proposed Changes:
Unify Derivation Path: Standardize the derivation path across the entire application (e.g., switch to a single standard like m/44'/... or a specific custom path used by the protocol).
Attached is a screenshot showing the different addresses and derivation paths as an example.
Currently, there is a discrepancy between the derivation paths used during wallet generation and those used during the import process. This leads to a situation where the same mnemonic phrase results in different addresses and inner-hash values depending on the action performed (Create vs. Import).
Problem:
Inconsistency: User gets different addresses for the same seed phrase.
UX Issue: Users cannot reliably restore their wallets if the derivation logic differs from the creation logic.
Data Integrity: The inner-hash calculation is tied to the derivation path, causing mismatches in local database indexing.
Proposed Changes:
Unify Derivation Path: Standardize the derivation path across the entire application (e.g., switch to a single standard like m/44'/... or a specific custom path used by the protocol).
Attached is a screenshot showing the different addresses and derivation paths as an example.