Describe the bug
When adding a new account to an existing singlesig wallet, the "Add Account" dialog defaults to "Account #0" even if Account #0 already exists. If the user clicks OK without manually changing the dropdown, Sparrow imports the xpub for Account #0 again, creating a duplicate derivation path under a new tab name. This corrupts the wallet's transaction mapping and splits history between tabs.
To Reproduce
Steps to reproduce the behavior:
- Create a wallet with
Account #0 (e.g., Native Segwit)
- Add
Account #1, give it a name
- Click "Add Account..." again
- Dialog shows "
Account #0" as the default option
- Click OK without changing the dropdown
- Sparrow creates a new tab with the same derivation path as Account #0
- Transaction history becomes split/corrupted across tabs
Expected behavior
The "Add Account" dialog should either:
- Default to the next unused account number (e.g.,
Account #2 if #0 and #1 exist
), OR
- Gray out/disable already-used account numbers, OR
- Show a warning if the user selects an already-used account
Screenshots
[Screenshot showing Account #0 offered when it already exists]
)
Sparrow Version: 2.5.1
OS: macOS / Linux Mint
Describe the bug
When adding a new account to an existing singlesig wallet, the "Add Account" dialog defaults to "Account #0" even if Account #0 already exists. If the user clicks OK without manually changing the dropdown, Sparrow imports the xpub for Account #0 again, creating a duplicate derivation path under a new tab name. This corrupts the wallet's transaction mapping and splits history between tabs.
To Reproduce
Steps to reproduce the behavior:
Account #0(e.g., Native Segwit)Account #1, give it a nameAccount #0" as the default optionExpected behavior
The "Add Account" dialog should either:
Account #2 if #0 and #1 exist), OR
Screenshots
)
[Screenshot showing
Account #0offered when it already exists]Sparrow Version: 2.5.1
OS: macOS / Linux Mint