What does "extended key is not unique" in Sparrow wallet mean?

External question — Bitcoin Stack Exchange Author: C-Otto Original post: https://bitcoin.stackexchange.com/questions/130984 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. I created a M-of-N multisig wallet with Sparrow, where each of the N keystores is defined using a 24 word BIP32 seed. I then imported the wallet using the "Output Descriptor" file on another machine. This gives me the correct keystores, showing the expected master fingerprints, derivations, and xpub/Zpub values. However, when I import the BIP32 seed (24 words) for the keystores, the xpub field and the keystore tab are marked in red, with a message "extended key is not unique".

External answer — Bitcoin Stack Exchange Author: C-Otto Original post: https://bitcoin.stackexchange.com/a/130985 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. The order of keystores may be different. When exporting the wallet (creating the output descriptor file), the tabs may be in a different order than after importing the wallet on another machine. As such, when entering the BIP32 seed based on the old/wrong order, one might use the wrong keystore and overwrite the correct xpub value (where the correct value was determined from the descriptor file, and the wrong value from the seed). As a consequence, the keystore might now be duplicated in another tab (and the overwritten keystore is missing completely). Long story short, find the correct keystore tab by comparing the fingerprints and shown xpub values before entering the seed.