You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, a bit of a weird one here. Due to an issue I raised with iOS (nunchuk-io/libnunchuk#27) I made a batched transaction on macOS v1.9.22 and it seems the change address that was chosen by Nunchuk used a derivation path that causes both Nunchuk on iOS and Sparrow on macOS to report incorrect balances.
After making the batched transaction I imported my wallet into Sparrow, increased the gap limit to 2000 and noticed that Nunchuk had chosen m/84'/0'/0'/1/54 as the change address for my batched transaction. ../1/0 to ../1/2 are the only change addresses previously used.
I guess this would fall more into a UX issue since I was able to configure my iOS version of the wallet with a larger gap limit to access my satoshi's but it may be confusing to less technical users 👍
The text was updated successfully, but these errors were encountered:
Hi, a bit of a weird one here. Due to an issue I raised with iOS (nunchuk-io/libnunchuk#27) I made a batched transaction on macOS v1.9.22 and it seems the change address that was chosen by Nunchuk used a derivation path that causes both Nunchuk on iOS and Sparrow on macOS to report incorrect balances.
After making the batched transaction I imported my wallet into Sparrow, increased the gap limit to 2000 and noticed that Nunchuk had chosen m/84'/0'/0'/1/54 as the change address for my batched transaction. ../1/0 to ../1/2 are the only change addresses previously used.
I guess this would fall more into a UX issue since I was able to configure my iOS version of the wallet with a larger gap limit to access my satoshi's but it may be confusing to less technical users 👍
The text was updated successfully, but these errors were encountered: