-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent seed grouping (monero) #1762
Comments
hi @nahuhh thanks for opening this issue, currently Monero shouldn't be grouped anyway, only Bip39 wallets should be grouped so even Bitcoin and Litecoin wallets which are created as Electrum seeds should not be grouped this feature will work best for newly created wallets, we will add support for Monero as well when we add support for BIP39 to monero seeds as well soon we will look into why it grouped it in the first place tho, but can you give me more info on which wallets it grouped it with? i.e did it group it with a Monero wallet, or with some other wallet types |
i have the same monero wallet added multiple times with diff restore heights. grouped with monero wallets |
Just to be sure, opening all the affected wallets reset their state and ungrouped them? So now your wallet screen has a *correct state for wallet groups? |
yes
not sure i understand the question. |
Meant "Correct state" :P |
I have multiple wallets with the same seed (diff restore height) Lets say seed 2: nahuhh2 nahuhh2old nahuhhtwo it was grouping after opening the seed1 wallets, the group disappeared. if xmr should not be grouping, then the bug was that it grouped them (then ungrouped them). if same-seed for xmr should be grouping, the bug is that its inconsistently grouping some same-seed Xmr wallets, but not others. |
Ok yeah this feature doesn't work for Monero yet so there isn't supposed to be any wallet groups with Monero. Will have to investigate the upgrade glitch causing incorrect wallet groups further |
Describe the bug
dirty fix: if primary addr match, group them.
The text was updated successfully, but these errors were encountered: