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
I am encountering a persistent issue while using a Trezor T hardware wallet with Nunchuk version 1.9.25, which occurs on both Windows and Linux operating systems. The primary concern is a warning message regarding an incorrect derivation path whenever I attempt to add the Trezor T to the Nunchuk application.
Key details:
The Trezor T wallet is configured with a native SegWit (bech32) address.
When I proceed despite the warning, the signing address displayed in Trezor resembles a legacy (P2PKH) address format.
I have attached screenshots for a clearer illustration of this issue.
I would appreciate guidance on whether this is the appropriate forum for this issue or if there's a more suitable platform for reporting. Any insights or resolutions to this problem would be highly valuable.
The text was updated successfully, but these errors were encountered:
Hey @alij , the above path is only used to health-check the device. If you go ahead with creating a NativeSegwit multisig wallet, it will pick the correct path (m/48h/0h/0h/2h). You can view the wallet configuration after the wallet is created to make sure.
I am encountering a persistent issue while using a Trezor T hardware wallet with Nunchuk version 1.9.25, which occurs on both Windows and Linux operating systems. The primary concern is a warning message regarding an incorrect derivation path whenever I attempt to add the Trezor T to the Nunchuk application.
Key details:
The Trezor T wallet is configured with a native SegWit (bech32) address.
When I proceed despite the warning, the signing address displayed in Trezor resembles a legacy (P2PKH) address format.
I have attached screenshots for a clearer illustration of this issue.
I would appreciate guidance on whether this is the appropriate forum for this issue or if there's a more suitable platform for reporting. Any insights or resolutions to this problem would be highly valuable.
The text was updated successfully, but these errors were encountered: