Tezos Stack Exchange is a question and answer site for users, experts, and developers of the Tezos blockchain project. It only takes a minute to sign up.
Sign up to join this community
What is the correct BIP-44 path structure for the Tezos ledger apps? Should it have five path components (as Galleon uses) or four (as tezos-client and Tezbox use)?
The BIP-44 spec defines 5 levels of path and uses all 5 in all of its examples. It's not apparent that the final "index" component is optional.
Tezbox and tezos-client appear to default to the m/44'/1729'/0'/0' path, whereas Galleon defaults to m/44'/1729'/0'/0'/0'.
The Ledger app itself supports any length from 2 components up to 10, as long as the derivation path starts with 44'/1729'. This allows the Ledger to support either convention, and this support will continue into the indefinite future. As for which convention is better, that is a controversy quite outside of my scope as a Ledger developer :-) but there is no strong need to change conventions and any good tool should allow you to enter a custom path. Personally, I go with the tezos-client convention because I prefer the command line.
