Incorrect derivation path displayed on when seed is found on non-standard paths

[wang352303]

1.When I set the path to --bip32-path "m/44'/0'/0'/268/".

python3 seedrecover.py --mnemonic "cup oppose swift nurse robot alcohol hat pigeon govern decline cube fan" --typos 0 --dsw --addr-limit 50000 --wallet-type bip39 --addrs 18bR5jEGCVCkRCJ59C1XDALsvNsCXgv5ZU --bip32-path "m/44'/0'/0'/268/"

2.But the scan result shows m/44'/0'/0'/-2147483380'/1。

python3 seedrecover.py --mnemonic "cup oppose swift nurse robot alcohol hat pigeon govern decline cube fan" --typos 0 --dsw --addr-limit 50000 --wallet-type bip39 --addrs 18bR5jEGCVCkRCJ59C1XDALsvNsCXgv5ZU --bip32-path "m/44'/0'/0'/268/"

Starting seedrecover 1.13.0-CryptoGuide, btcrecover 1.13.0-Cryptoguide on Python 3.13.2 64-bit, 21-bit unicodes, 64-bit ints
Using the 'en' wordlist.
Assuming a 12 word mnemonic. (This can be overridden with --mnemonic-length)
Initial seed guess has a valid checksum (6.2% chance).
2025-03-07 15:08:51 : Phase 1/1: up to 0 mistakes, excluding entirely different seed words.
Wallet Type: btcrseed.WalletBIP39
2025-03-07 15:08:51 : Using 4 worker threads
2025-03-07 15:08:53 : MATCHING SEED FOUND, Matched on Address at derivation path: m/44'/0'/0'/-2147483380'/1----------] 0:00:00, ETA: --:--:--
0 of 1 [--------------------------------------------------------------------------------------------------------------------] 0:00:01, ETA: --:--:--
2025-03-07 15:08:53 : Search Complete

3.Here I used the offline web page bip39-standalone.

[wang352303]

Why does this happen?

[3rdIteration]

It's a cosmetic issue and appears that BTCRecover is treating that part of the path as hardened when it's not. (But only for display of that message, not for actually checking the match)

[wang352303]

Dear btcrecover developers,

When can you correct this,

Allow non-standard paths to be scanned (similar to --bip32-path "m/44'/0'/0'/268/".)

Then come up with the correct answer, thank you!!

[3rdIteration]

It's purely cosmetic (and only applicable to extremely non-standard setups), so isn't a high priority. Probably in the next month or two or something. (Unless you fix it and bring a PR)