Quote from: shivam72 on August 10, 2024, 07:39:11 AM

Please tell me if this is the right process and if yes what would be the best way/script to brute force?

Generally, the "right process" is to check the wallet's documentation or source code depending on the availability.
With that, telling the wallet's name should be sufficient for exports to tell the correct derivation path to your address or if it's possible at all.

It's only possible if the derivation path is one of the commonly used derivation paths,
Example list: https://github.com/spesmilo/electrum/blob/master/electrum/bip39_wallet_formats.json

Quote from: Cricktor on August 10, 2024, 10:18:43 AM

btcrecover seems to have the ability to search derivation paths via its --pathlist command option. I haven't tried and used this option with btcrecover, so I'm not entirely sure if it's a valid recommendation and if you can even start with the details you know about your wallet.

The arg will only take a file containing a list of derivation paths that the user provided but wont bruteforce a combination of indices based from the list like a token file.